| Chapter 232. Initial Installation | ||
|---|---|---|
 | Part LXXIII. RedBoot User's Guide |  |
Chapter 232. Initial Installation
Table of Contents
232.1. Hardware Installation
Initial installation of RedBoot into the internel or external flash, or EEPROM, of target hardware is described alongside the respective target hardware documentation in the eCos and eCosPro Reference Manual.
![[Note]](pix/note.png) | Note |
|---|---|
The RedBoot installation documentation of outdated hardware and hardware no longer supported has been removed from editions of this document from July 2016 onwards. If the eCos and eCosPro Reference Manual does not contain instructions on installing RedBoot for your hardware, please refer to the [RedBoot User's Guide] or [eCos Reference Manual] accompanying your eCos distribution. |
232.1.1. What to Expect
The initial installation of RedBoot into a target's internal or external flash may normally be achieved using a hardware debugger, an application or tools provided by either the target hardware's manufacturer or the chip vendor of the target hardware, or even RedBoot's flash management commands from a revision of RedBoot running on the target hardware. In the latter case, a RAM executable RedBoot would have been loaded into the target hardware's RAM through the use of a hardware debugger from where it would have been started.
For example:
- ATMEL's SAM-BA In-system Programmer is a vendor specific software tool used for, amongst other, programming binary images into internal or external flash of ATMEL components.
- The Ronetix PEEDI is a hardware debugger that may be used to either program the internal or external flash of target hardware, or may be used to load RedBoot into the RAM (internal, external or otherwise) and commence it's execution, thereby allowing RedBoot to program itself into the flash of the target hardware.
| |  | |
| Chapter 231. Updating RedBoot |  | Part LXXIV. Robust Boot Loader |
| 2024-12-10 | eCosPro Non-Commercial Public License |