Difference between revisions of "Analog ADuCM430"
(Created page with "__TOC__ This article describes the device specific handling for Analog Device's ADuCM430 family which is based on Cortex-M3. ==Flash Banks== ===Internal Flash=== {| class="se...") |
|||
(3 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
__TOC__ |
__TOC__ |
||
− | This article describes the device specific handling for Analog |
+ | This article describes the device specific handling for Analog Devices ADuCM430 family which is based on Cortex-M3. |
==Flash Banks== |
==Flash Banks== |
||
Line 15: | Line 15: | ||
The J-Link software performs a device specific reset which ensures that the MCU is not halted after the boot ROM has been executed but before starting the user application code. |
The J-Link software performs a device specific reset which ensures that the MCU is not halted after the boot ROM has been executed but before starting the user application code. |
||
==Evaluation Boards== |
==Evaluation Boards== |
||
− | *Analog |
+ | *Analog Devices EV-ADuCM340ARDZ: [[Analog Devices EV-ADuCM340ARDZ]] |
+ | |||
==Example Application== |
==Example Application== |
||
− | *Analog |
+ | *Analog Devices EV-ADuCM340ARDZ: [[Analog Devices EV-ADuCM340ARDZ#Example_Project]] |
Revision as of 11:15, 10 October 2023
Contents
This article describes the device specific handling for Analog Devices ADuCM430 family which is based on Cortex-M3.
Flash Banks
Internal Flash
Base address | Size | J-Link Support |
---|---|---|
0x00000000 | Up to 1 MB |
Device Specific Handling
Reset
The J-Link software performs a device specific reset which ensures that the MCU is not halted after the boot ROM has been executed but before starting the user application code.
Evaluation Boards
- Analog Devices EV-ADuCM340ARDZ: Analog Devices EV-ADuCM340ARDZ
Example Application
- Analog Devices EV-ADuCM340ARDZ: Analog Devices EV-ADuCM340ARDZ#Example_Project