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

Code Load With ULINK Very Slow

When loading code via ULINK USB (not burning the flash) the load takes approx 5 minutes for a 300K file. What does the LOAD command do and why does it take so long when we are not burning the FLASH?

Parents
  • Thanks for the files, now I know what is going on.

    Since your application is already in flash and you have switched off the option 'Verify Application in ROM', the debugger load the application almost instantly. You see the load-progress-bar only one or two seconds.

    After that, the uVision target debugger needs to analyze the code to find ATOMIC and EXTx instructions. Therefore the complete code needs to be read. Since you have disabled all cache options in the Target Driver Setup dialog, the code needs to be read from the target system. This is where time is wasted. Please enable at least the option 'Ignore Code Modifications'. With this option set, the debugger starts in two seconds. As long as there is no good reason, I would enable all cache options.

Reply
  • Thanks for the files, now I know what is going on.

    Since your application is already in flash and you have switched off the option 'Verify Application in ROM', the debugger load the application almost instantly. You see the load-progress-bar only one or two seconds.

    After that, the uVision target debugger needs to analyze the code to find ATOMIC and EXTx instructions. Therefore the complete code needs to be read. Since you have disabled all cache options in the Target Driver Setup dialog, the code needs to be read from the target system. This is where time is wasted. Please enable at least the option 'Ignore Code Modifications'. With this option set, the debugger starts in two seconds. As long as there is no good reason, I would enable all cache options.

Children