Ronetix PEEDI User manual

PEEDI
Powerful Embedded Ethernet Debug Interface
User’s Manual
Version 2.00
DEVELOPMENT TOOLS

Acknowledgement
Acknowledgement
July,2016
Ronetix has made every attempt to ensure that the information in this document is accurate and complete.
However, Ronetix assumes no responsibility for any errors, omissions, or for any consequences resulting
from the use of the information included herein or the equipment it accompanies. Ronetix reserves the right
to make changes in its products and specifications at any time without notice. Any software described in this
document is furnished under alicense or non-disclosure agreement. It is against the law to copy this software
on magnetic tape, disk, or other medium for any purpose other than the licensee’s personal use.
Ronetix Development Tools GmbH
Giefinggasse 2
1210 Vienna
Austria
Tel: [phone]
Fax: [phone]
Web: www.ronetix.at
E-Mail: [e-mail]
Acknowledgments:
ARM, ARM7, ARM9, ARM11, Cortex-M, Cortex-A and Thumb are trademarks of ARM Ltd.
PowerPC and ColdFire are trademarks of Freescale Ltd.
Blackfinis trademark of Analog Devices Ltd.
Windows, Win32, Windows CE are trademarks of Microsoft Corporation.
Ethernet is a trademark of XEROX.
MIPS is a trademark of MIPSTechnologies.
AVR32 is a trademark of Atmel.
All other trademarks are trademarks of their respective companies.
Copyright© 2005-2016 Ronetix Development Tools GmbH
All rights reserved.
PEEDI User’s Manual 1www.ronetix.at

Contents
Contents
1 Introduction 8
1.1 PEEDI in the development process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1.1 Single developer environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1.2 Multiple developers environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 PEEDI in the manufacturing process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2.1 PEEDI as a standalone FLASH programmer . . . . . . . . . . . . . . . . . . . . . . . 10
1.2.2 PEEDI as a device tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2.3 High productivity with the Multi Core feature . . . . . . . . . . . . . . . . . . . . . . . . 11
2 Installation 13
2.1 Hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.1 Connection instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3 Using PEEDI 15
3.1 PEEDI interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Setup with RedBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.1 RedBoot Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.2 Firmware update procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Update via RS232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Update via Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.3 RedBoot commands used with PEEDI . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
fconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
memtest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3 Configure PEEDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3.1 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3.2 Target configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Section LICENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Section DEBUGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
REMOTE_PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
FLASH FLASHn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Section TARGET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
PLATFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Section PLATFORM_ARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Global parameters for all ARM cores . . . . . . . . . . . . . . . . . . . . . . . . 23
JTAG_CHAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
JTAG_CLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
JTAG_TDO_DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
TRST_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
RESET_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
WAKEUP_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
TIME_AFTER_RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
WDKICK_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
DBGREQ_OUTPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Core specificparameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
COREn_STARTUP_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
COREn_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
COREn_FLASHm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
COREn_ENDIAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
COREn_VECTOR_CATCH_MASK . . . . . . . . . . . . . . . . . . . . . . . . 26
COREn_BREAKMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
COREn_BREAK_PATTERN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
COREn_WORKSPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
PEEDI User’s Manual 2www.ronetix.at

Contents
COREn_DATASPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
COREn_DCC_PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
COREn_PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
COREn_FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
COREn_LOCKOUT_RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . 28
COREn_OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Section PLATFORM_ARM11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
COREn_USE_FAST_DOWNLOAD . . . . . . . . . . . . . . . . . . . . . . . . 29
COREn_DCC_PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Section PLATFORM_Cortex-M & Section PLATFORM_Cortex-M_SWD . . . . . . . . . 29
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
PERIODIC_TASK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
COREn_SWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
COREn_PROFILING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Section PLATFORM_Cortex-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Section PLATFORM_XSCALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
COREn_USE_FAST_DOWNLOAD . . . . . . . . . . . . . . . . . . . . . . . . 32
COREn_DEBUG_HANDLER_ADDR . . . . . . . . . . . . . . . . . . . . . . . 32
COREn_VECTOR/RELOCATED_UNDEF/SWI/PABORT/DABORT/RES/IRQ/FIQ 33
Section PLATFORM_MPC5200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
COREn_BOOT_ADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
COREn_MEMDELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Section PLATFORM_MPC5500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
COREn_NEXUS3_ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
MPC5XXX_AUX_TAP_CMDCOREn_AUX_TAP_CMD . . . . . . . . . . . . . . 34
Section PLATFORM_MPC8300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
COREn_BOOT_ADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
COREn_RCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
COREn_MMU_PTBASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Section PLATFORM_MPC8500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
COREn_MMU_TRANS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
COREn_MMU_PTBASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Section PLATFORM_QorIQ_P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
COREn_REGLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
COREn_MMU_TRANS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
COREn_MMU_PTBASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
COREn_PMEM_BASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Section PLATFORM_PPC400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Section PLATFORM_COLDFIRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
BDM_CLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
CORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
CORE_MEMMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Section PLATFORM_BLACKFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
COREn_VMEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
COREn_VMEM_WINDOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
COREn_VMEM_PINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
CORE_MEMMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Section PLATFORM_MIPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
PEEDI User’s Manual 3www.ronetix.at

Contents
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Section PLATFORM_AVR32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
COREn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
COREn_BLOCK_ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Section INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Section FLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
NOR FLASH programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
I2C Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
SPIFLASH programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
NAND FLASH programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
OneNAND FLASH programming . . . . . . . . . . . . . . . . . . . . . . . . . . 51
MMC/SD card programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Atmel SAM3/SAM4 programming . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Atmel AVR32UC3 programming . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Freescale Kinetis programming . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
TI/Luminary LM3S programming . . . . . . . . . . . . . . . . . . . . . . . . . . 52
NXP LPC2000 programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Freescale MAC7100 programming . . . . . . . . . . . . . . . . . . . . . . . . . 55
Freescale ColdFire V2programming . . . . . . . . . . . . . . . . . . . . . . . . 55
Freescale MPC5000 programming . . . . . . . . . . . . . . . . . . . . . . . . . 56
ST STM32 programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
ST STR7 programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
ST STR9 programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
TI TMS470 programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
PIC32, SmartFusion A2F, ADuC, EFM32 programming . . . . . . . . . . . . . . 58
CHIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
PART_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
BANK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
CHECK_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
ACCESS_METHOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
CHIP_WIDTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
CHIP_COUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
CHIP_SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
BASE_ADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
SPI_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
AUTO_ERASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
AUTO_LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
CPU_CLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
SECURE_FLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
SET_VECTORS_CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . 63
DATA_BANK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
BANK_SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
F2F4_PSIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
PROTECTION_KEY0 - PROTECTION_KEY3 . . . . . . . . . . . . . . . . . . 64
ALLOW_ZERO_KEYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
SPI_DIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
nSPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
nCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
SPI_SPCKSPI_MISOSPI_MOSISPI_CS . . . . . . . . . . . . . . . . . . . . . 66
CMD_BASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
DATA_BASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
ADDR_BASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
CS_ASSERT/RELEASEALE_ASSERT/RELEASECLE_ASSERT/RELEASE . . 67
BAD_BLOCK_TABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
BAD_BLOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
ERASE_BAD_BLOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
PEEDI User’s Manual 4www.ronetix.at

Contents
SWAP_BI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
OOB_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
DAVINCI_UBL_DESCIPTOR_MAGIC . . . . . . . . . . . . . . . . . . . . . . . 70
DAVINCI_UBL_DESCIPTOR_ENTRY_POINT . . . . . . . . . . . . . . . . . . 70
DAVINCI_UBL_DESCIPTOR_LOAD_ADDR . . . . . . . . . . . . . . . . . . . 70
DAVINCI_UBL_MAX_IMAGE_SIZE . . . . . . . . . . . . . . . . . . . . . . . . 70
NUM_ECC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
HEADER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
IPS_BASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
SPIFI_BASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
NCB_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
LDLB_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
SERIAL_NUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
I2C_ADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
I2C_DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
SDA_SETSDA_CLRSDA_INSDA_OUTSDA_READSCL_SETSCL_CLR . . . . 73
CS_ASSERTCS_RELEASESCLK_SETSCLK_CLRMOSI_SETMOSI_CLRMISO_READ 73
Section OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
ITEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Section SERIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
BAUD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
STOP_BITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
PARITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
TCP_PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Section TELNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
PROMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
BACKSPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Section DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Section ACTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.4 CPU specific considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.4.1 Philips LPC2000 family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.4.2 ST STM32 family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.4.3 Intel XScalefamily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.4.4 Freescale PowerQUICC II Pro MPC83XX family . . . . . . . . . . . . . . . . . . . . . . 79
3.4.5 Analog Devices Blackfin family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.5 Boot sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.6 Multiple core support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
3.7 Script execution using the front panel interface . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.8 Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
3.9 ARM DCC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
3.10 Working with Insight/gdb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.11 Debugging Linux kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.12 Target OS thread awareness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.13 Working with CLI (Command Line Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.13.1 File path convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.13.2 CLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
go . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
gm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
execute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
PEEDI User’s Manual 5www.ronetix.at

Contents
set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
jtag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
beep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
quit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
info flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
info registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
info target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
info config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
info ice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
info cp15, info cp14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
info spr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
info ctrl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
info breakpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
memory read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
memory write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
memory or . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
memory and . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
memory crc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
memory load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
memory multi load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
memory verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
memory dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
memory test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
flash set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
flash blank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
flash erase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
flash lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
flash unlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
flash query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
flash program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
flash multi erase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
flash multi blank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
flash multi program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
flash multi verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
flash verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
flash dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
flash read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
flash info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
flash find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
flash this . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
flash this hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
flash this nvmbit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
flash this secure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
flash this option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
flash this option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
flash this write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
flash this prot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
flash this prot read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
flash this prot program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
flash this ppb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
PEEDI User’s Manual 6www.ronetix.at

Contents
flash this isc_erase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
flash this isc_conf_write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
flash this isc_conf_read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
flash this isc_conf_boot_bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
flash this isc_conf_lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
breakpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
breakpoint add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
breakpoint add hard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
breakpoint add watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
breakpoint delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
breakpoint list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
card cd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
card md . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
card rd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
card dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
card copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
card type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
card delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
card rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
eeprom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
eeprom dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
eeprom copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
eeprom type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
eeprom delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
eeprom rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
eeprom format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
eeprom alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
3.13.3 Using aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
3.13.4 Using scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
3.14 Working with the FLASH programmer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.15 Multiple FLASH support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.16 Working with a MMC/SD memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.17 JTAG cable adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
3.18 PEEDI licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
4 Specifications 135
4.1 JTAGTarget connector signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4.2 RS232 Connector (DB9F, female) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
4.3 Schematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5 FAQ 138
6 Glossary 141
7 PEEDI Package contents 143
8 Warranty 144
A Sample target configuration files 145
PEEDI User’s Manual 7www.ronetix.at

Introduction
1 Introduction
PEEDI (Powerful Embedded Ethernet Debug Interface) is an EmbeddedICE solution that enables you to
debug software running a wide variety of processor cores via the JTAG port. JTAG is an IEEE standardized
protocol that enables full control of the CPU core, giving the opportunity to debug embedded software. The
PEEDI will help to reduce Time-To-Market and increase the quality of the end product.
PEEDI is a debugging and development tool that provides the ability to see what is taking place in the target
system and control its behavior. PEEDI provides the services needed to perform all debugging operations.
It receives command packets over the communication link and translates them into JTAG operations that are
needed toprovide the specificservice. It can control the operation of thetarget processor and target system,
start and stopthe processor's execution; it can set breakpoints ina program, examine and store values in the
processor’s registers, and examine and store program code or data in the target system’s memory.
PEEDI can work in cooperation with a host computer or autonomously using a MMC/SD card.
1.1 PEEDI in the development process
In the development process PEEDI can be used mainly as a debugger JTAG interface and FLASH program-
mer.
Two major configurations are possible here:
- Single developer environment
- Multiple developers environment
1.1.1 Single developer environment
Using the developer’s PC as a host computer - this is suitable for small projects. Here all necessary tools for
compiling and debugging the project must be installed on thedevelopers PC, including fileserver (TFTP, FTP
or HTTP) allowing PEEDI to retrieve configuration files or executableimages. Inthis (Figure 1) configuration
thedeveloper’s PCmust beconnected to PEEDIina commonLAN usingcrossoverpatch cable orby Ethernet
via hub/switch.
PEEDI User’s Manual 8www.ronetix.at

Introduction
Figure 1: A simple configuration
1.1.2 Multiple developers environment
Dedicated server with all the necessary development tools installed is used for a host. The developer uses a
PC only as a graphical terminal to logon to theserver. No specificsoftware is installed on thedeveloper’s PC,
so it is very easy to set another working environment for a new developer forthe project - just add a new user
on the server and make a copy of the project source and make files in the user’s home directory. Of course
any source control tool, suchas CVS or Visual Source Safe,can beused forsynchronizing theproject files. In
this configuration (Figure 2) all devices (the server, the developers’ PCs and all PEEDIs) must be connected
in a common LAN.
PEEDI User’s Manual 9www.ronetix.at

Introduction
Figure 2: An example of multiple programmer development
1.2 PEEDI in the manufacturing process
PEEDI can be used in the manufacturing process as a tool for testingthe device after it is assembled and as
a FLASH programmer to program the device firmware. In both scenarios the host computer is not required
because all theoperations can be formed as script files and executedusing the PEEDI’sfront panel interface.
If all the necessary files are stored on the MMC/SD card the Ethernet connection is not required as well.
1.2.1 PEEDI as a standalone FLASH programmer
PEEDI can be used as a FLASH programmer in two ways:
- The first way (Figure 3) is to connect to PEEDI via telnet and executeFLASH command and script files
from thecommand lineinterface (CLI). This method enables users to seeall the statusmessages inan
easy,understable format i.e. warnings and errors and therefore, maybe the preferred method.
PEEDI User’s Manual 10 www.ronetix.at

Introduction
Figure 3:
- The second way (Figure 4) is to use the front panel interface to choose, startand observe the status of
scripts, which invokes the desired FLASH commands. Here you can define an AUTORUN script to be
executedevery time a target is connected; this way there is no need to start the script manually - very
useful and timesaving when large volumes of target boards need to be programmed.
Figure 4:
1.2.2 PEEDI as a device tester
Here the PEEDI can be used in the same manner as in the previous section - making telnet connection or
through the front panel interface.
Depending on the specifics of what is tobe testedtwo options can be applied:
- Execute commands that directly make some sort of test i.e. flash verify,memory test, etc.
- Download executable code into target, which will perform the desired test and set a CPU register or
memory on exit to a value showing the result of the test. This option is often preferred because there
are virtually no limits to testexamples a user can create.
1.2.3 High productivity with the Multi Core feature
With the “Multi Core” feature users can increase productivity by working on upto four targets simultaneously
using a single PEEDI. The targets must be chained using a multi-core adapter (Figure 5) available from
Ronetix.
PEEDI User’s Manual 11 www.ronetix.at

Introduction
Figure 5:
PEEDI User’s Manual 12 www.ronetix.at

Installation
2 Installation
This chapter will explain how to connect PEEDI to the target and how to configure all the tools necessary for
development.
Two major steps must be followed in order to set up a working PEEDI:
- Connect all required cables, thisincludes apower cord, target cableand if necessary anEthernet cable,
which will provide connection to a host computer or file server.
This is explained in subsection2.1 Hardware installation.
- Install and configure insight/gdb debugger.
This is explained in subsection2.2 Software installation.
2.1 Hardware installation
Figure 6: Front panel and side connectors
Figure 7: Rear panel connectors
2.1.1 Connection instructions
To connect the PEEDI interface unit to your host and to the target hardware:
1. Connect the host computer to an Ethernet network or directly to the PEEDI as required:
A. Direct host connection
PEEDI User’s Manual 13 www.ronetix.at

Installation
Figure 8:
B. LAN Connection
Figure 9:
2. Connect the PEEDI interface unit to the target hardware, using the supplied JTAG adapter and cable.
The JTAG adapter must be on the PEEDI side of the JTAG cable. If your target JTAG port pinout is not
standard, you may need tomake your own target cableconsidering thePEEDI JTAG connector pinout.
Refer to subsection4.1 JTAG Target connector signals for the PEEDI JTAG connector pinout.
Figure 10:
3. Power up the target hardware.
4. Connect the external power supply to the PEEDI and apply power.
5. When PEEDI boots, if you have a terminal connected to the RS232 port of PEEDI you will see various
statusmessages.
2.2 Software installation
See ’Cross development with GNU toolchain and Eclipse’:
http://www.ronetix.at/software.html
PEEDI User’s Manual 14 www.ronetix.at

Using PEEDI
3 Using PEEDI
This chapter will explain PEEDI’s operating modes, PEEDI’s interface and the basic steps of configuring the
software tools for working with PEEDI.
To startusing PEEDI you need to:
- configure network settings
- make target configuration file
3.1 PEEDI interface
Figure 11:
Figure 12:
PEEDI User’s Manual 15 www.ronetix.at

Using PEEDI
1 Power LED
2 Target power LED
3 Ethernet connect/activityLED
4 Target connect/activity LED
5 Script number/status LED display
6 Next script button
7 Start script button
8 Target connector
9 MMC/SD card slot
10 RS232 port
11 Power supply
12 Reset button
13 Ethernet port
3.2 Setup with RedBoot
RedBoot is a bootstrap loader, which during normal boot-up is used to load and launch PEEDI’s executable
image. RedBoot is also used to update PEEDI’s firmware and to configure network settings, which are later
used by PEEDI.RedBoot has some useful testing facilities likeping and memtest.
3.2.1 RedBoot Configuration
RedBoot and PEEDI share the same network settings. To set the network you need to connect a simple
terminal application set to 115200, 8, N, 1 (for example HyperTerminal) to the PEEDI’s RS232 port using a
serial straight-through cable with DB9M (male) and DB9F (female) connectors on each end. Next step is to
restart PEEDI by pressing the RESET button while holding both front panel buttons in. This will tell RedBoot
not to load and launch the PEEDI executable if available, but to wait for connection on RS232 or Ethernet.
While rebooting RedBoot should output some diagnostic information on the serial port which youshould see.
When RedBoot is ready to accept commands, it will show the command line prompt ’RedBoot> ’. Now you
can use the fconfig command to set and save to FLASH all the parameters. When asked for different
parameters please enter the following:
WARNING:
If PEEDIis set to get its network settings from a DHCP server and if theEthernet cable
is unplugged or there is no DHCP server on the Ethernet, it may take some time for
PEEDI to boot. To avoid this, make sure PEEDI can reach a DHCP server.
Use DHCP for network configuration: yes /[no][ENTER]
Gateway IP address: X.X.X.X
Local IP address: X.X.X.X
Local IP address mask: X.X.X.X
Default server IP address, used by RedBoot and PEEDI: X.X.X.X
Note:
Instead of X’s enter IP address digits
Next you will be asked forthe path of the configuration file:
PEEDI User’s Manual 16 www.ronetix.at

Using PEEDI
Target config file path:
Accepted paths for the different protocols are:
tftp://server/sub_directory/filename.cfg
ftp://user:password@server/sub_directory/filename.cfg
http://server/sub_directory/filename.cfg
card://sub_directory/filename.cfg
Note:
A server is indicated by its IP address.
Now youmay enter DNS server used by RedBoot to resolve hostnames.
DNS server IP address:
If left blank and PEEDI is set toget the network configuration from DHCP server, the DNS server IP will also
be taken from the DHCP.
Next you will be prompted for the RedBoot telnet port:
RedBoot telnet port: 23
Finally youmay enter the update command default filepath:
Update filepath:
<1> - http://www.ronetix.at/download/firmware/fw_peedi_revA_last.bin
<2> - tftp://192.168.3.1/fw_peedi_rev.A_last.bin
<custom path>
Path: 1
If you have changed some of the parameters you will be ask to save them at the end. If youconfirm to save
them they will be take effectafter the next start.
3.2.2 Firmware update procedure
First of all youneed to reset PEEDI by pressing the RESET button on the back while holding both front panel
buttons in. This will tell RedBoot not to load and launch the PEEDI executable, but to wait for connection on
RS232 or Ethernet.
Entering the RedBoot command line prompt canbe done usingtwo different ways: via RS232 port usingserial
straight-through cable and a simpleterminal application set to 115200, 8, N, 1 or if the network is configured
you can connect using telnet application.
Once in the RedBoot’s command line prompt (verify by pressing ENTER, RedBoot’s prompt should appear -
’RedBoot> ’), you can update the firmware the following ways:
Update via RS232
Firmware update via RS232 is supported by Redboot v15.12.3 or newer.
If you want to update PEEDI via RS232 your terminal application must support XMODEM or YMODEM pro-
tocols. Now execute:
PEEDI User’s Manual 17 www.ronetix.at

Using PEEDI
RedBoot> update xmodem
or
RedBoot> update ymodem
to tell RedBoot to start listening on RS232 port for incoming packets. Next tell your terminal application to
start downloading the PEEDI firmware.
Update via Ethernet
Now youmay use update command to update the PEEDI firmware. You can update using TFTP,HTTP. The
syntax of the update command is:
update [FILEPATH | NUMBER]
The command shown below will attempt to download the firmware using the default filepath entered while
configuring RedBoot using thefconfig command or the pathused when lastupdate command is invoked:
RedBoot> update
If not changed, the default update path points to the last versionof the firmware directly on the RONETIX web
site. If update 1 is entered alsothe last versionof the firmware directly from the RONETIX web sitewill be
downloaded.
The following command will attempt to download the firmware using the HTTP protocol from a directory on
the server (this syntaxcan be used with TFTP too):
RedBoot> update http://server/subdir/file.bin
After you enter the command using your specific conditions, if the host is accessible and the file is present
you should see this:
PEEDI User’s Manual 18 www.ronetix.at

Using PEEDI
RedBoot> update
load -r -m tftp -b 0x100000 -h 192.168.1.1 fw_peedi_revA_last.bin
................................................................
Raw file loaded 0x00100000-0x002ab1bf, assumed entry at 0x00100000
Current Firmware:
-----------------
Hardware Ver. : 1.2
Software Ver. : 1.0
New Firmware:
-------------
Hardware Ver. : 1.2
Software Ver. : 1.1
Install PEEDI firmware version 1.1 (y/[n])? y
WARNING: The firmware image you are trying to load
exceeds your update license. Continue update (y/[n])? y
fis delete peedi
... Erase from 0x01840000-0x019f0000: ...........................
... Erase from 0x019f0000-0x01a00000: .
... Program from 0x007f0000-0x00800000 at 0x019f0000: .
fis create -b 0x100000 -l 0x1AB1C0 -f 0x1840000 -e 0x600040 -r 0x600000
peedi
... Erase from 0x01840000-0x019f0000: ...........................
... Program from 0x00100000-0x002ab1c0 at 0x01840000:
...........................
... Erase from 0x019f0000-0x01a00000: .
... Program from 0x007f0000-0x00800000 at 0x019f0000: .
RedBoot>
3.2.3 RedBoot commands used with PEEDI
These commands are used to update, configure, test and run PEEDI:
fconfig
Syntax: fconfig
Description:
Enter RedBoot and PEEDI configuration parameters
Argument:None
Example: fconfig
PEEDI User’s Manual 19 www.ronetix.at