Other Parts Discussed in Thread: HALCOGEN
Hello all,
I have problems to add an bootloader to an existing project on a on a TMS570LS1224. Before adding the bootloader the application it self was running without any problems for 2 years now.
Now I have a problem to start the application from a bootlader . After I jumped to the application I end up in the undefEntry which is a endless loop in my case.
For both bootloader and application I use the same Halcogen configuration but different linker scripts of cause. Before jumping to the application I de initialize all used modules and I disable all interrupts with _disable_interrupts_. For the bootloader the F021 API is configured to run from RAM and I copy it from FLASH to RAM in the bootloaders reset handler (_bl_c_init_00) just before calling bootloaders bl_main(). After that I'm able to write to the FLASH and EEPROM. For the application the F021 API remains in FLASH since I only write to the EEPROM from there.
To analyze my problem I flashed both bootloader and application via JTAG. When I now debug the bootloader and do the jump to the application i reach the applications reset handler _c_init_00() and finally applications main(). Now everything seems to work fin until I enable Interrupts again by calling _enable_interrupts_. Either immediately or after a few further steps I end up in the bootloaders undefEntry. The link register always points to the RAM where the F021 API was located for the bootloader.
I guess I have some misconfigured interrupt handler in the VIM. Now my question is how I can determine which interrupt causes the problem.
Kind regards
Jens