NetBurner Community Forum

Your doc link is the page I have been using. And no, there was no .bin file created when the app was built by Eclipse, only .s19, .elf, and .map files.

This looks like a problem on our side that we missed in testing. Its not an issue if you build and download from Eclipse, or build and download from the command line. But if you make a project in Eclipse and look for the file to download manually, the application image will be named test.bin (or test_APP.s19 if you have the s19 option enabled. This was caused by the way we tested builds when enablling making a _APP.s19 file in Eclipse.

If you look in your project's release folder, is there a test.bin file?

Yes, there is a test.bin file. Size is 260-bytes.

That sounds too small. Here is a .bin file you can use for ShowInterfaces example. Since we are seeing different things, the next step is probably a video call so we can go through it together. Please try the attached, and open a support ticket so I can schedule a time to meet.

I'll try it, but I read the size wrong. It's 260k bytes.

That actually sounds right. Did you try it?

When I use nbupdate to load the test.bin file you sent, I get the following output in MTTTY:

Header Checksum good
Loading 271067
Download Complete...
Programming complete reboot in 5 sec
Waiting 2sec to start 'A' to abort

Then nothing happens. It just sits and the Waiting message. All those messages happen almost instantly. Autoupdate always took several seconds to download and much longer to program. Is it really that fast?

When I load my test.bin file, I get the same first 3 messages above (Header check, Loading, Download), then nothing. Just sits there.

Does it show up in discover.netburner.com?