Difference between revisions of "NXP NCJ29D5"

From SEGGER Wiki
Jump to: navigation, search
(Created page with "The '''[SiliconVendor] [DeviceFamily]''' are [SHORT_DESCRIPTION] __TOC__ ==Flash Banks== ===Internal Flash=== {| class="seggertable" |- ! Flash Bank || Base address !! Size |...")
 
(8 intermediate revisions by one other user not shown)
Line 1: Line 1:
  +
The '''NXP NCJ29D5''' are Ultra-Wideband (UWB) ICs designed specifically to meet the connectivity and safety needs of the global automotive industry.
The '''[SiliconVendor] [DeviceFamily]''' are [SHORT_DESCRIPTION]
 
 
__TOC__
 
__TOC__
   
Line 8: Line 8:
 
! Flash Bank || Base address !! Size || J-Link Support
 
! Flash Bank || Base address !! Size || J-Link Support
 
|-
 
|-
| [BANK_NAME] || [BANK_BASE_ADDRESS] || Up to [FLASH_SIZE] KB || style="text-align:center;"| {{YES}} / {{NO}}
+
| Normal-Domain Application || 0x00200000 || 128 KB || style="text-align:center;"| {{YES}}
|}
 
 
====ECC Flash [OPTIONAL]====
 
*Describe ECC Flash restriction here.
 
 
===QSPI Flash===
 
QSPI flash programming requires special handling compared to internal flash. For more information about this, please see the [[QSPI Flash Programming Support | QSPI Flash Programming Support article]].<br>
 
J-Link supports multiple pin configurations for [DEVICE]. The default loader is marked in '''bold'''.
 
{| class="seggertable"
 
 
|-
 
|-
  +
| RX Radio Configurations || 0x00238A00 || 8 KB || style="text-align:center;"| {{NO}}
! Device !! Base address !! Maximum size !! Supported pin configuration
 
 
|-
 
|-
  +
| TX Radio Configurations || 0x0023AA00 || 8 KB || style="text-align:center;"| {{NO}}
| [DEVICE]|| [BANK_BASE_ADDRESS] || [MAX_SPI_FLASH_SIZE] MB ||
 
  +
|-
*'''[LOADER_NAME]'''
 
  +
| Customer Configuration Page || 0x0023C000 || 512 B || style="text-align:center;"| {{NO}}
*[LOADER_NAME]
 
  +
|-
*[LOADER_NAME]
 
  +
| Baseband DSP Firmware || 0x00230000 ||35 KB || style="text-align:center;"| {{NO}}
 
|}
 
|}
   
==ECC RAM [OPTIONAL]==
+
====ECC Flash====
  +
*Device has ECC flash, reading of un-programmed or erased areas will result in an error.
*Describe ECC RAM restriction here.
 
  +
*Dedicated verify and blank check functions are implemented.
 
==Vector Table Remap [OPTIONAL]==
 
*Describe Vector Table Remap here..
 
   
 
==Watchdog Handling==
 
==Watchdog Handling==
*The device does not have a watchdog.
+
*The device has a watchdog which is enabled by default after Reset with 20s timeout.
  +
*On connect, the reset source of the watchdog will be disabled, so it keeps running, but doesn't force a reset.
*The device has a watchdog [WATCHDOGNAME].
 
*The watchdog is fed during flash programming.
 
*If the watchdog is enabled, it is turned off during flash programming and turned back on afterwards.
 
   
 
==Multi-Core Support [OPTIONAL]==
 
Before proceeding with this article, please check out the generic article regarding Multi-Core debugging [[Multi-Core_Debugging | here]].<br>
 
The [DeviceFamily]family comes with a variety of multi-core options.<br>
 
Some devices from this family feature a secondary core which is disabled after reset / by default.<br>
 
Some of the are available with enabled ''lockstep'' mode, only. <br>
 
In below, the debug related multi-core behavior of the J-Link is described for each core:
 
===Main core===
 
====Init/Setup====
 
*Initializes the ECC RAM, see [[XXX | XXX]]
 
*Enables debugging
 
====Reset====
 
*Device specific reset is performed, see [[XXX | XXX]]
 
 
====Attach====
 
====Attach====
*Attach is not supported because the J-Link initializes certain RAM regions by default
+
*Attach is supported.
===Secondary core(s)===
 
====Init/Setup====
 
*If the main core session has not been started / debugging is not enabled yet, the secondary core executes the enable debug sequence.
 
*If the secondary core is not enabled yet, it will be enabled / release from reset
 
====Reset====
 
No reset is performed.
 
====Attach====
 
*Attach is supported / desired
 
   
 
==Device Specific Handling==
 
==Device Specific Handling==
 
===Reset===
 
===Reset===
*The devices uses normal Cortex-M reset, no special handling necessary, like described [[J-Link_Reset_Strategies#Type_0:_Normal | here]].
+
*The devices uses normal Cortex-M reset.
  +
*After Reset Watchdog is disabled as described above.
*The devices uses Cortex-M Core reset, no special handling necessary, like described [[J-Link_Reset_Strategies#Type_1:_Core | here]].
 
*The devices uses Cortex-M Rest Pin, no special handling necessary, like described [[J-Link_Reset_Strategies#Type_2:_ResetPin | here]].
 
*The device uses custom reset:.....
 
 
==Limitations==
 
===Dual Core Support===
 
Some XXX devices feature a second core. Right now, the J-Link software does support the main core, only. Support for the second core is planned for future versions.
 
 
===Attach===
 
Attach is not supported by default because the J-Link initializes certain RAM regions by default.
 
   
 
==Evaluation Boards==
 
==Evaluation Boards==
  +
*NXP NCJ29D5 UWB Shield Board V4 evaluation board: [[NXP LID2435]]
*[SiliconVendor] [EvalBoardName] evaluation board: http://techwiki.segger.local/WikiTemplateEvalBoard
 
   
 
==Example Application==
 
==Example Application==
  +
*NXP NCJ29D5 UWB Shield Board V4 evaluation board: [[NXP LID2435#Example Project]]
*[SiliconVendor] [EvalBoardName] evaluation board: http://techwiki.segger.local/WikiTemplateEvalBoard#Example_Project
 

Revision as of 11:23, 10 October 2023

The NXP NCJ29D5 are Ultra-Wideband (UWB) ICs designed specifically to meet the connectivity and safety needs of the global automotive industry.

Flash Banks

Internal Flash

Flash Bank Base address Size J-Link Support
Normal-Domain Application 0x00200000 128 KB YES.png
RX Radio Configurations 0x00238A00 8 KB NO.png
TX Radio Configurations 0x0023AA00 8 KB NO.png
Customer Configuration Page 0x0023C000 512 B NO.png
Baseband DSP Firmware 0x00230000 35 KB NO.png

ECC Flash

  • Device has ECC flash, reading of un-programmed or erased areas will result in an error.
  • Dedicated verify and blank check functions are implemented.

Watchdog Handling

  • The device has a watchdog which is enabled by default after Reset with 20s timeout.
  • On connect, the reset source of the watchdog will be disabled, so it keeps running, but doesn't force a reset.

Attach

  • Attach is supported.

Device Specific Handling

Reset

  • The devices uses normal Cortex-M reset.
  • After Reset Watchdog is disabled as described above.

Evaluation Boards

  • NXP NCJ29D5 UWB Shield Board V4 evaluation board: NXP LID2435

Example Application