... | @@ -65,6 +65,15 @@ A Perspective rearranges the Elements of the IDE specific for a special task. Wh |
... | @@ -65,6 +65,15 @@ A Perspective rearranges the Elements of the IDE specific for a special task. Wh |
|
The build of your code failed - so there is no binary, hence it can not be found by the debugger. Fix the error(s) in your code until it compiles. Then repeat.
|
|
The build of your code failed - so there is no binary, hence it can not be found by the debugger. Fix the error(s) in your code until it compiles. Then repeat.
|
|
{blank}
|
|
{blank}
|
|
|
|
|
|
|
|
== I get the message "ios.family.arm.m3.Hwi: line 143: E_alreadyDefined: Hwi already defined: intr# <some interrupt number>" - what's wrong?
|
|
|
|
You are mixing interrupt handling of an RTOS driver with manual HWI handling (setting up HWIs manually + setting up the underlying peripheral interrupts via driverlib or direct register writes).
|
|
|
|
|
|
|
|
For example, you want to set up an HWI for an input pin without using `GPIO_enableInt()` etc., but still call the RTOS' `Board_initGPIO()` (or `GPIO_init()`), e.g., to be able to use `GPIO_write()` to toggle the LEDs.
|
|
|
|
This cannot work because the GPIO driver sets up HWIs for all pins if enabled.
|
|
|
|
|
|
|
|
In general you should use either the RTOS driver for a peripheral (strongly recommended if available!) or handle all related programming including interrupt configuration manually.
|
|
|
|
{blank}
|
|
|
|
|
|
== I get a message similar to "error #10099-D: program will not fit into available memory. run placement with alignment fails for section ".vtable" size 0x26c , overlaps with ".vecs", size 0x360 (page 0)" - what's wrong?
|
|
== I get a message similar to "error #10099-D: program will not fit into available memory. run placement with alignment fails for section ".vtable" size 0x26c , overlaps with ".vecs", size 0x360 (page 0)" - what's wrong?
|
|
If you are using the TI-RTOS then it is likely you have tried to register an interrupt handler by using one of the `*IntRegister()` functions of the TivaWare library.
|
|
If you are using the TI-RTOS then it is likely you have tried to register an interrupt handler by using one of the `*IntRegister()` functions of the TivaWare library.
|
|
Since the RTOS handles interrupts itself using these functions is incompatible with it - avoid that and use the respective driver or set up an HWI instead.
|
|
Since the RTOS handles interrupts itself using these functions is incompatible with it - avoid that and use the respective driver or set up an HWI instead.
|
... | | ... | |