Difference between revisions of "NXP QN9090/30"
(→Vector Table Remap) |
(→Internal Flash) |
||
Line 10: | Line 10: | ||
===Vector Table Remap=== |
===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. |
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. |
||
==Evaluation Boards== |
==Evaluation Boards== |
Revision as of 10:18, 5 May 2020
Contents
The NXP QN9090 / QN9030 are ultra-low power, Cortex-M4 based wireless microcontroller 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.