This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Can nR52810 support Zephyr HCI_UART?

Hi Sir,

We design the nRF52810 in an embedded system and plans to use BlueZ to control the BLE device.

We can work with nRF52-DK through HCI_UART, so we also implement the HCI_UART for nRF52810, but we got link fail when tried to link w/ cell phone.

  

Some questions.

Q1. As check the folder, we found there is no nrf52810_pca10040.conf in the /zephyr/samples/bluetooth/hci_uart/boards,

Does it mean the nrf52810 not support in HCI_UART example?

 

 

Q2. I assume the 52810 can support example HCI_UART,

   Since we don't design the external 32K crystal, we config the 32k crystal set to RC, but we cannot get the link, even we change to synthesized.

Is it because the HCI_UART doesn't support nRF52810 natively? If not, is there something we miss in the Kconfig setting?

Q3. If Q2 is yes, we may change to nRF5232. For support DFU (MCUboot), what kind of setting we should enable in Kconfig?

Should we modify the flash size for MCUboot? and how? 

Or we have a detailed step to guide us to implement MCUboot?

Thank you.

BRs, Han

 

Parents Reply Children
  • Hi Susheel,

    Got it, I will try it again.

    And how about the setting procedure of MCUboot?

    If enable "Project" -> "Configure nRF Connect SDK Project..." -> "Boot Options" -> "MCUboot bootloader support"

    I got below error, how do I fix it?

    -------

    2> Compiling ‘poll.c’
    1> Archiving ‘libkernel.a’
    Rebuilding ‘zephyr/zephyr_prebuilt.elf’ from solution ‘build’ in configuration ‘Common’
    1> Compiling ‘empty_file.c’
    1> Linking ‘zephyr_prebuilt.elf’
    1> Memory region Used Size Region Size %age Used
    1> FLASH: 79403 B 73216 B 108.45%
    1> SRAM: 21440 B 24 KB 87.24%
    1> c:/gnuarmemb/8 2019-q3-update/bin/../lib/gcc/arm-none-eabi/8.3.1/../../../../arm-none-eabi/bin/ld.exe: zephyr\zephyr_prebuilt.elf section `text' will not fit in region `FLASH'
    1> c:/gnuarmemb/8 2019-q3-update/bin/../lib/gcc/arm-none-eabi/8.3.1/../../../../arm-none-eabi/bin/ld.exe: region `FLASH' overflowed by 6187 bytes
    1> collect2.exe: error: ld returned 1 exit status
    1> IDT_LIST: 152 B 2 KB 7.42%
    Build failed

    ---------

    Thank you.

    BRs, Han

  • It looks like there is not enough space for MCUBoot to fit in nRF52810 along side with your application. You need to optimize your application FLASH usage to make the MCU fit in.

    1> FLASH: 79403 B 73216 B 108.45%

  • Hi Susheel,

    I tried to adjust the feature from Kconfig, but I cannot reduce the size lower 100%

    I use the standard HCI_UART example code, do you have any idea for how we can optimize it?

    Thank you.

    Brs, Han

  • Unfortunately, I do not see any other way to optimize it other than restructuring the code. The example HCI_UART + MCUboot does not look like they fit together with the code structure we have on nRF52810.

Related