TMS320F28388D: How to create TI-RTOS(SYS/BIOS) project for TMS320F28388x

Hello Whitney 

Thank you for your answer. In my case it was necessary to click "Refresh" button and and project window was changed in proper way. Now I am thinking about  - where I have lost this information.

About  tcpEchoF2838X. Yes I followed this guide and the it work as described. When I have written about issues I meant the  next behaviour 

1) After upload firmware to the Cortex_M4_0, the firmware fall to the infinite loop in place to stop on the break point om the main().

2)Only after  clicking  button "Restart" it stop on the stack initialization. It is line 192  of  boot.asm file  in C:\ti\bios_6_76_01_12\packages\ti\targets\arm\rtsarm directory. 

3) After that is possible to click "Resume" button  to Run . But I can not set break points.  I follow  all recommendation about hidden break points 

   (Uncheck "Halt at program exit, Enable CIO function ,  Restore  breakpoints from previous session"  options ) . But it was not helpful.

I thought that is problem of mentioned above example but now I create from examples of SYS/BIOS projects for 320F28388D "hello" project and 

this project has the same problem. I can`t set breakpoint, it does not stop at the main() despite the check box  - start to the main "On the program load and restart" is checked. So can suspend it only at exit .   So I understand that is the common problem of projects  SYS/BIOS for TMS320F28388x . May be it use the some model which prohibit to use some resources? At least,  projects for Cortex_M4_0 but without support SYS/BIOS runs perfectly and as it expected with all break points. 

So do I have to create new thread for this Issue (I see the TI think that it resolved. But why ?)or we can resolve this issue in this thread?

Best regards

Andrii Shevchuk

I tried the F28388D M4 version of the "hello" example in CCS v10.1.1.00004 and couldn't reproduce the issue. As long as I had disabled the "Program/Memory Load Options" you already mentioned, I could still place a break point and jump to main when I clicked the "Restart" button.

When you try to place a break point does it display an error in the console about all resources being in use or does it do something else?

Maybe try creating a new clean workspace and see if importing and running the example works then? Can you try going to Help -> Check for Updates and see if any updates help (it looks like I'm using a slightly newer version of CCS)

Whitney

Hello Whitney

So I have made all updates Now it is Version: 10.2.0.00009 . And create new workspace and importing examples  "cm_common_config_c28x" and "hello" from SYS/BIOS examples. But nothing changed.

After restart of Cortex_m4 firmware  it show message 

Can't find a source file at "/db/ztree/library/trees/xdctargets/xdctargets-t04/src/ti/targets/arm/rtsarm/boot.asm" 
Locate the file or edit the source lookup path to include its location.

which really  placed in the C:\ti\bios_6_76_01_12\packages\ti\targets\arm\rtsarm

When  I point this directory, I can make step on the assembler instruction but can not set breakpoint 

Always it show message _JobHardwareBreakpoint::ARM_DEBUG_V7M_fpb_add_breakpoint: FPB : All resources are in use.[25062]

 The same message, system shows when I try to put it in some place in main.

I can make step  on the assembler instruction until jump to the reset function, after jump the system show the mentioned above message about resources in use.  Assembler code 

BEQ _no_reset_
MOV r1, pc
ADD r1, r1, #5
MOV lr, r1
BX r0

Reset  function  declared in the same boot.asm file as _xdc_runtime_Startup_reset__I 

_xdc_runtime_Startup_reset__I is defined  as empty in file ($PROJECT_LOCATION)\Debug\configPkg\package/cfg/hello_pem4.c

*
* Startup_reset__I is an internal entry point called by target/platform boot
* code. Boot code is not brought into a partial-link assembly. So, without this
* pragma, whole program optimizers would otherwise optimize-out this function.
*/
xdc_Void xdc_runtime_Startup_reset__I(void) __attribute__ ((used));

/*
* ======== xdc_runtime_Startup_reset__I ========
* This function is called by bootstrap initialization code as early as
* possible in the startup process. This function calls all functions in
* the Reset.fxns array _as well as_ Startup.resetFxn (if it's non-NULL)
*/
xdc_Void xdc_runtime_Startup_reset__I(void)
{
}

/**********************************************************************************************************************************/

So How it runs _c_int00 and how to it rich main() I do not track. 

So where is possible to read about boot sequence until main() ?

And what is wrong?

Best Regards

Andrii