NetBurner Community Forum

For the Mod5234, the application wizard has these options grayed out: 'Serial Load" and 'Serial Debugging". We have an application for which we do not plan to use networking. Is it possible to do serial debugging instead of network debugging on this platform anyway? Is it restricted by the boot loader on this target?

-Chuck

How about making a very short cable that connects from the ethernet header to an ethernet jack? You should have plenty of room, so even if you don't use networking it could still be active for debugging.

That's a possibility and we're looking into that. Not sure about the ethernet magnetics. I was wondering if serial debugging could be used with 5234 even though the new project application wizard has it disabled. It would seem the monitor would need to support downloading the image and maybe that support is only enabled in the 5213. It would be useful to have this option available on the other platforms.

If its disabled, its probably for a reason.
The magnetics are inside the Ethernet jack, so if you purchase the jack from netburner all you should need to do is hook it up. Theres even an app note on how to connect the jack to the mod5234-200:
http://www.netburner.com/downloads/modu ... Design.pdf

I would have to think this would be easier and more reliable than trying to force the tools or s/w to do something it was not designed to do.

Thanks for the tip. Ethernet support also adds to the size of the image. I'd still like to know if the serial debugging is a possibility on the 5234 platform.

You certainly can download over the serial port - I have, when I've munged my app badly enough! Simply downloading over the serial port to the monitor is unaffected by project settings.

Sorry, don't know about the debugging question, though...

Serial app updating is possible via the monitor.

Serial debugging is not recommended.

A very long time ago we had some serial GDB stub's, that did serial debugging.
They were the #1 source of support problems. We have not tested them in a very long time.
I'd be much more inclied to write specific informational dump commands than a serial debugger.

The Serial Debug options in eclipse are for the non network platforms (MOD5213)

Paul

I did manage to get command line gdb working via serial connection using the instructions in NetBurnerTools.pdf. First I did the Serial Connection Test. With that cleared up, I then followed the serial debugging instructions closely, including using baud 57600.

I was not able to get the NBEclipse debugger connection to work using the "SpeedSerial" connection. It doesn't automagically download the image the way it does with Network connection. I do have an image with the serial debug stub loaded on the target, so that is not the issue. If it works with the 5213, I bet it wouldn't take much to get it working with the 5234.

I can use command line gdb in a pinch, but the Eclipse interface is much nicer with the full screen graphical display. Debugging via printf is always a dependable fall back but there's nothing like a debugger for troubleshooting crashes.