![Ronetix PEEDI User Manual Download Page 94](http://html1.mh-extra.com/html/ronetix/peedi/peedi_user-manual_1485040094.webp)
Using PEEDI
[PLATFORM_Cortex-M]
JTAG_CHAIN = AUTO x 5,4 ; automatically detect up to 4 CPUs
in the JTAG chain
JTAG_CLOCK = 100, 5000 ; JTAG Clock in [kHz]
TRST_TYPE = OPENDRAIN ; type of TRST output: OPENDRAIN or
PUSHPULL
RESET_TIME = 20 ; length of RESET pulse in ms; 0 means
no RESET
CORE0 = Cortex-M,1; TAP is CortexM3 CPU
CORE0_STARTUP_MODE = RESET ; stop the core immediately after reset
CORE0_ENDIAN = LITTLE ; core is little endian
CORE0_BREAKMODE = HARD ; breakpoint mode
CORE0_INIT = INIT_STM32 ; init section for STM32
CORE0_FLASH = FLASH_STM32 ; FLASH section parameters
CORE0_WORKSPACE
= 0x20000000, 0x4000 ; workspace for agent
programming
CORE0_PATH = "tftp://192.168.3.1"
CORE1 = Cortex-M,3; TAP is CortexM3 CPU
CORE1_STARTUP_MODE = RESET ; stop the core immediately after reset
CORE1_ENDIAN = LITTLE ; core is little endian
CORE1_BREAKMODE = HARD ; breakpoint mode
CORE1_INIT = INIT_STM32 ; init section for STM32
CORE1_FLASH = FLASH_STM32 ; FLASH section parameters
CORE1_WORKSPACE
= 0x20000000, 0x4000 ; workspace for agent
programming
CORE1_PATH = "tftp://192.168.3.1"
CORE2 = Cortex-M,5; TAP is CortexM3 CPU
CORE2_STARTUP_MODE = RESET ; stop the core immediately after reset
CORE2_ENDIAN = LITTLE ; core is little endian
CORE2_BREAKMODE = HARD ; breakpoint mode
CORE2_INIT = INIT_STM32 ; init section for STM32
CORE2_FLASH = FLASH_STM32 ; FLASH section parameters
CORE2_WORKSPACE
= 0x20000000, 0x4000 ; workspace for agent
programming
CORE2_PATH = "tftp://192.168.3.1"
CORE3 = Cortex-M,7; TAP is CortexM3 CPU
CORE3_STARTUP_MODE = RESET ; stop the core immediately after reset
CORE3_ENDIAN = LITTLE ; core is little endian
CORE3_BREAKMODE = HARD ; breakpoint mode
CORE3_INIT = INIT_STM32 ; init section for STM32
CORE3_FLASH = FLASH_STM32 ; FLASH section parameters
CORE3_WORKSPACE
= 0x20000000, 0x4000 ; workspace for agent
programming
CORE3_PATH = "tftp://192.168.3.1"
Each core has its own TCP port number to wait for a debug session. The port number is the number
specified in the DEBUGGER section of the target configuration file plus the number of the core.
For example if the port specified is 2000 and the core number is 2 (starting from 0), then you should
connect to PEEDI for a debug session at TCP port 2002:
PEEDI User’s Manual
94