How to start debugging apps in LP4357?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by jgorsk on Thu Aug 30 01:58:23 MST 2012
I'm trying to use Keil 4.54 (eval) to debug programs in the LPC4357
using only the internal flash and ram memories.
The program loads and the PC is pointing to 0x10403e00 address
instead of a location in the internal flash memory.

The program will not jump or run to main function
but when the PC is altered manually to point to any
funtion in my program, debugging will work (except
for the ISRs).

Is dubbuging in flash based LPC43 parts supported by the current version of Keil?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by rgledhill on Sat May 11 02:23:53 MST 2013

We are developing and debugging just fine on a Hitex LPC4357 dev kit, using Keil 4.71a (also works fine with earlier versions). Make sure you're downloading the code to flash before debugging (I notice the box to do this isn't ticked in the screenshots above).

There is a bug in the USART0 CMSIS driver from NXP whereby it doesn't clear and initialise the FIFOs correctly on start-up. Corrected version attached.

I've also attached a demo project for the LPC4357 which uses the RTX library; you could remove references to RTX though and it will then just build as an app (note the LED will only work on the Keil LPC4357 kit). Tested on Hitex LPC4357 board but should still build and run on other 4357 kits.

Don't use the Keil simulator for LPC43xx - NXP haven't provided the necessary framework for the simulator so it would be difficult to get useful results out.

If you've bought the Keil software drop their support a line - even if you're evaluating it, they will be happy to help.

Cheers

Richard

Hitex UK Ltd

lpcware · ‎06-15-2016

Content originally posted in LPCWare by jgorsk on Fri Apr 26 00:48:42 MST 2013

Hi,

As far as I know Keil simulator isn't supporting the LPC43xx. You need the actual hardware, then you can run your program in debug mode. If that's what you're asking about. The LPC43xx chips are supporting debugging mode.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by sivareddydevireddy on Wed Apr 24 23:05:56 MST 2013

i am also trying to simulte the same blinky example program but when i enter into simulation pc is pointed to 0x0 location it is not going to main routine.

did you ever try that example in simulation mode? right now i dont have hardware board so i am trying to check the code in simulation mode will it support simulation mode?

i heard from someone else that this microcontroller doesnt support simulation mode.how far is it true?

please try to help me uot from this issue it really very urgent to me.

thanks inadvance

lpcware · ‎06-15-2016

Content originally posted in LPCWare by jgorsk on Wed Sep 19 02:06:49 MST 2012
wellsk, thank you very much for your reply. It really helped. The problem was in the initialization file.
I am able to debug now. There are still other problems but that may be just my bad understanding
of how some of the peripherials work. I need to spend some time on troubleshooting.

bavarian, thanks for your help too. My program started to work in debug mode but it didn't work
in normal mode untill I followed your recommendation and added this line $K\ARM\BIN\ELFDWT.EXE !L BASEADDRESS(0x1A000000)
in the User tab.
There might be some issues with your example. Have you tried using running it? It doesn't work for me.
1. Target CPU is 4350 not 4357 and that's why 'Stop after bootloader' seems not to be relevant
2. Program does not jump to main function. It jumps into the middle of 'SetClock' function.
3. When you run the example on your board, what's the state of pin P2.7? It's high on my board.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by bavarian on Tue Sep 18 02:33:45 MST 2012
I don't see any problems or strange effects when working with the LPC4357.

Let's make a quick crosscheck:
- You link your application to 0x1A000000 (internal flash, bank A)

- You add the required flash header to the file with the user program command "$K\ARM\BIN\ELFDWT.EXE !L BASEADDRESS(0x1A000000)" (in the User tab).
This header need to be there for internal flash

- Set up the flash programming settings: Click “Settings” in the “Utilities” tab. Add the LPC18xx/43xx IAP 512kB Flash driver to the “Programming Algorithm” box.
Then set the “RAM for Algorithm” box to a larger size, 0x8000 will be fine. Click OK to save.

- You program the file to the internal flash. Either do it manually from the Flash menu or you check the box "Download to flash" in Debug --> Settings.
Then it's done when you start the debugger

- You start the debugger (the INI script contains a LOAD instruction, so in the debug tab you could uncheck "Load application at startup".
Alternatively you keep it checked and un-comment the LOAD line in the script file)

If you did not check "Run to main" the debugger will come up with the PC set to the Reset_Handler. This is after the bootloader. As far as I know the setting "Stop after bootloader" is not relevant for the LPC4357 environment).
I attached my test example, an extended example from the folder .\Keil_4.54\ARM\Boards\Keil\MCB4300. It's the original Blinky example, I just added the internal flash as target.

Hope it helps

lpcware · ‎06-15-2016

Content originally posted in LPCWare by jgorsk on Mon Sep 17 14:56:09 MST 2012
Thank you so much wellsk for your reply.
I can't verify my setting now but I'll do that asap.
I think the basic settings are the same, the initialization
file may be different though.

Will debugging still work on your board if 'Stop after bootloader'
option is selected?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by wellsk on Mon Sep 17 13:31:00 MST 2012

I'm using the v4.54 version of Keil UV4 with the Keil MCB 4357 board with internal FLASH. So far, I've seen no issues similar to that.

The only thing I can think of is that the debugger configuration is incorrect. See my settings below (especially VECTRESET).

The initialization file contains:

FUNC void Setup (unsigned int region) {

region &= 0xFF000000;
_WDWORD(0x40043100, region);                // Set the shadow pointer
_WDWORD(0xE000ED08, 0);                    // Set the vector table offset to 0
SP = _RDWORD(0);                     // Setup Stack Pointer
PC = _RDWORD(4);                 // Setup Program Counter
}

LOAD %L INCREMENTAL
Setup(0x1A000000); // Get ready to execute image in Flash bank A

lpcware · ‎06-15-2016

Content originally posted in LPCWare by jgorsk on Sun Sep 16 23:54:07 MST 2012
Is there anyone who has succeeded debugging in the FLASH versions of the LP43 family?
I'm having big problems with that. Also USART0 and SSP1 are giving problems. ISRs are
triggered with all the status bits indicating the interrupt source being cleared.
My guess is that the bootloader is dodgy but I'm not able to confirm that since
I'm not getting any support from NXP. This is a disaster.

Please let me know if you are using a flash version of the LP43 micro and it works.
I'm sure the romless versions work well enough. I wasted way too much time on this
and only a few features of this micro work properly. I'm going to scrap this project
soon and start over with another micro.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by jgorsk on Thu Sep 13 09:00:29 MST 2012
Hello,

No, I haven't solved the issue. Could you please post a working example?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by bavarian on Thu Sep 13 06:08:59 MST 2012
Hello,

did you already solve the issue with the LPC4337?
I can provide you with a working example if you like.
But on the other hand there should be enough examples in the Boards\KEIL\MCB4300 folder of µVision to show how it works.

Best regards.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by jgorsk on Wed Sep 12 23:40:50 MST 2012
It doesn't matter what the code is. I start a new
project in Keil and insert a blank SystemInit and main
functions and the CPU will never jump into either
of them. It's not even staying in the bootloader
code. It jumps into an area where there is no program code.

Can someone start a blank project in Keil for target LPC4357
and let me know if debugging works please? I'm actually
using the LPC4337 but only the LPC4357 is supported by Keil
at the moment. Can this be the reason why debugging isn't working?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by mc on Wed Sep 12 18:04:32 MST 2012
Hi Jgorsk,
Could you please post your code here.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by jgorsk on Wed Sep 12 03:33:50 MST 2012
Is anyone using the flash version of the LPC43?