| Line 202... |
Line 202... |
| `-nostartfiles` | Do not use the default start code. The makefiles use the NEORV32-specific start-up code instead (`sw/common/crt0.S`).
|
| `-nostartfiles` | Do not use the default start code. The makefiles use the NEORV32-specific start-up code instead (`sw/common/crt0.S`).
|
| `-Wl,--gc-sections` | Make the linker perform dead code elimination.
|
| `-Wl,--gc-sections` | Make the linker perform dead code elimination.
|
| `-lm` | Include/link with `math.h`.
|
| `-lm` | Include/link with `math.h`.
|
| `-lc` | Search for the standard C library when linking.
|
| `-lc` | Search for the standard C library when linking.
|
| `-lgcc` | Make sure we have no unresolved references to internal GCC library subroutines.
|
| `-lgcc` | Make sure we have no unresolved references to internal GCC library subroutines.
|
| `-mno-fdiv` | Use builtin software functions for floating-point divisions and square roots (since the according instructions are not supported yet).
|
| `-mno-fdiv` | Use built-in software functions for floating-point divisions and square roots (since the according instructions are not supported yet).
|
| `-falign-functions=4` .4+| Force a 32-bit alignment of functions and labels (branch/jump/call targets). This increases performance as it simplifies instruction fetch when using the C extension. As a drawback this will also slightly increase the program code.
|
| `-falign-functions=4` .4+| Force a 32-bit alignment of functions and labels (branch/jump/call targets). This increases performance as it simplifies instruction fetch when using the C extension. As a drawback this will also slightly increase the program code.
|
| `-falign-labels=4`
|
| `-falign-labels=4`
|
| `-falign-loops=4`
|
| `-falign-loops=4`
|
| `-falign-jumps=4`
|
| `-falign-jumps=4`
|
|=======================
|
|=======================
|
| Line 542... |
Line 542... |
|=======================
|
|=======================
|
| **`ERROR_0`** | If you try to transfer an invalid executable (via UART or from the external SPI flash), this error message shows up. There might be a transfer protocol configuration error in the terminal program. Also, if no SPI flash was found during an auto-boot attempt, this message will be displayed.
|
| **`ERROR_0`** | If you try to transfer an invalid executable (via UART or from the external SPI flash), this error message shows up. There might be a transfer protocol configuration error in the terminal program. Also, if no SPI flash was found during an auto-boot attempt, this message will be displayed.
|
| **`ERROR_1`** | Your program is way too big for the internal processor’s instructions memory. Increase the memory size or reduce your application code.
|
| **`ERROR_1`** | Your program is way too big for the internal processor’s instructions memory. Increase the memory size or reduce your application code.
|
| **`ERROR_2`** | This indicates a checksum error. Something went wrong during the transfer of the program image (upload via UART or loading from the external SPI flash). If the error was caused by a UART upload, just try it again. When the error was generated during a flash access, the stored image might be corrupted.
|
| **`ERROR_2`** | This indicates a checksum error. Something went wrong during the transfer of the program image (upload via UART or loading from the external SPI flash). If the error was caused by a UART upload, just try it again. When the error was generated during a flash access, the stored image might be corrupted.
|
| **`ERROR_3`** | This error occurs if the attached SPI flash cannot be accessed. Make sure you have the right type of flash and that it is properly connected to the NEORV32 SPI port using chip select #0.
|
| **`ERROR_3`** | This error occurs if the attached SPI flash cannot be accessed. Make sure you have the right type of flash and that it is properly connected to the NEORV32 SPI port using chip select #0.
|
|
| **`ERR 0x???????? 0x???????? 0x????????`** | The bootloader encountered an exception during operation. This might be caused when it tries to access peripherals that were not implemented during synthesis. Example: executing `l` or `s` (SPI flash operations) without the SPI module beeing implemented.
|
|=======================
|
|=======================
|
|
|
|
|
|
|
|
|
| Line 578... |
Line 579... |
handlers.
|
handlers.
|
|
|
After the initial setup of the RTE, each entry in the trap handler's look-up table is initialized with a debug
|
After the initial setup of the RTE, each entry in the trap handler's look-up table is initialized with a debug
|
handler, that outputs detailed hardware information via the **primary UART (UART0)** when triggered. This
|
handler, that outputs detailed hardware information via the **primary UART (UART0)** when triggered. This
|
is intended as a fall-back for debugging or for accidentally-triggered exceptions/interrupts.
|
is intended as a fall-back for debugging or for accidentally-triggered exceptions/interrupts.
|
For instance, an illegal instruction exception catched by the RTE debug handler might look like this in the UART0 output:
|
For instance, an illegal instruction exception caught by the RTE debug handler might look like this in the UART0 output:
|
|
|
[source]
|
[source]
|
----
|
----
|
Illegal instruction @0x000002d6, MTVAL=0x00001537
|
Illegal instruction @0x000002d6, MTVAL=0x00001537
|
----
|
----
|
