• State Not Answered
  • Replies 6 replies
  • Subscribers 64 subscribers
  • Views 277 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 324962
Options

What are the flashing pins for the nRF52820 chip and how do I flash with the flashing pins?

Gotak

Hi,

I want to know what are the flashing pins for the part nRF52820, and what is the procedure for flashing the program with these pins? Should I use the comands? If yes, please help me with the commands?

Note: I am using nRF connect desktop SDK

Thanks,

Gotak

Parents Reply Children
  • 0 in reply to Jørgen Holmefjord

    Hi,

    Thanks for the reply! I will try that.

    While I was going through flashing I got struck at one point at the very initial. What build configuration should I choose for flashing a custom nrf52820, all I could find is 

    1. nrf52833dk_nrf52820

    2. nrf52820dongle_nrf52820

    Both of these build configurations gave be incomplete build fatal errors. What should I do? Or , Is there any other build configuration that would work for nrf52820 custom board?

    Thanks 

    Gotak

  • 0 in reply to Gotak

    The nrf52833dk_nrf52820 target would be the best starting point in nRF Connect SDK. We do not have a dedicated development kit for nRF52820, but nRF52833 DK can work as a "emulated" development platform. You can also reference "Adding custom board support" lesson in nRF Connect SDK Intermediate course in DevAcademy on how to implement your custom board in NCS.

    Depending on what application you are building, you might need to set different configurations or devicetree overlays to build and run successfully.

    If you post which sample you build, and attach the build log, we can help you resolve the problems.

  • 0 in reply to Jørgen Holmefjord

    So when I am trying to build the configurations for my nRF52820 custom board with nrf52833dk_nrf52820 with the central sample, I am getting this errors:

    * Executing task: nRF Connect: Build: central/build (active)

    Building central
    C:\WINDOWS\system32\cmd.exe /d /s /c "west build --build-dir c:/ncs/v2.5.2/nrf/samples/bluetooth/central/build c:/ncs/v2.5.2/nrf/samples/bluetooth/central"

    [1/6] Linking C executable zephyr\zephyr_pre0.elf
    FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map
    cmd.exe /C "cd . && C:\ncs\toolchains\c57af46cb7\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -gdwarf-4 @CMakeFiles\zephyr_pre0.rsp -o zephyr\zephyr_pre0.elf && cmd.exe /C "cd /D C:\ncs\v2.5.2\nrf\samples\bluetooth\central\build\zephyr && C:\ncs\toolchains\c57af46cb7\opt\bin\cmake.exe -E true""
    c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
    c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `noinit' will not fit in region `RAM'
    c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `FLASH' overflowed by 7776 bytes
    c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `RAM' overflowed by 11040 bytes
    collect2.exe: error: ld returned 1 exit status
    ninja: build stopped: subcommand failed.
    FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\c57af46cb7\opt\bin\cmake.EXE' --build 'c:\ncs\v2.5.2\nrf\samples\bluetooth\central\build'

    * The terminal process terminated with exit code: 1.
    * Terminal will be reused by tasks, press any key to close it.

    only when I am using these prj.conf:

    CONFIG_BT=y
CONFIG_BT_CENTRAL=y

CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y

CONFIG_NVS=y
CONFIG_LOG=y
CONFIG_LOG_MODE_IMMEDIATE=y
CONFIG_NVS_LOG_LEVEL_DBG=y
CONFIG_REBOOT=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y

CONFIG_BT_SMP=y
CONFIG_BT_GATT_CLIENT=y
CONFIG_BT_GATT_DM=y
CONFIG_HEAP_MEM_POOL_SIZE=1024
CONFIG_BT_GATT_DM_DATA_PRINT=y

CONFIG_UART_ASYNC_API=y
CONFIG_NRFX_UARTE0=y
CONFIG_SERIAL=y
CONFIG_GPIO=y
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
CONFIG_HEAP_MEM_POOL_SIZE=2048
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_APPEARANCE=833
CONFIG_BT_MAX_CONN=6
CONFIG_BT_MAX_PAIRED=1
CONFIG_BT_NUS=y
CONFIG_BT_SETTINGS=y
CONFIG_FLASH_MAP=y
CONFIG_SETTINGS=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=y
CONFIG_LOG_PRINTK=y
CONFIG_ASSERT=y

# CONFIG_UART_INTERRUPT_DRIVEN=y
# CONFIG_UART_0_INTERRUPT_DRIVEN=y

#thread
CONFIG_LOG_MODE_IMMEDIATE=y

CONFIG_WATCHDOG=y
CONFIG_WDT_LOG_LEVEL_DBG=y
CONFIG_WDT_DISABLE_AT_BOOT=y

CONFIG_TASK_WDT=y
CONFIG_TASK_WDT_MIN_TIMEOUT=500

CONFIG_THREAD_NAME=y

# Required to disable default behavior of deep sleep on timeout
CONFIG_PM_DEVICE=y
CONFIG_GPIO=y
# Optional select RAM retention (nRF52 only)
#CONFIG_APP_RETENTION=y
CONFIG_CRC=y
CONFIG_POWEROFF=y
CONFIG_ASSERT=y
CONFIG_ASSERT_LEVEL=2
CONFIG_CMSIS_RTOS_V1=y
CONFIG_NUM_PREEMPT_PRIORITIES=56
CONFIG_HEAP_MEM_POOL_SIZE=256
CONFIG_THREAD_NAME=y
CONFIG_THREAD_STACK_INFO=y
CONFIG_THREAD_MONITOR=y
CONFIG_INIT_STACKS=y
CONFIG_POLL=y
CONFIG_SCHED_SCALABLE=y
CONFIG_THREAD_CUSTOM_DATA=y

    Thanks,

    Gotak

  • 0 in reply to Gotak

    Hi,

    Any update on this?

    I am trying to flash the code image into my external custom nrf52820 board with my nrf52833 DK.

    Is these any board switch settings to do on the nRF52833 DK to flash on the nRF52820 externally?

    Thanks,

    Gotak

  • 0 in reply to Gotak
    Gotak said:
    So when I am trying to build the configurations for my nRF52820 custom board with nrf52833dk_nrf52820 with the central sample, I am getting this errors:

    The build log indicates that the application is too large to fit in Flash and RAM of nRF52820:

    c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `FLASH' overflowed by 7776 bytes
c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `RAM' overflowed by 11040 bytes

    Try building a simpler application.

    Gotak said:

    I am trying to flash the code image into my external custom nrf52820 board with my nrf52833 DK.

    Is these any board switch settings to do on the nRF52833 DK to flash on the nRF52820 externally?

    No, the nRF52833 DK will select the external board based on voltage level on VTG pin. If you are connecting the external board through P20 header, please connect VTG pin to VDD of the external board. Note that the on-board J-Link on the DK does not support voltage level conversion, so the external board must be supplied at the same voltage as the DK (3.0V).

Related