amigasociety wrote:I already have the internal cable as I paid for that option to be installed by AmigaKit but what I search for is what external cable do I now need to connect the X1000 to the SAM440ep and a more step by step for the extreme dummy on what else is needed to get the two to talk and the crash log to be sent to the SAM 440ep.
You need a "null modem" cable. You will also need a terminal program on your Sam440ep (sorry, can't help you there as I use PuTTY on my PC).
I assume that you want this to capture logs when the whole machine locks up. Otherwise grimreaper will allow you to save the log, or you could use dumpdebugbuffer. Anyway, the basic procedure is as follows:
- Redirect the debug stream to the serial port
- Start the terminal program on your Sam440ep (or whatever machine you're using to capture the data)
- Run the program that crashes
- Save the resulting crash log that has been captured on the other machine
- Submit the crash log
There are two ways to redirect the debug stream to serial:
- In CFE, set the os4_commandline ENV var to "serial", and then boot
e.g., setenv os4_commandline "serial"
- In AmigaOS4, execute:
kdebug "console serial"
I'm not sure that the kdebug command will work properly on the A1-X1000. When I tried it, this caused a lockup itself. Since then I enable serial debug logging in CFE. I recommend that you only enable serial logging when needed, because it will slow your machine down whenever data is being dumped to debug. On my machine I have created a second CFE menu entry which boots AmigaOS with serial debug logging enabled.
amigasociety wrote:Then once this happens, is there a proper channel to report these crash logs in hopes it will help others update their apps.
Example, when running TuneNet and Timberwolf, lock ups for me happen all the time. Would love to channel that info to folks that can use it.
Bug reports and crash logs for TuneNet and Timberwolf should be submitted to
http://bugs.os4depot.net/.
Hans