Difference between revisions of "Apollo4"
(Created page with "__TOC__ The AmbiqMicro Apollo4 are ultra-low power, Cortex-M4 based. ==Internal Flash== ===Supported Regions=== The internal flash is divided into 2 different regions:<br> *Re...") |
|||
(5 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
+ | [[Category:Device families]] |
||
__TOC__ |
__TOC__ |
||
The AmbiqMicro Apollo4 are ultra-low power, Cortex-M4 based. |
The AmbiqMicro Apollo4 are ultra-low power, Cortex-M4 based. |
||
Line 6: | Line 7: | ||
*Reserved by boot code (0x00000 - 0x17FFF), not accesible. |
*Reserved by boot code (0x00000 - 0x17FFF), not accesible. |
||
*Program Flash (0x18000 - 0x1FFFFFF) |
*Program Flash (0x18000 - 0x1FFFFFF) |
||
− | + | J-Link supports the program flash space. The boot code area is not accessible and cannot be erased or programmed. |
|
+ | |||
==Evaluation Boards== |
==Evaluation Boards== |
||
*Ambiq Micro Apollo4 blue evaluation board: https://wiki.segger.com/AmbiqMicro_Apollo4Blue |
*Ambiq Micro Apollo4 blue evaluation board: https://wiki.segger.com/AmbiqMicro_Apollo4Blue |
||
− | ==Example |
+ | ==Example Project== |
+ | The following example project was created with the SEGGER Embedded Studio project wizard and runs out-of-the-box on the NXP JN5189-DK006. It is a simple Hello World sample linked into the internal flash. |
||
− | *Ambiq Micro Apollo4 blue evaluation board: https://wiki.segger.com/AmbiqMicro_Apollo4#Example_Project |
||
+ | '''SETUP''' |
||
+ | *J-Link software: V6.95c |
||
+ | *Embedded Studio: V5.34 |
||
+ | *Hardware: Ambiq Micro Apollo4 Blue (AMA4B2EVB) |
||
+ | *Link: [[File:AmbiqMicro_Apollo4_IntFlash_TestProject_ES_V534.zip]] |
||
+ | |||
+ | == Recovering unresponsive devices == |
||
+ | It is possible to put an Apollo4 device into an unresponsive state in which debug probes cannot establish a debug connection to the target device anymore.<br> |
||
+ | This could be achieved by downloading an application which resets the device early in user code, causing the device to continuously reset itself.<br> |
||
+ | |||
+ | An AMAP4BEVB board with an unresponsive device may be recovered by rewriting on-chip security configuration for the boot options. |
||
+ | However, due to the confidentiality of the security implementation, you need to get in touch in Ambiq for details. |
Latest revision as of 14:25, 10 May 2024
Contents
The AmbiqMicro Apollo4 are ultra-low power, Cortex-M4 based.
Internal Flash
Supported Regions
The internal flash is divided into 2 different regions:
- Reserved by boot code (0x00000 - 0x17FFF), not accesible.
- Program Flash (0x18000 - 0x1FFFFFF)
J-Link supports the program flash space. The boot code area is not accessible and cannot be erased or programmed.
Evaluation Boards
- Ambiq Micro Apollo4 blue evaluation board: https://wiki.segger.com/AmbiqMicro_Apollo4Blue
Example Project
The following example project was created with the SEGGER Embedded Studio project wizard and runs out-of-the-box on the NXP JN5189-DK006. It is a simple Hello World sample linked into the internal flash. SETUP
- J-Link software: V6.95c
- Embedded Studio: V5.34
- Hardware: Ambiq Micro Apollo4 Blue (AMA4B2EVB)
- Link: File:AmbiqMicro Apollo4 IntFlash TestProject ES V534.zip
Recovering unresponsive devices
It is possible to put an Apollo4 device into an unresponsive state in which debug probes cannot establish a debug connection to the target device anymore.
This could be achieved by downloading an application which resets the device early in user code, causing the device to continuously reset itself.
An AMAP4BEVB board with an unresponsive device may be recovered by rewriting on-chip security configuration for the boot options. However, due to the confidentiality of the security implementation, you need to get in touch in Ambiq for details.