Intro:
As the chipset of nRF5340 is built by Dual Core structure (net core and application core), we need to proceed the coding and compiling process individually to net core & application core.
After the coding and compiling process done, we could get the separate zephyr.hex file respectively which are used for BLE module FW.
Firmware Development Steps : Code Building / Compiling
Case Study :
NON-Audio Project
nRFConnect SDK V2.1.2
Nordic Example code -“hci_rpmsg” & “peripheral_uart”
- Nordic example code of “hci_rpmsg” extracted for coding and we will get zephyr.hex file for net core
- Nordic example code of “peripheral_uart” extracted for coding and we will get zephyr.hex file for application core
Step 1. Net core Layer
1d) Select “nrf5340dk_nrf5340_cpunet” and check Nordic boards, then Execute “Build Configuration”
Step 2. Application core Layer:
2a) Activate “Open VS Code” IDE in NCS V2.1.2
2b) Select “Add an existing application” and extract “peripheral_uart” file moving forward
2c) Click “Add Build Configuration” icon
2d) Select “nrf5340dk_nrf5340_cpuapp” and check Nordic boards, then Execute “Build Configuration”
2e) zephyr.hex file is successfully generated for application core layer if the coding process is properly executed
Find more nRF5340 module development resources in below link
How To Get started with MDBT53/53V Demo Board Set up (MDBT53-DB-40/MDBT53V-DB-40)
How To USE Nordic Connect SDK (NCS) Flashing Built Code into nRF5340 Module
Raytac Corporation 勁達國際電子有限公司
A BT5.3 & BT5.2 & BT5.1 module maker based on Nordic nRF53 & nRF52 solution
(nRF5340 & nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52811 & nRF52810 & nRF52805)
www.raytac.com email: service@raytac.com Tel: +886.2.3234.0208
No comments:
Post a Comment