Difference between revisions of "Realtek Ameba D"

From SEGGER Wiki
Jump to: navigation, search
Line 1: Line 1:
 
__TOC__
 
__TOC__
The '''Realtek Ameba D''' are dual core K0 & K4 microprocessors with WIFI and Bluetooth.
+
The '''Realtek Ameba D''' are dual core (K0/K4) microprocessors with WIFI and Bluetooth.
   
 
==Flash Banks==
 
==Flash Banks==
Line 6: Line 6:
 
{| class="seggertable"
 
{| class="seggertable"
 
|-
 
|-
! Flash Bank || Base address !! Size || J-Link Support
+
! Flash Bank || Base address !! Size || J-Link Support || Limitations
 
|-
 
|-
| [BANK_NAME] || [BANK_BASE_ADDRESS] || Up to [FLASH_SIZE] KB || style="text-align:center;"| {{YES}} / {{NO}}
+
| QSPI || 0x08000000 || 4 MB || style="text-align:center;"| {{YES}} || only for RTL872xDF devices
 
|}
 
|}
   
====ECC Flash [OPTIONAL]====
 
*Describe ECC Flash restriction here.
 
   
 
===QSPI Flash===
 
===QSPI Flash===
Line 21: Line 19:
 
! Device !! Base address !! Maximum size !! Supported pin configuration
 
! Device !! Base address !! Maximum size !! Supported pin configuration
 
|-
 
|-
| [DEVICE]|| [BANK_BASE_ADDRESS] || [MAX_SPI_FLASH_SIZE] MB ||
+
| RTL872xCS || 0x08000000 || 16 MB ||
  +
*'''Default''' SCK@B13 CS@B16 D0@B14 D1@B17
*'''[LOADER_NAME]'''
 
*[LOADER_NAME]
 
*[LOADER_NAME]
 
 
|}
 
|}
   

Revision as of 12:29, 6 March 2023

The Realtek Ameba D are dual core (K0/K4) microprocessors with WIFI and Bluetooth.

Flash Banks

Internal Flash

Flash Bank Base address Size J-Link Support Limitations
QSPI 0x08000000 4 MB YES.png only for RTL872xDF devices


QSPI Flash

QSPI flash programming requires special handling compared to internal flash. For more information about this, please see the QSPI Flash Programming Support article.
J-Link supports multiple pin configurations for [DEVICE]. The default loader is marked in bold.

Device Base address Maximum size Supported pin configuration
RTL872xCS 0x08000000 16 MB
  • Default SCK@B13 CS@B16 D0@B14 D1@B17

ECC RAM [OPTIONAL]

  • Describe ECC RAM restriction here.

Vector Table Remap [OPTIONAL]

  • Describe Vector Table Remap here..

Watchdog Handling

  • The device does not have a watchdog.
  • 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 here.
The [DeviceFamily]family comes with a variety of multi-core options.
Some devices from this family feature a secondary core which is disabled after reset / by default.
Some of the are available with enabled lockstep mode, only.
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
  • Enables debugging

Reset

  • Device specific reset is performed, see XXX

Attach

  • Attach is not supported because the J-Link initializes certain RAM regions by default

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

Reset

  • The devices uses normal Cortex-M reset, no special handling necessary, like described here.
  • The devices uses Cortex-M Core reset, no special handling necessary, like described here.
  • The devices uses Cortex-M Rest Pin, no special handling necessary, like described 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

Example Application