I've created an interop method that's been added to the NetduinoPlus2 firmware. It builds correctly, I have the generated binary files.
I am trying to follow the instructions from http://wiki.netduino...to-GCC-4-6.ashx
[color=rgb(51,51,51);font-family:Verdana, Arial, Helvetica, sans-serif;]The build system will create a subtree 'BuildOutput' will contain the various build products. The firmware pieces of interest are in .BuildOutputTHUMB2GCC4.6leFLASHreleaseNetduinoPlus2bin and are * Tinybooter.bin * tinyclr.bin/ER_CONFIG * tinyclr.bin/ER_FLASH[/color]
[color=rgb(51,51,51);font-family:Verdana, Arial, Helvetica, sans-serif;]Use the 'DFU File Manager' from the 'DfuSe Demo' apps, to extract a binary from a dfu, to extract the pieces of the official firmware (we only need the Tinybooter). I.e. NetduinoPlus2_Firmware_126.96.36.199_00_08000000.bin[/color]
[color=rgb(51,51,51);font-family:Verdana, Arial, Helvetica, sans-serif;]Use the 'DFU File Manager' from the 'DfuSe Demo' apps, to generate a dfu from multiple bin files. Since these are bin file, you will need to specify their location in flash. The locations to use are: 08000000 for NetduinoPlus2_Firmware_188.8.131.52_00_08000000.bin 0800c000 for ER_CONFIG 08020000 for ER_FLASH[/color]
Can somebody please rephrase that bit for me? I do not have the file "NetduinoPlus2_Firmware_184.108.40.206_00_08000000.bin" inside "BuildOutput" and I don't know what address to put "Tinybooter.bin" at.
I tried putting Tinybooter.bin at 08000000 (along with the ER_FLASH and ER_CONFIG, placed at the addresses suggested in the wiki), generated a DFU file, erased the chip using DFU Tester, and then attempted to upgrade using DfuSe Demo. I got the error that the first verification mismatch occurred at 0x0800C000. I am unsure if this is my mistake or not because this memory region is considered "config" region, and might be protected.
I have attempted to erase this config region but I got an unknown error without explaination.
After the attempted upgrade, my NetduinoPlus2 does not enumerate when plugged into the USB port, so it is not working with Visual Studio anymore. I am not panicking, because I can still access the bootloader, and I also own several J-Links and ST-Links.
What exactly is wrong? Did I build a malfunctioning firmware? Did I mess up the DFU file? Is the configuration region to blame?