Page 8 of 9

Re: DM42 License Statement

Posted: Wed Jun 06, 2018 1:16 pm
by Vitasam
dlachieze wrote:
Wed Jun 06, 2018 12:41 pm
Good! Which ARM Toolchain have you used for your build?
Actually the same GCC ARM toolchain I'm using for my "slow-moving" Stm32Basic hobby project on STM32F103C8T6 "blue pill" board:

Code: Select all

sudo apt-get install gcc-arm-none-eabi binutils-arm-none-eabi gdb-arm-none-eabi

Re: DM42 License Statement

Posted: Thu Jun 07, 2018 2:58 pm
by Thomas_ER
Vitasam wrote:
Wed Jun 06, 2018 1:13 pm
FireBird wrote:
Wed Jun 06, 2018 12:44 pm
Maybe we should create a separate HowTo thread?
+1 !
+1,
would be very helpful!

Re: DM42 License Statement

Posted: Thu Jun 07, 2018 3:13 pm
by grsbanks
I'm going to do better than that.

When I get a couple of minutes I'm going to set up a "developer" sub-forum under "DM42".

Re: DM42 License Statement

Posted: Thu Jun 07, 2018 5:43 pm
by Thomas_ER
@SwissMicros:
Please don't forget to adjust the User Manual, e.g. https://www.swissmicros.com/dm42/doc/dm42_user_manual/
I don't know,if other places like https://www.swissmicros.com/dm42/tools/ have to be checked.

Re: DM42 License Statement

Posted: Fri Jun 08, 2018 11:38 am
by grsbanks
There is now a community-driven forum for DM42 firmware, where questions about the toolchain, methods, tips & tricks can be discussed.

Please note that support in this forum from Swiss Micros staff will only happen as time permits, so not that often! This is intended mainly as an area for the community to meet.

Re: DM42 License Statement

Posted: Mon Jun 11, 2018 1:00 pm
by Logan
This is absolutely outstanding. I'm excited. Not sure how capable I am of contributing much more than enthusiasm though :)

Re: DM42 License Statement

Posted: Mon Jun 11, 2018 3:45 pm
by mcc
Hi Logan,

Enthusiasm is one of the greatest contributions one could give.

Only my two cents, your mileage may vary...

:)

Cheers!
Meino

Re: DM42 License Statement

Posted: Wed Jun 13, 2018 11:57 am
by Thomas Okken
Bill (Smithville NJ) wrote:
Tue Jun 05, 2018 3:19 pm
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?
It took me a while to take a look at it, my apologies for that -- I was on vacation when the release was made, and while on vacation, I caught a nasty cold that I'm still not recovered from -- but yesterday I finally installed 3.7 on my DM42, and downloaded the sources from github and built the pgm from them.

I haven't looked at everything yet, but from what I have seen so far, SwissMicros did a good job with this. It is possible for DM42 users to customize and build their own firmware now, and that was what the whole controversy was all about.

The only remaining issue that I could imagine existing would be if they put code in the OS part that belongs in the Free42 part, but I don't think that's the case. Again, I haven't looked at everything yet, but it looks like the OS API defines functionality along lines that are reasonable for an OS, namely, hardware abstraction, including filesystem and display access.

So, to summarize, I'm happy with the 3.7 release. Well done!

Re: DM42 License Statement

Posted: Wed Jun 13, 2018 12:05 pm
by toml_12953
Thomas Okken wrote:
Wed Jun 13, 2018 11:57 am

The only remaining issue that I could imagine existing would be if they put code in the OS part that belongs in the Free42 part, but I don't think that's the case. Again, I haven't looked at everything yet, but it looks like the OS API defines functionality along lines that are reasonable for an OS, namely, hardware abstraction, including filesystem and display access.

So, to summarize, I'm happy with the 3.7 release. Well done!
That's great to hear! So there's no remaining acrimony between you and D & M? If not, you three can move forward again and we will all benefit.

Re: DM42 License Statement

Posted: Wed Jun 13, 2018 12:10 pm
by Thomas Okken
toml_12953 wrote:
Wed Jun 13, 2018 12:05 pm
So there's no remaining acrimony between you and D & M?
Yes, as far as I'm concerned, we're good now.