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.

AM2434: Updated from CCS12 to CCS20 PCIE can't read

Part Number: AM2434
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi Ti Expert,

   I am debugging a very simple PCIE project. The following are the code.

   These code can run well on CCS Version: 12.4. both reading and writing.

    When using CCS Version: 20.2.0, the writing is all right, but crash occurs when I read PCIE.

    I also post the sysconfig of the two test, they are almost the same.

    please help me with this,

int main(void)
{
uint32_t * test = (uint32_t *)(0x68000000U + 0x01000000U);
uint32_t read_test = 0;
System_init();
Board_init();


Drivers_open();
HAL_PCIE_fpgaInit(gPcieHandle[CONFIG_PCIE0]);

*(test+0) = 0x1f;  // writing 
*(test+0) = 0x0;    // writing 
*(test+0) = 0x1;    // writing 

read_test = *(test+0x140/4);   //reading 

Board_deinit();
System_deinit();

return 0;

}

This is my init function for fpga-PCIE.

int32_t HAL_PCIE_fpgaInit(Pcie_Handle handle)
{
int32_t status = SystemP_SUCCESS;
pcieHandle = handle; //gPcieHandle[CONFIG_PCIE0]

//Drivers_open(); // if this driver is the only one in this project, need this line
//Board_driversOpen(); // if this driver is the only one in this project, need this line

status = Pcie_getVendorId(pcieHandle, PCIE_LOCATION_REMOTE, &vndId, &devId);

if (SystemP_SUCCESS != status)
{
return status;
}

status = pcieFpgaSetStatusCmd(pcieHandle);

if (SystemP_SUCCESS != status)
{
return status;
}

status = pcieFpgaEpBar1Cfg(pcieHandle);

if (SystemP_SUCCESS != status)
{
return status;
}

status = pcieWriteDevStatCtrlReg(pcieHandle);

if (SystemP_SUCCESS != status)
{
return status;
}
pcie_initialized_indicating = 1;
return status;

}

Thanks 

Chunyang 

  • Hi Ti Expert


    I want to add something from my last debug.
    When Add DDR in the sysconfig in the above CCS 20.2.0 project. The reading became successful.

    In my other projects reading PCIE also cannot be sucessful, as the demo it always stuck in here


    LDR pc, data_abort_addr // Abort (data)

    For your information.

    BR,
    Chunyang

  • Hello Chunyang,

    but crash occurs when I read PCIE.

    I assume you are referring to the target application crashing and not CCS itself.

    I want to add something from my last debug.
    When Add DDR in the sysconfig in the above CCS 20.2.0 project. The reading became successful.

    In my other projects reading PCIE also cannot be sucessful, as the demo it always stuck in here


    LDR pc, data_abort_addr // Abort (data)

    Thank you for the added information. This is something that the device/SDK experts will need to investigate. I will bring this thread to their attention.

    Thanks

    ki

  • Thanks Ki,

        The PCIE communication is a essential performance of our design.

         The Am243x is RC while FPGA is EP in our design. This could work all right with CCS Version: 12.4.

         But when we updated to CCS Version: 20.2.0, even the simplest project could not work as the first post shows.

         Now, it is blocking our development' progress. If there is some update from you, please let me know!

     

    BR,

    Chunyang

  • Hi Chunyang,

    Have you also updated the version of SDK with newer CCS?

    Which version of compiler are you using?

    Regards,

    Tushar

  • You can check the compiler and SDK version in CCS project properties.

    For Compiler version:

    Open Project Properties. Navigate to General.

    For SDK version:

    Open Project Properties -> General -> Dependencies.

  • Hi Tushar,

        Sorry for the missing of SDK version.

        My new CCS version is CCS 20.2.0, and SDK is ind_comms_sdk_am243x_11_00_00_08, and compiler version is: TI Clang v4.0.0.LTS

        And I Checked that even in CCS 12.8.1(SDK ind_11) there is also this issue.


        My old version of CCS 12.4 and SDK 9.2. There is no this issue.

        For your information.

    BR,

    Chunyang 

  • Hi Chunyang,

    Thanks for providing the above details. For me it doesn't look like a CCS issue as it is failing in CCS v12.8 also.

    Also there are so many changes to SDK also when migrating from SDK v9.2 to v11.0. It can be issue with SDK upgradation also.

    Can you please try a default example from SDK v11.0 and do changes on top of it?

    Regards,

    Tushar