Differences

This shows you the differences between two versions of the page.

--- runtime_library:exceptions:start [2016/02/25 13:33] – external edit 127.0.0.1
+++ runtime_library:exceptions:start [2022/12/20 10:24] (current) – [Debug Mode on PowerPC Processors] ursgraf
@@ Line 4: / Line 4: @@
 ===== Exception Handling =====
-All unchecked Java exceptions must be caught by the system. In such a case, an string is written to the //System.err// stream. Make sure, that you have directed this stream to an existing serial interface.
+All unchecked Java exceptions must be caught by the system. In such a case, the type of the exception is written to the //System.err// stream. Make sure, that you have directed this stream to your ''System.out''.
-==== Example on the mpc555 ====
 <code java>
-  SCI1.start(9600, SCI1.NO_PARITY, (short)8);
-  System.out = new PrintStream(SCI1.out);
   System.err = System.out
 </code>
-==== Example on the mpc5200 ====
+Obviously you have to put the ''System.out'' onto an existing output stream, e.g. your standard output, see [[firstexample:start|Hello World with System.out]].
-<code java>
+===== Signaling with LED =====
-  UART3.start(9600, UART3.NO_PARITY, (short)8);
-  System.out = new PrintStream(UART3.out);
+==== Zynq7000 based boards ====
-  System.err = System.out
+On the [[https://wiki.bu.ost.ch/infoportal/embedded_systems/zynq7000/microzed|Avnet MicroZed board]] there is a single user LED on MIO47. On the [[https://wiki.bu.ost.ch/infoportal/embedded_systems/zynq7000/zybo|Digilent Zybo board]] we use the LED on MIO7.
-</code>
+^ blinking pattern ^ state ^ comment ^
+| 1x every second| code was loaded with error | FCS error in kernel |
+| 1x once | exception thrown in command | unchecked exception caught in //Task.loop// |
+| 2x once | exception thrown in command | unchecked exception caught in //Kernel.loop// |
+| 3x once | exception thrown in action method of task | unchecked exception caught in //Task.loop// or check stack failed in kernel|
+| 5x every second| exception thrown in boot method | unchecked exception caught in kernel |
+| 1x followed by 2x| data abort exception | memory access threw data abort exception |
-==== Signaling with LED ====
+==== PowerPC based boards ====
-On the [[http://wiki.ntb.ch/infoportal/embedded_systems/mpc555/headerboard/start|NTB MPC555 Headerboard]] there is a single LED. On the [[http://wiki.ntb.ch/infoportal/embedded_systems/mpc5200/start|Freescale MPC5200]] module there is no LED, but we use the one on the carrier board (at pin Gpio_Wkup_7).
+On the [[http://wiki.bu.ost.ch/infoportal/embedded_systems/mpc555/headerboard/start|NTB MPC555 Headerboard]] there is a single LED. On the [[http://wiki.bu.ost.ch/infoportal/embedded_systems/mpc5200/start|Freescale MPC5200]] module there is no LED, but we use the one on the carrier board (at pin Gpio_Wkup_7).
 ^ blinking pattern ^ state ^ comment ^
@@ Line 27: / Line 30: @@
 | 1x once | exception thrown in command | unchecked exception caught in //Task.loop// |
 | 2x once | exception thrown in command | unchecked exception caught in //Kernel.loop// |
-| 3x once | exception thrown in action method of task command | unchecked exception caught in //Task.loop//|
+| 3x once | exception thrown in action method of task command | unchecked exception caught in //Task.loop// or check stack failed in kernel|
-| 5x every second| Exception thrown | unchecked exception caught in kernel |
+| 5x every second| exception thrown | unchecked exception caught in kernel |
-| 1x followed by 2x every second| Machine Check Exception | bus error, PPC exception |
+| 1x followed by 2x every second| machine check exception | bus error, PPC exception |
-| 1x followed by 3x every second| System Call | sc-instruction, PPC exception |
+| 1x followed by 3x every second| system call | sc-instruction, PPC exception |
-| 1x followed by 4x every second| Floating Point Unavailable Exception | FPU switched off, PPC exception |
+| 1x followed by 4x every second| floating point unavailable exception | FPU switched off, PPC exception |
-===== Debug Mode =====
+===== Debug Mode on PowerPC Processors =====
 The RCPU of the mpc555 has a built-in debug feature. Some of the PPC exceptions can cause the processor to enter debug mode, instead of running the appropriate exception handler. However, this can happen only in case of the processor running out of RAM. If you run the program out of flash, you can never enter debug mode (which wouldn't make sense).\\
-Debug mode is indicated on the [[http://wiki.ntb.ch/infoportal/embedded_systems/mpc555/usb-bdi|MPC555 USB Background Debugging Interface (USB-BDI)]] with the blue LED.
+Debug mode is indicated on the [[http://wiki.bu.ost.ch/infoportal/embedded_systems/mpc555/usb-bdi|MPC555 USB Background Debugging Interface (USB-BDI)]] with the blue LED.

deep

User Tools

Site Tools

Differences

Page Tools