Part Number: TMS320F28030
Using a xds100, is it required that pins gpio 12 and 17 be shorted to gnd that TRST be pulled high
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: TMS320F28030
Using a xds100, is it required that pins gpio 12 and 17 be shorted to gnd that TRST be pulled high
I can program the flash. To boot from flash I short the TRSET.
the sequence of steps:
1. power on system
2. GPIO34 = GPIO37 = 1 & TRSTn = 1
3. wait ~5sec's
4. short TRST to Ground GPIO34 = GPIO37 = 1 & TRSTn = 0.
5. Boot from flash and excludes source code.
6. Send test script Pass
Test 2
1 short TRST to Ground GPIO34 = GPIO37 = 1 & TRSTn = 0
2. power on system
3. wait ~5sec's
5. Send test script Fails
In case 1 shorting TRST to ground 5 sec after power is applied, pass.
In case 2 shorting TRST to ground before power is applied, fails
.
thanks
Is this normal behavior?
thanks
JW,
No, this is not normal behavior.
Case 2 should be able to run your application code in standalone mode. Case 1 really doesn't make sense to me. Also, I don't see why you have to wait for 5 secs. Is 5 secs a timeout condition before we call a test failed?
Regards,
Manoj
the time is arbitrary, I can wait 5 sec or 10mins the results are the same.
starts in stand alone mode
"Set weak pull-up on GPIO34 = GPIO37 and weak pull down on TRSTn = 0", the codes does not run correctly
Starts emulation mode then transition to stand alone mode
"Set weak pull-up on GPIO34 = GPIO37 and weak pull down on TRSTn = 1", wait, the codes runs correctly.
In all cases the emulator is disconnected
suggestions where to look
Hi, the TRST is being read after startup, Can the issue be in the CMD file?
MEMORY
{
PAGE 0: /* Program Memory */
/* Memory (RAM/FLASH/OTP) blocks can be moved to PAGE1 for data allocation */
RAML0 : origin = 0x008000, length = 0x000800 /* on-chip RAM block L0 */
RAML1 : origin = 0x008800, length = 0x000400 /* on-chip RAM block L1 */
OTP : origin = 0x3D7800, length = 0x000400 /* on-chip OTP ONE TIME PROGRAMABLE MEMORY*/
FLASH : origin = 0x3E8000, length = 0x00FF80 /* FLASH, All sectors combined */
CSM_RSVD : origin = 0x3F7F80, length = 0x000076 /* Part of FLASHA. Program with all 0x0000 e. */
BEGIN_FLASH : origin = 0x3F7FF6, length = 0x000002 /* Part of FLASHA. Used for "boot to Flash */
CSM_PWL_P0 : origin = 0x3F7FF8, length = 0x000008 /* Part of FLASHA. CSM password locations in */
IQTABLES : origin = 0x3FE000, length = 0x000B50 /* IQ Math Tables in Boot ROM */
IQTABLES2 : origin = 0x3FEB50, length = 0x00008C /* IQ Math Tables in Boot ROM */
IQTABLES3 : origin = 0x3FEBDC, length = 0x0000AA /* IQ Math Tables in Boot ROM */
ROM : origin = 0x3FF27C, length = 0x000D44 /* Boot ROM */
RESET : origin = 0x3FFFC0, length = 0x000002 /* part of boot ROM */
VECTORS : origin = 0x3FFFC2, length = 0x00003E /* part of boot ROM */
*/
RAMM2 : origin = 0x008C00, length = 0x000400 /* on-chip RAM block L2 */
RAML3 : origin = 0x009000, length = 0x001000 /* on-chip RAM block L3 */
FLASHB : origin = 0x3F4000, length = 0x002000 /* on-chip FLASH */
}
Entered 0x3F7FF6, result: at 0x3F7FF6
jumped to InitSysCtrl()
jumped to Intro0clDel()
jump to Initperipherial clock
Jump to GPIO initPie vector table
Jump to initCpu Timer
Using the debugger it executes as expected
Does the In scripts "EMU mode" dose the EMU mode need to be selected?
Do I need to be concern about the GEL See below:
if (GEL_IsInRealtimeMode()) /* If in real-time-mode */
{
}
else /* Put device in C28x mode */
{
C28x_Mode();
}
Unlock_CSM();
Device_Cal();
CLA_Clock_Enable(); /* Enable CLA clock - allows the debugger to set CLA breakpoints after reset */
// Uncomment for the desired boot-mode on a reset:
// EMU_BOOT_SARAM(); /* Set EMU Boot Variables - Boot to SARAM */
// EMU_BOOT_FLASH(); /* Set EMU Boot Variables - Boot to flash */
}