DM42 License Statement

Discussion around the Swiss Micros DM42 calculator.
User avatar
Vitasam
Posts: 192
Joined: Thu Jun 01, 2017 9:51 am
Location: Finland
Contact:

Re: DM42 License Statement

Post by Vitasam » Tue Jun 05, 2018 6:16 am

I have a question about flashing the firwmware:
Update procedure
1. Active USB disk in the setup menu
2. Copy both DMCP_flash_X.Y.bin and the .pgm file from the PC/MAC to the FAT partition of the DM42
/build folder contains following files:

Code: Select all

662048 Jun  5 05:55 DM42PGM_flash.bin
662068 Jun  5 05:55 DM42PGM.pgm
1370864 Jun  5 05:55 DM42PGM_qspi.bin
So I have to copy DM42PGM_flash.bin and DM42PGM.pgm to the FAT of DM42?
Elektronika MK-61, Elektronika MK-52, HP15c LE, DM42 SN#16 FW 3.7.1

User avatar
ijabbott
Posts: 82
Joined: Fri Dec 15, 2017 1:34 pm
Location: Manchester, UK

Re: DM42 License Statement

Post by ijabbott » Tue Jun 05, 2018 7:39 am

Vitasam wrote:
Tue Jun 05, 2018 6:16 am
I have a question about flashing the firwmware:
Update procedure
1. Active USB disk in the setup menu
2. Copy both DMCP_flash_X.Y.bin and the .pgm file from the PC/MAC to the FAT partition of the DM42
/build folder contains following files:

Code: Select all

662048 Jun  5 05:55 DM42PGM_flash.bin
662068 Jun  5 05:55 DM42PGM.pgm
1370864 Jun  5 05:55 DM42PGM_qspi.bin
So I have to copy DM42PGM_flash.bin and DM42PGM.pgm to the FAT of DM42?
You just need to copy DM42PGM.pgm, I think. Then load it into Flash memory using the DMCP menu. (Note: you haven't built DMCP, only DM42PGM.)

keithdalby
Posts: 477
Joined: Mon Apr 24, 2017 6:38 pm

Re: DM42 License Statement

Post by keithdalby » Tue Jun 05, 2018 8:21 am

I have no use for the source code (nor all this fuss about it), so I'll just wait for the next normal firmware update and update as normal. I don't see the point of updating the firmware when there is no functional difference between the last firmware version and this new open source one.

gmac42
Posts: 14
Joined: Fri Jun 01, 2018 9:30 am

Re: DM42 License Statement

Post by gmac42 » Tue Jun 05, 2018 8:51 am

keithdalby wrote:
Tue Jun 05, 2018 8:21 am
I have no use for the source code (nor all this fuss about it), so I'll just wait for the next normal firmware update and update as normal. I don't see the point of updating the firmware when there is no functional difference between the last firmware version and this new open source one.
The point is to see if you can compile it yourself, as a starting point for your own fixes and improvementes, or just out of curiosity.
DM42 #650, DM41L #801, HP 41CX, HP 41CV, HP 50G, TI 89

grsbanks
Posts: 652
Joined: Tue Apr 25, 2017 9:23 am
Location: Preston, Lancs, UK

Re: DM42 License Statement

Post by grsbanks » Tue Jun 05, 2018 9:08 am

Not everybody has that curiosity. Some people buy a calculator because they need something to help them in their job or hobby rather than because they want it to be that hobby.
Not SwissMicros staff, just an enthusiast.

gmac42
Posts: 14
Joined: Fri Jun 01, 2018 9:30 am

Re: DM42 License Statement

Post by gmac42 » Tue Jun 05, 2018 9:20 am

grsbanks wrote:
Tue Jun 05, 2018 9:08 am
Not everybody has that curiosity. Some people buy a calculator because they need something to help them in their job or hobby rather than because they want it to be that hobby.
And that's perfectly fine, too. :-)
DM42 #650, DM41L #801, HP 41CX, HP 41CV, HP 50G, TI 89

Thomas Okken
Posts: 453
Joined: Tue May 02, 2017 3:48 pm
Contact:

Re: DM42 License Statement

Post by Thomas Okken » Tue Jun 05, 2018 12:44 pm

keithdalby wrote:
Tue Jun 05, 2018 8:21 am
I have no use for the source code (nor all this fuss about it)
If the DM42 had been GPL-compliant from the beginning, there would never have been any fuss. And you could have simply ignored the fuss that did occur, since you don't care about the issue anyway.

rprosperi
Posts: 341
Joined: Mon Apr 24, 2017 5:48 pm
Location: New York

Re: DM42 License Statement

Post by rprosperi » Tue Jun 05, 2018 1:42 pm

keithdalby wrote:
Tue Jun 05, 2018 8:21 am
I have no use for the source code (nor all this fuss about it), so I'll just wait for the next normal firmware update and update as normal. I don't see the point of updating the firmware when there is no functional difference between the last firmware version and this new open source one.
One reason you may consider updating to this new version is to help verify that this new version truly is functionally identical to the prior version. As you already use the DM42 for some set of uses, running those same programs and/or calculations on the new build and verifying same results will contribute to the new DM42's known stability.

One of the reasons that Free42 and the DM42 are the fine tools that they are is because of the extensive feedback provided by the community. The new build, which obviously had a lot of 'under the hood' changes, is intended to be functionally identical, but only extensive use by a wide variety of programs and calculations will verify this is truly the case.

Just a suggestion though.
--bob p

DM42: β00071 & 00282

keithdalby
Posts: 477
Joined: Mon Apr 24, 2017 6:38 pm

Re: DM42 License Statement

Post by keithdalby » Tue Jun 05, 2018 2:45 pm

rprosperi wrote:
Tue Jun 05, 2018 1:42 pm
Just a suggestion though.
A very good one I hadn't considered, thank you

Bill (Smithville NJ)
Posts: 19
Joined: Sat Jul 22, 2017 7:14 pm

Re: DM42 License Statement

Post by Bill (Smithville NJ) » Tue Jun 05, 2018 3:19 pm

Thomas Okken wrote:
Tue Jun 05, 2018 12:44 pm
If the DM42 had been GPL-compliant from the beginning, there would never have been any fuss. And you could have simply ignored the fuss that did occur, since you don't care about the issue anyway.
Thomas,

I think the key question for me is:

Are you satisfied with the final result?
Or do you feel that there are still outstanding issues?

I'm looking forward to what people come up with now that they have the code.

Bill
Smithville, NJ

Post Reply