NetBurner Mod5282 Unresponsive

[hayedid]

My netburner worked great until last night. Now, I can no longer ping it or load software on it. I hooked it up to my serial port and it says the following:

Waiting 2sec to start 'A' to abort
Decomp Failed
No Valid app

Netburner MOD5282 Monitor V1.13 Dec 6 2005 14:35:59
HELP for help
nb>

It does not response to 'A' or 'HELP' or 'FLA'

As I understand it, there is a "serialload.exe' that is supposed to allow you to load new firmware on the board via the serial port ("Serial Update Tool"). However, the NNDK disk installed the link for this tool, but not the actual executable. Does anyone have this file or can you suggest another way to get my brick going again?

Thank you.

[Ridgeglider]

OK: make sure you are on the correct serial port at the right baud, stop, parity, etc. If in doubt, set up two serial ports and 2 instances of MTTTY so you connect to both the 5282 Com0 and Com1 ports. In rare situations, I have seen MTTTY lock up and require a reset of the host PC, but that is pretty rare and usually occurs if you are yanking a Serial/USB adapter in and out while connencted via MTTTY.

Next power the 5282 off. Wait 30 secs. Turn on caps lock on your PC (be sure it is on not off). Press and hold th A key. turn on the 5282. If this does not work, power off and try it on the MTTTY connected to the other 5282 Com port. If it still does not work, try repeating with the Caps Lock in the other state.

[greengene]

It looks like you corrupted you application in flash.
Here's an entry in the wiki that explains what to do to get your app reloaded:
http://wiki.embeddedethernet.com/Suppor ... _via_MTTTY

Also, take a look around the wiki in the Support FAQ for other pertinent info on this problem.

[MasterFrmMO88]

Not purposefully meaning to bring up an old topic but this is the only topic I could find with a similar problem.

I'm not sure, at all, what happened but one moment my MOD5270 was working fine then suddenly it wasn't appearing in my DHCP list. I hadn't flashed a new program on it or anything I had just changed some code on the computer side, in the program I am building to communicate with the NB Module. I went to test out the computer based program and started getting errors that it couldn't connect.

Now, while I can't figure out why it stopped working, I figured I'd just hook it up to the MTTTY and flash a new app on it so I could at least start getting a response again. I have done this before on a few occasions to fix Traps and such so I know it is connected the way it should be. Anyway here is the result:

Waiting 2sec to start 'A' to abort


Netburner MOD5270B Monitor V1.03 Feb 28 2011 08:51:04
HELP for help
nb>FLABegin Down load now.... (Any char but S to stop )
********************************************************************************
********************************************************************************
********************************************************************************
****************************************************Starting address = 02000000
S Record End detected

EWaiting 2sec to start 'A' to abort
Internal Error #DECE:FFF0C2F2
Decomp failed
No Valid app


Netburner MOD5270B Monitor V1.03 Feb 28 2011 08:51:04
HELP for help
nb>

This was just trying to Flash a simple APP to the module that was just created with Debug, and DHCP; without any extra code. I get the same result trying to Flash the FactoryDemo as well. Can anyone help me out with this?

[MasterFrmMO88]

Going to go ahead and update on my progress.

Not sure which step actually took care of it but I'll go ahead and post my steps and results. Maybe someone more well versed in this matter can point to which was the key and make the solution available for anyone else who might have a similar problem.

In my searching I found where someone had a similar problem and posted it on a different site. The reply seemed to be the Flash was somehow corrupted but still no fix was given.

Here's what I did:
Stopped the boot after a power cycle and setup a static IP.
Stopped the boot again and flashed the factory demo and got a response out of it, finally.
Flashed the initial program back onto the board that was giving the decomp error in the first place.
After that I was not longer receiving the decomp error but instead back to getting traps.
Undid the static IP so it would get an IP assigned to it and started getting traps shortly after the DHCP Request.
Looked into the program and noticed I was (for whatever reason) trying to run a command directly after the Debug check and Remarked that out.
Program seems to be working as it was before.

Again, not sure how I got over the initial Decomp Error but it seems to be working now so it must be somewhere in those first two steps. Unfortunately the only difference is assigning the static IP but I cant figure out how that would affect the Decomp Error.

Anyway, hope this helps anyone with this problem in the future!

[rnixon]

Do either of you have anything connected to the address or data bus? The decomp would fail if external h/w is driving these lines during boot.

Are you running the module in the NetBurner development board, or plugged into you own h/w? If you own h/w, what are you using for a power supply and what is its current rating? Needs to be 3.3V at 400mA or more. That would affect flash programming and boot.

I think that changing your PC program could indeed cause a trap in your NetBurner code because you could be exercising some part of the code differently. For example, sending a larger amount of data and overflowing a buffer in your code (this is just an example, not saying that is your problem).

Are either of you writing to the system flash parameters or user flash parameters immediately upon boot? That should be avoided because if someone cycles power quickly, or if your power supply isn't big enough, it could corrupt flash.

Just some ideas, hope it helps.

[tod]

Whenever you trap and do an automatic reboot and have problems flashing, always do a cold boot. Power down, power up and break into the monitor before the first trap can occur. I have had your problem in the past and this has always gotten me going again.

Also - in my opinion it's better to just start a new topic, bandwidth on this forum is reasonably low.