Debug problem on LPC2468 VIC

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Debug problem on LPC2468 VIC

1,364 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by nmariner on Mon Apr 28 14:41:15 MST 2014
Last week I posted an issue I am having debugging the LPC2468 because all of the VIC registers are not showing.
I have had no responses yet so wonder if there is a more appropriate place to ask this question.
I am not sure if it could be a bug in the IDE.

Nigel.
0 Kudos
Reply
5 Replies

1,342 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by nmariner on Wed Apr 30 06:51:04 MST 2014
Ok thanks for the info. At least it's not something I am doing.
Will check the examples and compare code.

Thanks,
Nigel.
0 Kudos
Reply

1,341 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Apr 29 07:33:00 MST 2014
Sorry, I forgot to comment on this earlier. There is an issue with the VIC peripheral in the Peripheral view not being complete (for LPC23/24 parts) and having the wrong addresses used for the 14/15 registers. This has now been logged in our system for future investigation.

My comment about using ISP (and the example code I posted) was really to see if it helped solve the issues you were trying to debug when you looked at the VIC registers to start with.

Regards,
LPCXpresso Support
0 Kudos
Reply

1,342 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by nmariner on Tue Apr 29 05:54:41 MST 2014
OK, I have held ISP enable low during power up and this makes no difference.
I have even created a new project with the wizard and just have the start code that increments a variable. Still the VIC is only showing as 16 vector address registers, and with register 14 and 15 being the same address as registers 2 and 3 !

Regards,
Nigel.
0 Kudos
Reply

1,342 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by nmariner on Tue Apr 29 04:08:21 MST 2014
Sorry my mistake, I am using the LPC2368.
I am using the code red toolchain and the gnu make builder (in the toolchain editor settings)
I am using JTAG connection for debugging and don't toggle the ISP pin at the moment.
I am also using the standard cr_startup file as provided by the intial new project wizard.
I can load and run the program ok, I have timer2 running and can see the counter has incremented each time I halt the program and read out the peripheral register so I believe that the debug interface is fine.
The problem is that when I interrogate the VIC registers I can only see the first 16 vector address registers in the IDE (as per screen shot provided in first post). I was looking to view the timer2 interrupt vector address but cannot as it is on interrupt 26. This is what is stopping me from progressing further in my investigations as to why timer2 interrupt is not hitting (I put the breakpoint int the timer2 ISR but to no avail, no program halt at breakpoint).
Also if I force an address into VIC vector address 15 (during debug program halt) it gets mirrored into vector address 3 which I can understand as they are both showing the same register address, but surely this should not happen and kind of suggests something is not working right with the debug environment.

I will try powering board with the ISP pin low to see if it makes a difference.

Best Regards,
Nigel.
0 Kudos
Reply

1,342 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Apr 29 01:51:00 MST 2014
I'm not sure which part you are actually using - LPC2468 as you state here, or LPC2368 as you stated in your other post. However as these two parts are very similar, this should not really matter.

However I've attached a zip file which contains two blinky projects for the Keil MCB2368 board (one blinks the LEDs faster than the other, so that you can alternate between the 2). I suggest that you compare these with your own code base.

One thing to note is that these ARM7 MCUs can sometimes require you to power them up with the ISP button depressed in order to successfully debug them. It is possible that this is what is causing the problems you are having.

Regards,
LPCXpresso Support




0 Kudos
Reply