• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 21 subscribers
  • Views 3119 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LPC2368 bootloader and RL-ARM

julien M

Hello,

I developped an usb bootloader which works perfectly when I use an simple firmware, but which doesn't works with an firmware using RTX kernel.

Anyone can help me ?

Thanks

Parents
  • 0 in reply to mo tal

    This is strange, I still dont understand why this is occurring.

    1. The new code that I download (using my bootloader via USB) is built with the RTX kernal.

    2. If my bootloader is built with an RTX then I can boot the new code correctly.

    3. If my bootloader is built without an RTX then Im unable to boot the new code.

    4. Both bootloaders (with or without an RTX) will execute code (that contains no RTX) correctly.

    In both cases the new code starts at address 0x5000 and has the correct options in the startup file.

    Any ideas why?

Reply
  • 0 in reply to mo tal

    This is strange, I still dont understand why this is occurring.

    1. The new code that I download (using my bootloader via USB) is built with the RTX kernal.

    2. If my bootloader is built with an RTX then I can boot the new code correctly.

    3. If my bootloader is built without an RTX then Im unable to boot the new code.

    4. Both bootloaders (with or without an RTX) will execute code (that contains no RTX) correctly.

    In both cases the new code starts at address 0x5000 and has the correct options in the startup file.

    Any ideas why?

Children