EmbeddedRelated.com
Forums
The 2024 Embedded Online Conference

LPC2148 troubleshooting

Started by Sumit Bhatnagar February 23, 2009
I am getting the following message while loading my code to the LPC2148
using JTAG.

Warning: Target inconsistency detected in Memory range 0x00000000-
0x0000003F

Any idea of why this might happen.

Best Regards,
Sumit

An Engineer's Guide to the LPC2100 Series

>From where do you get the message? My guess is it's complaining about a
bad value in the checksum vector.

-----Original Message-----
From: l... [mailto:l...] On Behalf
Of Sumit Bhatnagar
Sent: Monday, February 23, 2009 6:41 PM
To: l...
Subject: [lpc2000] LPC2148 troubleshooting

I am getting the following message while loading my code to the LPC2148
using JTAG.

Warning: Target inconsistency detected in Memory range 0x00000000-
0x0000003F

Any idea of why this might happen.

Best Regards,
Sumit



I am using the Wiggler JTAG. Debugging using the IAR with HJTAG server.

This is the warning message I recieve when I start debgging. The LPC2148 seems to be locked in some mode.

The code I was able to execute earlier is no longer working. I have recycled power to the board.
The HJTAG recognizes the chip and the board powers-up but it appears that I am not able to reset the board using HJTAG.

Thanks and Regards,
Sumit.
>From where do you get the message? My guess is it's complaining about a
bad value in the checksum vector
Is there a way of resolving the checksum error if the LPC2148 is locked with it??
>I am getting the following message while loading my code to the LPC2148
>using JTAG.
>
>Warning: Target inconsistency detected in Memory range 0x00000000-
>0x0000003F
>
>Any idea of why this might happen.
>
>Best Regards,
>Sumit
>
>
I'm not familiar with the message, and I don't know what board your
LPC2148 is soldered on. You probably have the on-chip ISP boot loader
available. If so, boot the chip into the ISP, and reconnect. If IAR
offers a simulated reset vector catch, you could set that up before you
connect. Alternatively, set a break to stop execution at a known safe
location in your code. If you don't know, start at the reset vector.
Proceed from there to see if your application is doing something
untoward.

-----Original Message-----
From: l... [mailto:l...] On Behalf
Of s...@yahoo.com
Sent: Monday, February 23, 2009 7:10 PM
To: l...
Subject: [lpc2000] Re: LPC2148 troubleshooting

I am using the Wiggler JTAG. Debugging using the IAR with HJTAG server.

This is the warning message I recieve when I start debgging. The LPC2148
seems to be locked in some mode.

The code I was able to execute earlier is no longer working. I have
recycled power to the board.
The HJTAG recognizes the chip and the board powers-up but it appears
that I am not able to reset the board using HJTAG.

Thanks and Regards,
Sumit.

>From where do you get the message? My guess is it's complaining about a
bad value in the checksum vector
Is there a way of resolving the checksum error if the LPC2148 is locked
with it??

>I am getting the following message while loading my code to the LPC2148

>using JTAG.
>
>Warning: Target inconsistency detected in Memory range 0x00000000-
>0x0000003F
>
>Any idea of why this might happen.
>
>Best Regards,
>Sumit
>
>



Steve, Thanks for your inital suggestion. I ended up erasing the flash and loading the code to flash. Now it appears the USB mouse demo code seems to be working fine.

I am using the Olimex Header board for LPC2148 and wiggler jtag for programming it with the IAR and HJTAG.

However, the code for the UART still seems to have issues. Could I have bricked specific pins on the chip. Is there a way of checking this.
I mean, I can write code to find out if the IO is working and checking with simple LEDs but even with the IO working could it be possible that I brick the UART function only(I am pretty sure that my code ran fine from the RAM earlier).

Best Regards

>I am getting the following message while loading my code to the LPC2148
>using JTAG.
>
>Warning: Target inconsistency detected in Memory range 0x00000000-
>0x0000003F
>
>Any idea of why this might happen.
>
>Best Regards,
>Sumit
>
>

The 2024 Embedded Online Conference