Hi dear ARM fellows,
Firstly, let me introduce the context. I am developping a RTX/RL software for a custom board based on a LPC2388 µC. I was using an old version of MDK-ARM and RL-ARM to develop the bootloader and the user app, everything was working well until we bought the new MDK-ARM Pro to add the FTP functionality.
With this latest version, I am experiencing weird behaviors, all related to os_xxx function calls. For example, os_itv_wait() and os_dly_wait() did not trigger the task at the programmed amount of time. Now my software hangs on the first os_mut_wait call, but I've checked that all is well declared and initialized and anyway, the mutex is not used as this is the first call to a mutex in my program.
After a week of debugging and trying to understand what is happening, I erased my bootloader and configured my user app to load at 0x00 and then... gotcha ! Everything is working as expected but it is really annoying that I can't use my bootloader anymore.
This bootloader is written from the SD card example provided in NXP's application note AN10835. I generate the .bin file from the .axf outputed by µvision with the fromelf utility located in C:\Keil\ARM\ARMCC\bin. Previously I was using the fromelf located in C:\Keil\ARM\BIN40 but it doesn't work with the latest version of MDK-ARM.
At this point, I am suspecting fromelf to not perform the job as intended. I opened a support ticket with Keil but I would like to ask you, guys, if someone using a bootloader has experienced the same kind of issues and if they found a workaround.
Best regards.