We're using Atmel/Microchip studio for compiling programs for the NetBurner (MODM7AE70).
The discover software can't upload a "foreign" binary file, but works fine if the binary file is generated by NNDK.
What do we need to do to make this compatible?
Using the web interface to load a "foreign" executable
-
jpelletier
- Posts: 18
- Joined: Wed Dec 23, 2020 3:32 am
Re: Using the web interface to load a "foreign" executable
The way the MODM7 is setup to boot via 2 stages with the embedded D20, this is not going to work.
The D20 makes sure the device is unbrick able. The format of the NetBurner binary file is not the same as the atmel tools.
It could probably be made to work by removing the D20 and using an external JTAG connection to the test connector,
but that modification would not be reversable and make the board no longer compatible with the NetBurner environment.
You would be much better off to use one of the SAME7 dev boards designed to work with the Atmel/Microchip tools.
If this is the reason you purchased this board you can return it for a Refund.
Given that what feature are missing from the Netburner environment that keeps it from working for you as is?
The D20 makes sure the device is unbrick able. The format of the NetBurner binary file is not the same as the atmel tools.
It could probably be made to work by removing the D20 and using an external JTAG connection to the test connector,
but that modification would not be reversable and make the board no longer compatible with the NetBurner environment.
You would be much better off to use one of the SAME7 dev boards designed to work with the Atmel/Microchip tools.
If this is the reason you purchased this board you can return it for a Refund.
Given that what feature are missing from the Netburner environment that keeps it from working for you as is?
-
jpelletier
- Posts: 18
- Joined: Wed Dec 23, 2020 3:32 am
Re: Using the web interface to load a "foreign" executable
"It could probably be made to work by removing the D20 and using an external JTAG connection to the test connector,
but that modification would not be reversible and make the board no longer compatible with the NetBurner environment."
That's what we did; by disconnecting the D20 by removing 4 resistors. It worked with a Netburner v1.4 but doesn't work with a Netburner v1.5.
See the Netburner Hardware forum for my post.
"Given that what feature are missing from the Netburner environment that keeps it from working for you as is?"
It would be advantageous for us to use the Netburner environment to be able to program the device though an ethernet connection, but we can't debug our application. Maybe we can port our soft to NNDK.
but that modification would not be reversible and make the board no longer compatible with the NetBurner environment."
That's what we did; by disconnecting the D20 by removing 4 resistors. It worked with a Netburner v1.4 but doesn't work with a Netburner v1.5.
See the Netburner Hardware forum for my post.
"Given that what feature are missing from the Netburner environment that keeps it from working for you as is?"
It would be advantageous for us to use the Netburner environment to be able to program the device though an ethernet connection, but we can't debug our application. Maybe we can port our soft to NNDK.