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

Must build restricted module to get around bug - ?

I am using the Cypress EZUSB system with the Keil compiler(compiler 6.10, linker 4.03). When trying to debug the ISOSTRM sample app, I got the infamous 'MONITOR ERROR 22:NO CODE MEMORY AT ADDRESS 0045H' message.

The app note at http://www.keil.com/support/docs/863.htm told me to hack the USBJmpTb.a51 file and rebuild. I did so, then discovered I also needed to rebuild the monitor to apply the changes. I rebuilt in %CYUSB%\Target\fw\FX2 and got the linker error L251. The man page @ http://www.keil.com/support/docs/1827.htm tells me to use the full version of the Keil product to rebuild. I don't have the full version.

Is there another way around this BUG??

Eric

Parents
  • And while we're engaging in irrelevancies: the common English word for someone that tries to provoke flames is "troll", same as the mythological monster. "Trollop" means "prostitute".

    --

    To get back on topic, any thoughts on Eric's problem? "Buy the full version" of course solves the problem. But it does seem like the eval version ought to be capable of modifying the sample apps so that you can evaluate the tools on your particular target hardware.

Reply
  • And while we're engaging in irrelevancies: the common English word for someone that tries to provoke flames is "troll", same as the mythological monster. "Trollop" means "prostitute".

    --

    To get back on topic, any thoughts on Eric's problem? "Buy the full version" of course solves the problem. But it does seem like the eval version ought to be capable of modifying the sample apps so that you can evaluate the tools on your particular target hardware.

Children