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.

SysBios start up fails due to exception - for TCI6636K2H

Other Parts Discussed in Thread: TCI6636K2H, SYSBIOS, MATHLIB

Hi,

we are trying to bring up our application in TCI6636K2H platform, facing issue in BIOS-start up after the SWI start up the Program counter moves to Interrupt Handler HWI-1 execution due to exception, instead of executing the Task_startup() due to this idle task is not getting executed. Not sure about the exception due to what it is getting executed.

we observed when all the devices initialization(linked LLDs in our project ) is not done BIOS-starting up correctly, when any one of the device example FFT initialization(created FDQ-Q#8930 and High priority accumulation RXQ and RX flow Q#704) is enabled BIOS-start up is failing at this function  ti_sysbios_knl_Swi_startup();.

Void ti_sysbios_BIOS_startFunc__I()
{
xdc_runtime_System_atexit(
(xdc_runtime_System_AtexitHandler)ti_sysbios_BIOS_exitFunc__I);
ti_sysbios_BIOS_registerRTSLock();
ti_sysbios_hal_Hwi_startup();
ti_sysbios_hal_Timer_startup();
ti_sysbios_knl_Swi_startup();
ti_sysbios_knl_Task_startup();
}

Please provide your inputs or guide us to solve this problem     

Thank You
JP

  • Hi JP,

    Do you see this behavior with MCSDK example project? 

    Please post your BIOS related queries on BIOS forum.

    Please refer below announcement.

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/368521.aspx

    Thank you.

  • Hi Rajasekaran , 

    we are not seeing this issue in PDK example FFTC  projects. 

    I could not suspect it is a bios issue, so posted in general. we could not get any points to debug further on this issue from earlier list of posts available on TCI-6636K2H. 

    we are porting TCI-6670 based code on TCI-6636K2H got this issue and stuck here, after launching PC-control is coming to main and the devices are configured successfully (QMSS,FFTC) even though we are seeing this issue. 

    Following drivers' version installed in our PC

    bios_6_35_04_50
    ctoolslib_1_0_2_0
    dsplib_c66x_3_2_0_1
    edma3_lld_02_11_10_09
    imglib_c66x_3_1_1_0
    ipc_3_00_04_29
    mathlib_c66x_3_1_0_0
    mcsdk_bios_3_00_03_15
    mcsdk_linux_3_00_03_15
    ndk_2_22_02_16
    pdk_keystone2_3_00_03_15
    salld_keystone2_02_00_02_00
    syslib_3_00_00_04
    uia_1_03_00_02
    uia_1_03_01_08
    xdais_7_21_01_07
    xdctools_3_25_02_70
    xdctools_3_25_03_72

    CCS-Version-5.5 

    we have taken  necessary changes to migrate it to TCI6636K2H from TCI-6670.

    Please let me know if further inputs needed.  

     

    Thanks & Regards

     JP 

  • Hi All,

    Can I know the difficult level porting from Nyquist(6670) to Hawkins(6636K2H) ,mainly I am looking at what are major changes which we need to take care since 6670 is keystone 1 and 6636K2H is keystone 2,so please suggest how to proceed.

    Regards,

    Umesh

  • Hi,

    Apologize for the delay. Below is the responses from experts,

    1. I am assuming they are running on their h/w and not on the EVM. I would suggest running the program on the EVM first this would eliminate any h/w issues on their h/w.

    2. Another point is that since the examples work, then the LLDs should be compatible with BIOS. I would also ask them to compare the BOIS cfg with the ones in the example.

    Thank you.