Is the TinyCLR Bootloader (FEZ Config and the TeraTerm method) the same as STMicro’s DFU Bootloader (STDFU Tester and DFuSeDemo)?
Interesting I tried both the Tester and Demo when I had the FEZ Stick in loader mode and both programs did not see it so I’m assuming that something is different. Note, on my STM32F4 board I have to put it into DFU mode by jumping the Boot0 pin to 3.3v.
The reason I ask is I use the STMF32 DFU boot loader for when for whatever reason memory (user and firmware) is corrupted and both the App and MFDeploy cannot connect to the board.
Also, can the GHI Bootloader get corrupted and if so, do I need to be able to use the STM DFU boot loader to load the GHI Bootloader? I need to know this to plan for the Boot0 jumper on the new board. And if I need this, where do I get the GHI Bootloader file or is it included in the firmware load?
The GHI Bootloader is different to STMicro’s DFU Bootloader.
The GHI Bootloader is installed on our TinyCLR devices. Depends on what device is, it stays in first few sectors of flash, and it locks the device as well. Because the device is locked so DFU (STDFU Tester and DFuSeDemo) will not work on these locked devices.
You need TinyCLR Config or TeraTerm to program the firmware if GHI Bootloader installed on the board, no need STMDFU.
FezConfig is for NETMF, not for TinyCLR - SITCore.
On TinyCLR boards (here is FEZ stick), user should not need BOOT0. Leave it alone since I think it should have 10K pulldown. You just need LDR pin. This pins is low => enter GHI loader mode. high => run firmware if firmware is ready.
Also, can the GHI Bootloader get corrupted
=> No, it is locked, and user can’t modify it, unless user deleted on purpose, because it is not simple to wipe out with normal way.
where do I get the GHI Bootloader file or is it included in the firmware load?
It is installed by GHI only. Somehow if user deleted it, you may need contact GHI to program GHI bootloader again.