Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

Alternate systems for Netduino Plus 2


  • Please log in to reply
6 replies to this topic

#1 blackt1ger

blackt1ger

    Member

  • Members
  • PipPip
  • 14 posts

Posted 03 December 2013 - 09:42 PM

Okay, excuse my blasphemy, but I'm investigating putting FreeOS (or similar) on my Netduino and building a native app.  Yes, this would be a lot of work.....

 

The way this came about was a need to create/test/build a new STM32 based board.  I took stock of what I had laying around and noticed that the Netduino Plus 2 that I have fits the bill perfectly (well, almost).

 

What I like is there is not a lot of extra junk on the board (accelerometer, LED's, POT's, Kitchen Sinks, etc).  However, I don't want to totally toast the board from running the base MicroFramework.

 

I however, need to understand a few things about flashing.  First, I can DFUSE stuff and I can MFDeploy stuff successfully.  I've built firmware and used MFDeploy to push "BuildOutputTHUMB2GCC4.6leFLASHreleaseNetduinoPlus2bintinyclr.hex" 

 

What I need to understand are the underlying bits - what does DFUSE connect to?  I presume the BootLoader.  Does STM have their own bootloader?  What does MFDeploy connect to? 

 

And most importantly --- what should I NOT do, to keep everything running?  Ideally, I want to move from a Native STM app to a MicroFramework app and back.

 

I'm okay with reading docs, if someone can point me to something that is pertinent.  I don't want to start reading the STM FLASH programming guide and then realize that "Oh, Netduino does something a bit different....." after I totally brick my board, have to solder in the JTAG connector headers and buy the STLink cable.



#2 Kip

Kip

    Member

  • Members
  • PipPip
  • 22 posts
  • LocationItaly

Posted 03 December 2013 - 10:02 PM

If you want to do something like this you should buy a stlink anyway... Also, I don't think it's possibile to switch between native and netmf at runtime



#3 CW2

CW2

    Advanced Member

  • Members
  • PipPipPip
  • 1592 posts
  • LocationCzech Republic

Posted 03 December 2013 - 10:45 PM

Does STM have their own bootloader?

  Yes, they have bootloader (in ROM). It supports serial, CAN and USB OTG in device mode (DFU).   

What does MFDeploy connect to?

 

TinyBooter or TinyCLR; via a proprietary wire protocol. I am not sure it is documented, but there is WireProtocol.cpp in the firmware source.

 

And most importantly --- what should I NOT do, to keep everything running?  Ideally, I want to move from a Native STM app to a MicroFramework app and back.

 

If I understand it correctly, the most critical part will be flash memory layout. I guess it should not be too hard to modify TinyBooter to launch either TinyCLR or your native STM application based on some flag, or implement a managed method that transfers execution to a particular address.



#4 blackt1ger

blackt1ger

    Member

  • Members
  • PipPip
  • 14 posts

Posted 04 December 2013 - 06:09 AM

 

 ... I guess it should not be too hard to modify TinyBooter to launch either TinyCLR or your native STM application based on some flag, or implement a managed method that transfers execution to a particular address.

 

Thanks.  I'm okay with having to reflash to switch between systems.  The TinyBooter should just jump to a vector, anyway.  So, If I leave TinyBooter alone, all I really need to worry about is what goes at 0x08020000.  I'll check out WireProtocol.cpp.

 

I just finally got through to the OVP people.  They manually approve registrations and then you still got to wait for a FLEX license.  Even though it is free. I'll see if I can "clone" the boot sequence into an OVP platform.  Sigh - but it means setting up MINGW 1.0.  Never a good thing.  But I'll check it out, - ain't no reason why I couldn't use Yagarto 4.6......



#5 Kip

Kip

    Member

  • Members
  • PipPip
  • 22 posts
  • LocationItaly

Posted 04 December 2013 - 08:45 AM

Just a curiosity: is there a reason to use Yagarto 4.6 instead of the latest 4.7.2?



#6 blackt1ger

blackt1ger

    Member

  • Members
  • PipPip
  • 14 posts

Posted 04 December 2013 - 12:57 PM

Well only that I've got 4.6 working.

I don't want to go to the 4.3 firmware yet, as I'm using VS2010.

 

Now, should I be using 4.7.2?

 

I had major pains getting the firmware built.  Of course, the problem was a flakey usb port.  But to go through another iteration of "it don't work" trial an error is not something I want to do.



#7 Kip

Kip

    Member

  • Members
  • PipPip
  • 22 posts
  • LocationItaly

Posted 04 December 2013 - 02:29 PM

I don't know, I was asking because I managed to successfully build a firmware with 4.7.2 but it doesn't work (hangs when trying to debug), I'm trying to figure out where is the problem (the compiler of my dev environment)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.