|
I'm programming an lcp2106 with the IAR tools and J-Link, and program
was dieing. As a check I turned on JLink's ability to verify a flash download by reading it back and comparing. The verification fails with a series of errors like this: Target inconsistency detected at memory address 0x000000F9 Target inconsistency detected at memory address 0x00000024 Target inconsistency detected at memory address 0x00000028 Target inconsistency detected at memory address 0x000000FC Target inconsistency detected at memory address 0x00000101 Target inconsistency detected at memory address 0x00000104 Target inconsistency detected at memory address 0x0000012C Target inconsistency detected at memory address 0x00000110 Target inconsistency detected at memory address 0x00000020 Target inconsistency detected at memory address 0x00000070 Target inconsistency detected at memory address 0x000000A8 Target inconsistency detected at memory address 0x000000D4 Target inconsistency detected at memory address 0x00000121 These are always in the same place in memory. I lowered the JTAG speed to minimum, and this did not help, and the errors stayed exactly the same. I also switched between ARM the THUMB mode and they stayed the same. It's a new chip, and other big programs that I've downloaded with Philips downloader run fine. I don't have another chip handy to do a comparison. Is this likely to be faulty flash memory? How often does this happen in new chips? Could it be a power supply problem? (although the voltages seem correct) Thanks for any advice you can offer. - Chris Graham |
|
|
JTAG Download Errors
Started by ●June 22, 2004
Reply by ●June 22, 20042004-06-22
|
--- In , "Chris Graham" <chris_e_gr@y...> wrote: > I'm programming an lcp2106 with the IAR tools and J-Link, and program was > dieing. As a check I turned on JLink's ability to verify a flash download > by reading it back and comparing. > > The verification fails with a series of errors like this: > > Target inconsistency detected at memory address 0x000000F9 > Target inconsistency detected at memory address 0x00000024 > Target inconsistency detected at memory address 0x00000028 > Target inconsistency detected at memory address 0x000000FC > Target inconsistency detected at memory address 0x00000101 > Target inconsistency detected at memory address 0x00000104 > Target inconsistency detected at memory address 0x0000012C > Target inconsistency detected at memory address 0x00000110 > Target inconsistency detected at memory address 0x00000020 > Target inconsistency detected at memory address 0x00000070 > Target inconsistency detected at memory address 0x000000A8 > Target inconsistency detected at memory address 0x000000D4 > Target inconsistency detected at memory address 0x00000121 > > These are always in the same place in memory. I lowered the JTAG speed to > minimum, and this did not help, and the errors stayed exactly the same. I > also switched between ARM the THUMB mode and they stayed the same. > > It's a new chip, and other big programs that I've downloaded with Philips > downloader run fine. I don't have another chip handy to do a comparison. > > Is this likely to be faulty flash memory? How often does this happen in new > chips? Could it be a power supply problem? (although the voltages seem > correct) > > Thanks for any advice you can offer. > > - Chris Graham I had similiar problems with IAR,Jlink and the 2106 I found that if you had code in the 2106 flash with the PLL enabled I would get similiar problems as above. In order to program the flash/debug with Jlink the 2106 flash had to be blank or running code without the PLL enabled. Also make sure in the debugger options for Jlink you have - 1. philips LPC flash download ticked. 2. reset asserts hardware reset pin ticked. In the general options target - 1. The chip radio button is selected with the lpc2106.i79 file with all this done and after many days of frustration I'm now happily using Jlink to debug Doug |
|
|
Reply by ●June 23, 20042004-06-23
|
Thanks Doug!! I've been struggling for days to get it to run, and
finally it does :-))) . I had overlooked setting "reset asserts hardware reset" . IAR should really document this better given how popular the 21xx chips are. - Chris > > > I had similiar problems with IAR,Jlink and the 2106 > > I found that if you had code in the 2106 flash with the PLL enabled I > would get similiar problems as above. In order to program the > flash/debug with Jlink the 2106 flash had to be blank or running code > without the PLL enabled. > > Also make sure in the debugger options for Jlink you have - > > 1. philips LPC flash download ticked. > > 2. reset asserts hardware reset pin ticked. > > In the general options target - > > 1. The chip radio button is selected with the lpc2106.i79 file > > with all this done and after many days of frustration I'm now happily > using Jlink to debug > > Doug |
Reply by ●June 23, 20042004-06-23
|
I have installed IAR EWARM 3.40, which should have support for Macraigor RAVEN JTAG. When I lauch C-SPY debugger with the JTAG setup configured, the code downloads correctly and when the application starts it jump to the main function. The problem is, when I go step by step with the debugger, I get an error ("macraigor driver error") saying that only to breakpoints can be set in ROM. Could anybody explain me how to download the code in RAM instead of ROM (perhaps with a linker file example) or what to in order to put several breakpoints in my code with the IAR IDE? Thank you very much. Regards, Tsim |
