• State Not Answered
  • Replies 23 replies
  • Subscribers 74 subscribers
  • Views 716 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 345218
Options

Sysbuild example nRF5340DK UART output

danny0007

Hi Community,

I'm learning the sysbuild stuffs, try to upgrade my code to sdk v2.9.0.

Exercise 2 - Adding custom image - Nordic Developer Academy

I'm using nRF5340DK to run this exercise code, but I can't find the so called "UART30 " for output.

Could you please give me more instructions? thanks!

Regards

Danny

Parents Reply Children
  • 0 in reply to danny0007
    danny0007 said:
    is it somehow possible to use the dfu_application.zip directly? 

    It is not. The nRF SoC can not handle the .zip file. This is required by the app that sends the update.
    When you select dfu_application.zip in the Android app, the nrf Android app will unzip it automatically and send the images in order.

    danny0007 said:

    Cannot find any discussion regarding this kind of error, maybe nobody tried this, could you please have a look:

    ---- Reopened serial port COM28 ----
    *** Booting My Application v3.0.0-b901c3efa989 ***
    *** Using nRF Connect SDK v3.0.0-3bfc46578e42 ***
    *** Using Zephyr OS v4.0.99-3e0ce7636fa6 ***
    Starting Bluetooth Peripheral LBS sample
    I: 8 Sectors of 4096 bytes
    I: alloc wra: 0, fe8
    I: data wra: 0, 0
    E: Endpoint binding failed with -11
    E: HCI driver open failed (-11)
    Bluetooth init failed (err -11)

    My guess is that this error is because the radio core fails, and therefore, the application core can not communicate with it over HCI.

  • 0 in reply to Sigurd Hellesvik

    Hi  

    I compared the board files of nRF5340DK and Thingy53 one by one, still cannot make it working.

    could you please compile the FOTA code for Thingy53 and take a look? thanks.

    Regards

    Danny

  • 0 in reply to danny0007

    Hi @ 

    after changing the code in thingy53_nrf5340_common.dtsi to this:

        chosen {
            //zephyr,bt-hci-ipc = &ipc0;
            zephyr,bt-hci = &bt_hci_ipc0;
            //nordic,802154-spinel-ipc = &ipc0;
            //zephyr,ieee802154 = &ieee802154;
            //nordic,pm-ext-flash = &mx25r64;
        };
    changing the code in thingy53_nrf5340_cpunet.dts to this:
        chosen {
            //zephyr,console = &uart0;
            //zephyr,shell-uart = &uart0;
            //zephyr,uart-mcumgr = &uart0;
            //zephyr,bt-mon-uart = &uart0;
            //zephyr,bt-c2h-uart = &uart0;
            zephyr,bt-hci-ipc = &ipc0;
            //nordic,802154-spinel-ipc = &ipc0;
            zephyr,sram = &sram1;
            zephyr,flash = &flash1;
            zephyr,code-partition = &slot0_partition;
            zephyr,ieee802154 = &ieee802154;
        };
    the FOTA code for both cores is running, the HCI error is gone, but I'm not sure if it's a reliable solution, please double check it.
    **********************************************************************************
    Additionally, since I only have USB on my board, for debugging I want to redirect the logging and output of printk to USB, so I add following code in app.overlay 
    /* Step 1.1  - Add external flash to applciation */
    / {
        chosen {
            nordic,pm-ext-flash = &mx25r64;
            zephyr,console = &cdc_acm_uart0; //for printk in app
        };
    };
     
    &usbd {
        cdc_acm_uart0: cdc_acm_uart0 {
            compatible = "zephyr,cdc-acm-uart";
            status = "okay";
        };
    };
    and this in prj.conf:
    # Enable USB subsystem
    CONFIG_USB_DEVICE_STACK=y
    CONFIG_UART_LINE_CTRL=y
    CONFIG_USB_DEVICE_INITIALIZE_AT_BOOT=y
    CONFIG_USB_DEVICE_PRODUCT="TEST_USB"
    CONFIG_STDOUT_CONSOLE=y
    CONFIG_LOG=y
     
    but this crashes the system often, the chip get rebooted very often, how can I make a reliable USB logging? 
    Regards
    Danny
  • 0 in reply to danny0007
    danny0007 said:
    the FOTA code for both cores is running, the HCI error is gone, but I'm not sure if it's a reliable solution, please double check it.

    Good job!

    Looks like you just had to make sure hci matches. So yes, in that case, the changes seem reasonable to me.

    danny0007 said:
    but this crashes the system often, the chip get rebooted very often, how can I make a reliable USB logging? 

    For USB:

    How often do you log?
    Does it improve if you log a bit less?

    Try to set CONFIG_USB_CDC_ACM_RINGBUF_SIZE=16384

  • 0 in reply to Sigurd Hellesvik

    Regardless of the USB issue.

    the HCI issue happens again, it seems not a stable solution, it happens randomly.

    Actually during the debugging, I also found it's working only sometimes, even the same code doesn't work after another flash.

Related
Terms of service