topic Re: LPC54005 - Systick Handler never called in LPC Microcontrollers

LPC54005 - Systick Handler never called

Beggar — Mon, 27 Nov 2023 09:56:16 GMT

Hello all,

I spent a whole day with trying to get the LED-Blinky example working on my customer target Hardware without success. I read through the documentation, countless posts, tried this and that but did not find a solution which worked. Very frustrating. Hope that someone here can give me some hints.

Here is what I did:
First I downloaded and installed the LPC54004 SDK stuff in the MCUXpresso IDE. Then I set up pins, clocks and some of the peripherals. Then I took the LPC54s018 "Hello world" code example. This was recommended by NXP since that processor is pretty close to the LPC54005. I managed to compile and run/debug the "Hello world" example on my customer target Hardware and it's doing what it's supposed to do.

Then I made a copy of the project, took parts of the 54s018_led_blinky example source code and replaced some of the code of the Hello World example with it.

The debugger tells me that the systick handler is never called.

Questions:

1.) What are potential reasons that prohibit this from working ?

2.) In the clock tool, I can set the source and div ratio for the systick clock.
But the systick period is also set in the code, using

SysTick_Config(SystemCoreClock / 1000U)

Two configs ? Which one is relevant ?

Thanks for your help

Here is the rest of the code:

/* * Copyright 2016-2023 NXP * All rights reserved. * * SPDX-License-Identifier: BSD-3-Clause */ /** * @file LPC54005_Project.c * @brief Application entry point. */ #include <pin_mux.h> #include <stdio.h> #include "board.h" #include "peripherals.h" #include "clock_config.h" #include "LPC54005.h" #include "fsl_debug_console.h" /* TODO: insert other include files here. */ /* TODO: insert other definitions and declarations here. */ /******************************************************************************* * Definitions ******************************************************************************/ //GPIO_0_1 #define BOARD_GPIO_PORT 0U #define BOARD_GPIO_PIN 1U /******************************************************************************* * Prototypes ******************************************************************************/ /******************************************************************************* * Variables ******************************************************************************/ volatile uint32_t g_systickCounter; /******************************************************************************* * Code ******************************************************************************/ void SysTick_Handler(void) { if (g_systickCounter != 0U) { g_systickCounter--; } } void SysTick_DelayTicks(uint32_t n) { g_systickCounter = n; while (g_systickCounter != 0U) { } } /* * @brief Application entry point. */ int main(void) { /* Init board hardware. */ BOARD_InitBootPins(); BOARD_InitBootClocks(); BOARD_InitBootPeripherals(); #ifndef BOARD_INIT_DEBUG_CONSOLE_PERIPHERAL /* Init FSL debug console. */ BOARD_InitDebugConsole(); #endif PRINTF("\r\nGPIO TOGGLE TEST\r\n"); /* Set systick reload value to generate 1ms interrupt */ if (SysTick_Config(SystemCoreClock / 1000U)) { while (1) { } } PRINTF("SYSTICK CONFIGURED\r\n"); while (1) { /* Delay 1000 ms */ SysTick_DelayTicks(1000U); GPIO_PortToggle(GPIO, BOARD_GPIO_PORT, 1u << BOARD_GPIO_PIN); //PRINTF("GPIO toggeled\r\n"); } }

Re: LPC54005 - Systick Handler never called

frank_m — Mon, 27 Nov 2023 12:08:07 GMT

Did you try to step into the SysTick_Config() function in the debugger , and see if the interrupt gets enabled (the IE flag set) ?

This function is usually implemented as "static inline" in core_cm4.h.

Re: LPC54005 - Systick Handler never called

Beggar — Mon, 27 Nov 2023 15:39:23 GMT

The SysTick_Config() function is visited and it seems that the register is set correctly.

But shortly after that it gets stucked in the while loop that waits for the counter to be zero.

I'm completely new to this IDE and debugging so forgive me if I ask silly questions.

And please let me know whether you can read the screenshots. Should I upload them as attachments ?

How can I verify that the Flag is really set ?

It seems that the SysTick_CTRL_CLKSOURCE_Msk is reset after the initial configuration. Is that a problem ?

Thanks for your help

Re: LPC54005 - Systick Handler never called

Beggar — Mon, 27 Nov 2023 16:13:10 GMT

SysTick.VAL is counting, shows values between 0 and 11999.

g_systickCounter is not counting. Whenever I stop/pause the debugger, it has the inital value of 1000.

Re: LPC54005 - Systick Handler never called

frank_m — Tue, 28 Nov 2023 06:28:28 GMT

And did you try setting a breakpoint in the Systick handler ?
The "g_systickCounter" variable is manipulated there.

Systick is common to all Cortex M devices, and thus basically all toolchains come with a default hander.
With LPCXpresso, this is in "startup_lpc<nnn>.c", which is part of your project (with <nnn> is probably "54005" in your case).
The default handler in this file is declared as "WEAK", i.e. supposed to be overwritten with your code.
If the function name of your own handler doesn't match, this routine would fire, too.

So, if you cannot step into your own Systick handler, try setting a breakpoint in this default routine.

Re: LPC54005 - Systick Handler never called

Beggar — Tue, 28 Nov 2023 16:33:56 GMT

A breakpoint inside the SysTick_Handler routine is never reached.

Re: LPC54005 - Systick Handler never called

Beggar — Wed, 29 Nov 2023 13:15:55 GMT

I put a breakpoint into the WEAK SysTick_Handler in startup_lpc54005.c and it is also not triggered.

So what's going on here ? What am I missing ? Never needed 3 days to toggle a GPIO in a reasonable deterministic frequency !

Isn't there something like a usleep function that just works (like in other architectures) ?

Anyone from NXP who can help me ?

Do I have to change the MCU to a none-NXP part to procees with my project ?

Kind regards

Re: LPC54005 - Systick Handler never called

Alice_Yang — Thu, 30 Nov 2023 02:00:55 GMT

Hello @Beggar

1) You can check Systick register in "Peripherals+" view as below:

2) I have no board for this chip, so only can test on LPC54018. How about create a simple new project based on LPC54005, then copy application code from blinky demo to your project, then debug check registers. If still can't work, send your project to me.

3) BTW, without Systick , does your board can work well? For example, just turn on one led of your board.

Alice

Re: LPC54005 - Systick Handler never called

frank_m — Thu, 30 Nov 2023 06:31:22 GMT

I would check the map file.
Just open the "Debug" folder in the Project explorer view. The file is named <project_name>.map.
Double-click top open it, and seach for "SysTick_Handler". The map file should list the address it is located, and the souce/object file it was compiled from.

Maybe you somewhat mixed up your project, and the sourcefile(s) you edit are not those that take effect.
You wouldn't be the first one that happens to ...
I occasionally came across workspaces with projects that had identically named files in different folder.
To make clear which one belongs to my project, I added a "#error "<some string>" directive to it.
If the build did not throw an error, I got the wrong one ...

Re: LPC54005 - Systick Handler never called

frank_m — Thu, 30 Nov 2023 07:08:31 GMT

> Do I have to change the MCU to a none-NXP part to procees with my project ?

Had to reboot my work PC in the meantime, because of a forced update ...

But the basic issue wouldn't change with another vendor/MCU. Not only is Systick handling basically the same (Systick is fixed part of the core provided by ARM), you would still have to get familiar with the IDE and toolchain.

I am not a huge fan of Eclipse IDEs either, by the way.
But LPCXpresso is the most supported IDE by NXP, and the provided examples usually run out of the box.
You have not described how you had set up you project.

But as Alice suggested, the best option is to use an example project from the SDK for your MCU, or (even better) for your eval board, if you are using one.

Re: LPC54005 - Systick Handler never called

Beggar — Thu, 30 Nov 2023 09:26:25 GMT

Hello Alice, thanks for your comments

2) How about create a simple new project based on LPC54005, then copy application code from blinky demo to your project

That's what I did. I wrote that in my first post. The HelloWorld example is working

3) BTW, without Systick, does your board can work well? For example, just turn on one led of your board.

Yes. when I comment out

SysTick_DelayTicks(1000U);

It works fine. The GPIO toggles at a rate of around 170 kHz.

However, my Peripherals+ window is empty !?

Re: LPC54005 - Systick Handler never called

Beggar — Thu, 30 Nov 2023 09:33:42 GMT

Hello Frank,

The map file should list the address it is located, and the source/object file it was compiled from.

There are two lines which contain "SysTick_Handler":

0x00000264 SysTick_Handler

SysTick_Handler ./startup/startup_lpc54005.o

Does that look correct to you ?

Re: LPC54005 - Systick Handler never called

frank_m — Thu, 30 Nov 2023 10:15:00 GMT

So far, yes.

The first one is the handler location (in the vector table), and second one is the actual handler routine.
The location "./startup/startup_lpc54005.o" refers to a file in your project, see here (example from a project of mine):

This is the handler routine taking effect.
Do you see your code there ?

Re: LPC54005 - Systick Handler never called

Beggar — Thu, 30 Nov 2023 12:22:16 GMT

The WEAK SysTick_Handler exists in startup_lpc54005.c

However, when I set a breakpoint inside the WEAK SysTickHandler, it is never reached.

Re: LPC54005 - Systick Handler never called

frank_m — Thu, 30 Nov 2023 13:04:32 GMT

This can be deceiving.
The default handler is usually either an endless loop or an empty function body, compiled a few machine instructions. It is often impossible to observe this on source code debug level.

But getting back to your last post.
Your own handler is implemented in the main file, of which you posted the contents.
Thus the linker map file should list this file as source for the SysTick_Handler routine, not the startup file. Something seems off here.

Does the build fail if you comment out the "weak" handler in startup_lpc54005.c ?

Re: LPC54005 - Systick Handler never called

Beggar — Thu, 30 Nov 2023 15:39:54 GMT

Does the build fail if you comment out the "weak" handler in startup_lpc54005.c ?

No, build does not fail

Re: LPC54005 - Systick Handler never called

frank_m — Fri, 01 Dec 2023 06:51:41 GMT

It should.
There seems something wrong with you project. It looks like the code you are editing and that the debugger displays is not the code actually executed.

I would setup the project anew.

As a test, I added a Systick handler to one of my LPCXpresso projects that did not use Systick.
As seen here, the map file lists both instances, and the non-"WEAK" implementation first.
As implied, it is the file ./source/mcan_interrupt_transfer.c that implements the handler function.

Re: LPC54005 - Systick Handler never called

Alice_Yang — Tue, 05 Dec 2023 01:57:32 GMT

Hello @Beggar

1) However, my Peripherals+ window is empty !?

When debug, there is value in Peripherals+ window . Please take a screenshot show yours.

2) Share your project, a simple project that can reproduce your issue, please.

Alice

Re: LPC54005 - Systick Handler never called

Beggar — Tue, 05 Dec 2023 11:05:21 GMT

Hello Alice,

I set up a new LPC45005 project, replaced the pin_mux.c and pin_mux.h files to match my target hardware and made sure that the "Hello World" example works. Then I added a SysTick_Handler into the source code and started the debugger. Result: SysTick_Handler does not get called.

How do I share the project with you ?

Re: LPC54005 - Systick Handler never called

Beggar — Tue, 05 Dec 2023 11:11:56 GMT