I'm evaluating the Demo version of the ARM7 tools from Keil and notice a lot of unusual quirkiness when dealing with the Flash erase procedure called out in Philips' IAP section. Many times I've had to power down the eval MCB2100 board, constantly re-enter Debug mode, do the hokey-pokey, etc. to re-establish the code and get it to run. On one occasion, I had put into the Memory Window address 0xFFFFF030 (or any other address from the Vectored Interrupt Controller (VIC)) and my target just froze up. Anyone else experiencing strange stuff with this eval board and ARM7 tools? Thanks.
Hi, use the Philips ISP Tool to get the version. What LPC device is mounted on the MCB2100 a LPC2129??? Andreas
Please see my relpy just above. Is the problem in the version (1.5) of Bootloader? Thanks, -Jim
Sorry, but I did not got this email. Please send it to: support.intl@keil.com
Hi, I got the information from Philips that some of the early devices had a problem with the bootloader and flash. If you use the ISP tool from Philips to get the device ID successfully and it hang when you try to erase or program the device it seems that your device had a problem. Then you can still use the Ulink programming the flash directly (without using the IAP functions) or get a replacement of the device. Andreas
I have your code working (basically you need to initialize the lCommand struct to 0). I will send it via email.