AM437x IDK system debugging issue

nima shokouhfar

Other Parts Discussed in Thread: SYSBIOS

Hi all
I m dealing with syscalls.c issue for very long time.I read most threads regarding this issue , I even consulted our local FAE.

The problem can be explained in this way:

when I attempt to debug the project after "power on" or "physical system restart" every thing works fine ,however if I try to debug the session for second run the debug session will fail .in other words it will call the syscalls.c .

if I step through the program the syscalls.c will be called after execution of following line

you could check my debug and target configurations on the following images

I have to mention so far this configuration gives me the best result ,in other words if I change any thing I wont be able to start the debug session at all . specially "jtag clock" and "reset the target on debug".

some more previously I had issue of
Can't find a source file at "/db/ztree/library/trees/xdctargets/xdctargets-h32x/src/gnu/targets/arm/rtsv7A/syscalls.c"
Locate the file or edit the source lookup path to include its location.

which I solve it by manually locating the file through browse window

Thanks in advance

over 9 years ago

0 Biser Gatchev-XID over 9 years ago

TI__Guru**** 393215 points

Hi,

I will ask the ISDK team to look at this.

0 JJD over 9 years ago in reply to Biser Gatchev-XID

TI__Guru* 86180 points

Can you explain what you are exactly doing on your "second run". Most likely, the processor is not in a proper state and a reset would be required.

Regards,

James

0 lding over 9 years ago in reply to JJD

TI__Guru* 95265 points

Do you run any example program from Processor SDK 2.0.2.11? What is the application? Why you need to run a program again without reset the ARM core?

Regards, Eric

0 nima shokouhfar over 9 years ago in reply to JJD

Prodigy 200 points

Hi james

Thanks for prompt reply.
Actually I m debugging exactly same source code no change at all, after the power on or physical system reset the code executed properly.however if I want to debug the exact same code for second run I would encounter syscall.c
.I have to mention that my other colleague do not encounter this issue at all.

In order to avoid any confusion I already uploaded the video on youtube ,you could check the following link for further information:

https://www.youtube.com/watch?v=uGHakEJVA2M&feature=youtu.be

Best Regards

Nima Shokouhfar

0 nima shokouhfar over 9 years ago in reply to nima shokouhfar

Prodigy 200 points

Hi Eric
Thanks for prompt reply.
I m ok to restart the system every time starting a new debugging session (I meen IDE restart the processor before start debugging). however I m not very comfortable to physically press the restart button every time before debugging session started. beside that my other colleague is using same development board and same CCS IDE however he does not encounter this issue at all.

I have tried example code from sysbios_ind_sdk_2.1.1.2 the result was the same . I have never try any source code from Processor SDK 2.0.2.11 before,therefore I will try and I will let you know the result.

Best Regads
Nima Shokouhfar

0 Vinesh Balan over 9 years ago in reply to nima shokouhfar

TI__Expert 7360 points

Hi,

Taking a look at the video, I see one thing going wrong. After the first loading, to reload you are only "Stopping" the debugger and relaunching it. This doesn't necessarily mean that the board is reset, and as a result when the next load happens the board is in a bad state. If you do a reset(on CCS) before stopping the debugger, it should work fine.

These are the ideal steps to load a program - processors.wiki.ti.com/.../SYSBIOS_Industrial_SDK_Getting_Started_Guide . In case of reloading, you can skip steps 1,2 and 3

Regards,
Vinesh

0 nima shokouhfar over 9 years ago in reply to Vinesh Balan

Prodigy 200 points

Hi Vinesh

thanks for reply.
I tried System reset and then exit debugging session.

I get the following error

Error connecting to the target:
(Error -1141 @ 0x3D58)
Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 6.0.14.5)

this error occurred before loading gel file .

is there a way to configure CCS to perform system reset before executing gel file?

Best regards
Nima Shokouhfar

0 nima shokouhfar over 9 years ago in reply to nima shokouhfar

Prodigy 200 points

please check following link , the case very similar to my case

e2e.ti.com/.../383249

0 nima shokouhfar over 9 years ago in reply to nima shokouhfar

Prodigy 200 points

Finally I Fixed the issue

the issue can be solved by editing GEL file.

open the gel file ,you can find the gel file in the following directory:

C:\ti\ccsv6\ccs_base\emulation\boards\idk_am437x\gel\idk_am437x.gel

replace the content with the following code :

//####################################################
//AM437x IDK GEL

StartUp()
{
GEL_LoadGel("$(GEL_file_dir)/AM437x_EVMs.gel");
GEL_LoadGel("$(GEL_file_dir)/AM437x_MMRs.gel");
GEL_LoadGel("$(GEL_file_dir)/AM437x_Status.gel");
GEL_LoadGel("$(GEL_file_dir)/AM43xx_PLLconfig.gel");
GEL_LoadGel("$(GEL_file_dir)/AM43xx_EMIFconfig_HWlvl.gel");
GEL_LoadGel("$(GEL_file_dir)/AM43xx_ICSSconfig.gel");
}
OnTargetConnect()
{
GEL_AdvancedReset("System Reset");
GEL_Halt();
AM43xx_IDK_EVM_Initialization();
}

Best regards
Nima Shokouhfar

Processors

Processors forum

AM437x IDK system debugging issue