Samples for NRF54L15 not working

I have just started using 2.7.0 with the nrf54L15 chips and come across a few problems.

When trying to run the UART sample I found that the app overlay files, which I believe are auto generated, for most of the older chips use:

/ {
    chosen {
        nordic,nus-uart = &uart0;
    };
};
and correspond to the .dtsi file as:
/ {
    chosen {
        zephyr,console = &uart0;
        zephyr,shell-uart = &uart0;
        zephyr,uart-mcumgr = &uart0;
    };
But the nrf54L15 .dtsi file is:
/ {
    chosen {
        zephyr,console = &uart20;
        zephyr,shell-uart = &uart20;
        zephyr,uart-mcumgr = &uart20;
    };
I believe that the coding for the board files has chosen to indicate pin numbers in the naming, just a guess, and that's why the files no longer match and carry forward with the universal one for all feeling of the Nordic development environment. its easy enough to change the app overlay file to &uart20, I am just noting this issue that may confuse some.
How do we include global files into the system such that all modules pickup the changes? This is in reference to NRF54L15_Globals.h and NRF54L15_Eang_globals.h that redefine many "_S" defines to no longer have the "_S".  For example:
C:/ncs/v2.7.0/modules/hal/nordic/nrfx/drivers/src/nrfx_rramc.c: In function 'nrfx_rramc_irq_handler':
C:/ncs/v2.7.0/modules/hal/nordic/nrfx/drivers/src/nrfx_rramc.c:268:47: error: 'NRF_RRAMC' undeclared (first use in this function); did you mean 'NRF_RRAMC_S'?
its probably a change to the configuration of the build I just cant seem to add the reference properly without messing up other builds.
Parents Reply
  • More issues, specifically with running debug on the PDK eng_rev_B PCA10156

    Segger does not recognize the chip and debug fails across multiple sample applications

    debug message results:

    JLinkGDBServerCL: SEGGER J-Link GDB Server V7.94i Command Line Version
    JLinkGDBServerCL:
    JLinkGDBServerCL: JLinkARM.dll V7.94i (DLL compiled Feb 7 2024 17:08:52)
    JLinkGDBServerCL:
    JLinkGDBServerCL: -----GDB Server start settings-----
    JLinkGDBServerCL: GDBInit file: none
    JLinkGDBServerCL: GDB Server Listening port: 59049
    JLinkGDBServerCL: SWO raw output listening port: 2332
    JLinkGDBServerCL: Terminal I/O port: 2333
    JLinkGDBServerCL: Accept remote connection: localhost only
    JLinkGDBServerCL: Generate logfile: off
    JLinkGDBServerCL: Verify download: off
    JLinkGDBServerCL: Init regs on start: off
    JLinkGDBServerCL: Silent mode: on
    JLinkGDBServerCL: Single run mode: on
    JLinkGDBServerCL: Target connection timeout: 0 ms
    JLinkGDBServerCL: ------J-Link related settings------
    JLinkGDBServerCL: J-Link Host interface: USB
    JLinkGDBServerCL: J-Link script: none
    JLinkGDBServerCL: J-Link settings file: none
    JLinkGDBServerCL: ------Target related settings------
    JLinkGDBServerCL: Target device: cortex-m33
    JLinkGDBServerCL: Target device parameters: none
    JLinkGDBServerCL: Target interface: SWD
    JLinkGDBServerCL: Target interface speed: 12000kHz
    JLinkGDBServerCL: Target endian: little
    JLinkGDBServerCL: =thread-group-added,id="i1" =cmd-param-changed,param="pagination",value="off" nrf_event_check (event=304, p_reg=p_reg@entry=0x500c6000) at C:/ncs/v2.7.0/modules/hal/nordic/nrfx/hal/nrf_common.h:264 264 return (bool)*(volatile const uint32_t *)((const uint8_t *)p_reg + (uint32_t)event);
    [New Thread 536884376]
    [New Thread 536884176]
    [New Thread 536878720]

    These sample application worked on the nRF54840 Dev board, built from the same code alternate build.

    Segger kicks up the following screens when trying to debug

    Thanks in advance

Children
Related