Serial Flash Loading Fails Everytime MOD54415

[cfavreau]

I am trying to troubleshoot why my MOD54415 cannot be programmed through AutoUpdate anymore. I was in the middle of trying to get the debugging working and it now stops. I can still ping the board using my Windows XP computer. If I use MTTY to login to the board and press the A key to get the 'nb' prompt everything works. The first issue is there is no prebuilt factory application as the "RestoreModuleToFactorySettings.pdf" document says. I looked in the C:\nburn\MOD5441X folder and I looked on the http://www.netburner.com/resources page and I cannot find it. I was working with it in NBEclipse before the board stopped uploading so I am try to use the MOD54415FactoryApp_APP.s19 file that was created in the Release folder. That application worked so I thought I would start with that.

Now that I have the factory application I tried the "fla" command at the prompt and everything appears to go well except that at the end (or towards the end) of the download I get kicked back to the nb prompt and it says that the download failed. Not matter what application I try it says that the download fails despite getting a lot of * printed to the screen. I tried Help and found the un WriteProtect command however it says that it does not recognize that command or the WriteProtect command (not sure why).

Is there a new procedure with the MOD54415 boards?

Thanks,
Chris Favreau

[cfavreau]

Small Update:

The only way I have found to get something working again is to use MTTY to get the NB prompt and to use AutoUpdate to load the factory application... it only worked from Eclipse though. Using the standalone AutoUpdate in this manner appeared to work however upon reset the factory program was not there.

[rnixon]

Check your settings (type "setup" from NB> prompt) to see if you have "boot to application" selected rather than "boot to monitor". When you use "fla", are you sure you are using the _APP.s19 file and not just the .s19 file?

[cfavreau]

I checked to make sure the setup says "Boot To Application" and... yes I am sure I am using the _APP.s19 file. I tried the plain old .s19 file and that did not work either.

I tried my other board and that one appears to go as planned after having to wait for the DHCP to do something...

So.. I think I have it figured out.

My other board that I have not touched until now... is configured stock ... its IP is 0.0.0.0 and netmask is 0.0.0.0... so my other board is configured as 192.168.0.101 255.255.255.0 so I set my non-working board to 0.0.0.0 and 0.0.0.0... and it programs using the FLA command.

Can someone else try this out to see if I am totally bonkers or if this is what is happening?

Thanks,
Chris F.

[rnixon]

That doesn't seem to make sense. What is the address/mask of your PC?

What is the address/mask assigned by DHCP to the netburner?

[cfavreau]

The address of my PC is 192.168.0.100 and the mask is 255.255.255.0... however I fail to see why it matters when I am using the serial console and trying to do an operation that "should" depend only on my serial port connection and not the network connection. I think it is probably just a bug in the MOD54415's monitor program.

I am not using DHCP at all as I am using the red network crossover cable so the DHCP client does not set an IP address. I have to wait for it to timeout before it allows me to get to the "nb" monitor prompt using the "A" key.

Has anyone tried this with their MOD54414 development board?

[tod]

Yes, I just tried it on my MOD54415 dev board. I took a powered down unit, connected the USB cable. Connected with MTTY. Hit the Reset button, hit SHIFT-A to get to

Code: Select all

nb> Welcome to the Netburner Alternate Boot Monitor   Command Program
NetBurner MCF5441x Alternate Image Monitor V1.00 May 29 2002 15:25:39
Help for help
nb>

I then Entered FLA and selected the _APP.s19 file for the factory demo. The asterisks went flying across the screen. Right at the end of the asterisks I saw "ErasWaiting 5 sec to start 'A' to abort. So the only anomaly was there appeared to be a cut off message "Eras" but the APP file loaded and the unit booted correctly afterwards.

Tod

[cfavreau]

Thanks for the reply. Are you using a static IP address?

I get the same thing when my IP address that is programmed in is 0.0.0.0 however when I use 192.168.0.101 as my UP address I get all the same except after all the *'s fly by I get a failed message.

[pbreed]

Trying to understand this a few questions....

1)Does it do this with the ethernet cable unplugged?

2)When you set the IP address did you do it via the monitor or via the ipsetup utility?

3)Another useful piece of info is does it do this at 57600 instead of 115200?

4)Are you using the USB port or the DB9 port?

5)Is ANY thing attached to the other serial port(s)?

6)If you try a DIFFERENT static IP address does it still fail?

7)IF the answer to #6 is no, is there something else trying to talk to this address while the FLA is running?


The FLA code for the MOD5441X and NANO54415 are 100% different from the FLA code in a normal netburner.
I have no idea what is wrong, but it would not shock me that some combination of your setup could be doing weird things.

I want to hunt this one down and kill it, given that, I also understand that you want to git back to work, so I ask
since one of the really cool things about the MOD5441X and NANO54415 is that you can always use autoupdate why
are you even messing with the serial port?

[cfavreau]

I will get some answers to your #1 to #6 shortly.

I am using the serial port because AutoUpdate does not "always" work and IPSetup did not work in the beginning. And the big positive is that I can use printf's for debugging. I have been able to bugger the system up where AutoUpdate does not work... some how some combination of not compiling in the EnableAutoUpdate() function call and trying to get debugging to work. It is much better now however when I first started a few days ago I had to reflash it a few times.

Still the serial port is useful for debugging.

Thanks!