• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 21 subscribers
  • Views 3124 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

    Moshe,
    I am working on a USB bootloader not operating with the presence of RTX. Please see here for a short description of my problem:
    http://www.keil.com/forum/docs/thread14069.asp
    I don't understand why using on chip peripherals prevents the application code from being interrupted. I see that the jump to application works, but if I dare to do it with a timer running of USB - the application will not get interrupted. the weird thing is that older revision of the code did not have that, but I don't see how a simple change in startup in main() can give me such a headache. Any ideas?

Reply
  • 0 in reply to mo tal

    Moshe,
    I am working on a USB bootloader not operating with the presence of RTX. Please see here for a short description of my problem:
    http://www.keil.com/forum/docs/thread14069.asp
    I don't understand why using on chip peripherals prevents the application code from being interrupted. I see that the jump to application works, but if I dare to do it with a timer running of USB - the application will not get interrupted. the weird thing is that older revision of the code did not have that, but I don't see how a simple change in startup in main() can give me such a headache. Any ideas?

Children
No data