Difference between revisions of "NXP QN9090/30"
(→Example Application) |
|||
(9 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
+ | [[Category:Device families]] |
||
__TOC__ |
__TOC__ |
||
The NXP QN9090 / QN9030 are ultra-low power, Cortex-M4 based wireless microcontrollers supporting Bluetooth Low Energy 5.0. |
The NXP QN9090 / QN9030 are ultra-low power, Cortex-M4 based wireless microcontrollers supporting Bluetooth Low Energy 5.0. |
||
Line 15: | Line 16: | ||
The device has a ROM code which needs to be run after reset. The J-Link halts the MCU after executing the ROM code but before starting the application. |
The device has a ROM code which needs to be run after reset. The J-Link halts the MCU after executing the ROM code but before starting the application. |
||
==Evaluation Boards== |
==Evaluation Boards== |
||
+ | *NXP JN5189-DK006 evaluation board: https://wiki.segger.com/NXP_JN5189-DK006 |
||
+ | |||
==Example Application== |
==Example Application== |
||
+ | *NXP JN5189-DK006 evaluation board: https://wiki.segger.com/NXP_JN5189-DK006#Example_Project |
||
− | The application toggles 3 LEDs (blue, red and green) on the MIMXRT685-EVK evaluation board. The application is linked into the external flash. It includes a valid boot header so it also runs stand-alone. |
||
− | EL xxxxxxxxxxxxxxxxxx |
||
− | '''SETUP''' |
||
− | *J-Link software: V6.62d |
||
− | *Embedded Studio: V4.50 |
||
− | *Hardware: NXP MIMXRT685-EVK |
||
− | *Link: [[File:NXP_MIMXRT685-EVK_QSPI_ES.zip]] |
Latest revision as of 13:12, 15 May 2024
Contents
The NXP QN9090 / QN9030 are ultra-low power, Cortex-M4 based wireless microcontrollers supporting Bluetooth Low Energy 5.0.
Internal Flash
Supported Regions
The internal flash is divided into 3 different regions:
- Reserved by flash controller (0x9F000 - 0x9FFFF)
- Reserved by boot code (0x9DE00 - 0x9EFFF)
- Application space (0x00000 - 0x9DDFF for JN5189; 0x00000 - 0x50000 for JN5188)
For now, the J-Link supports the application space, only.
Vector Table Remap
The first 512 bytes of the device (0x0000 - 0x01FF) can be mapped to flash, ROM or RAM. When using the J-Link flashloader, this region is mapped to flash. This is done on purpose as the device does not provide a mirror address for the first 512 bytes of flash thus without remapping, the J-Link could not program the first 512 bytes.
ECC flash
The flash seems to be ECC protected. Read fails for sectors with invalid ECC (e.g. erased sectors). In order to prevent errors when reading empty sectors, the DLL do neither perform a blank check nor a compare of the flash content before programming.
Reset
The device has a ROM code which needs to be run after reset. The J-Link halts the MCU after executing the ROM code but before starting the application.
Evaluation Boards
- NXP JN5189-DK006 evaluation board: https://wiki.segger.com/NXP_JN5189-DK006
Example Application
- NXP JN5189-DK006 evaluation board: https://wiki.segger.com/NXP_JN5189-DK006#Example_Project