Hyperion Entertainment Message Boards

When my X1000 crashes and locks up is there anything that I can be running in the background to see what caused the error? Sometimes the whole system will lock - without a guru - and it would be interesting if I could see what the problem was. Foe example - just now I have been running the latest Timberwolf and Tunenet - switched on from cold boot and the whole system locked after 5 minutes. Could be the Timberwolf beta (back on OWB now) - but would be good to have an error log to see what caused the problem.

Yes!
I have a Micro-AmigaOne running in the background, connected to the X1000 by serial cable.

With "Term" running on the Micro, and 'setenv os4_commandline "DEBUGLEVEL=5 SERIAL" ' somewhere in the CFE command structure,
The Micro will spew lots of interesting data on every crash.

If you're in a really bad spot, you could probably use a windows machine to catch the debug stream, but somehow that seems ugly.

Have Fun!

Thanks for the advice. Having another Amiga attached would be nice but unfortunately I don't have one. Now that the serial port work s on the X1000 though I could point this to a PC.

Sam wrote:Thanks for the advice. Having another Amiga attached would be nice but unfortunately I don't have one. Now that the serial port work s on the X1000 though I could point this to a PC.

Axctually the serial port already worked for capturing serial dumps. The new serial driver was for use of the serial port under AmigaOS 4.

Trevor

LyleHaze wrote:Yes!
I have a Micro-AmigaOne running in the background, connected to the X1000 by serial cable.

With "Term" running on the Micro, and 'setenv os4_commandline "DEBUGLEVEL=5 SERIAL" ' somewhere in the CFE command structure,
The Micro will spew lots of interesting data on every crash.

If you're only interested in the crash log, then you can drop the "DEBUGLEVEL=5" and go with just "SERIAL".

Hans

I use a USB2Serial adapter with the serial end attached to the X1000 debug serial port, and the USB end attached to my PC running windows.
Program I use is PuTTY which works sufficiently well.

Settings in PuTTY:
1. Connection type: Serial
2. Serial line: COMx (Where x is the number of the COM port, can be identified from Control Panel->System, e.g. COM4)
3. Baud rate 115200 (default value from X1000)
4. Set option: Terminal->Implicit CR on every LF
5. Set option: Window->Lines on Scrollback (to a larger value, e.g. 200000)
6. Save the session under a new name!

Would'nt it be easier for the user to boot from CD and then test that way.
If no crashes happen, that will rule out HW and you can then start looking at SW issue (i.e. Debug).