• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 97 subscribers
  • Views 422 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Problems about reading data from DSP6678

aichen wang
Intellectual 380 points

Hi, everyone!

Recently I am working on DSP 6678 booting from PCIe. The procedure which reads data from DSP is ok in EVM, but it result in the host rebooting when working on DSP 6678. Can anybody give me some useful advice about this situation?

 

Thanks

Wang aichen

  • 0
    TI__Guru* 95265 points

    Wang aichen,

    Please provide more details about the issue: what is the PCIE RC? The PCIE EP is a 6678 EVM or customized board? What is the boot mode for 6678? What is the SW running on both sides? Can RC writes successfully to EP? When RC reads from EP, if RC is rebooting, how do you know the read is successful?

    Regards, Eric

     

  • 0 in reply to lding
    Intellectual 380 points

    Eric,

    I am sorry that I did not provide enough information.

    1.The PC is regarded as the PCIE RC, and the PCIE EP is a customized board.(The customized board is designed similar to 6678 EVM, and the procedure works well when 6678EVM works as PCIE EP).

    2.The boot mode is PCIE.

       SW3: (off, on, on, off)

       SW4: (on, on, on, on)

       SW5: (on, on, on, off)

       SW6: (off, on, on, on)

       SW9: (off, on,on,on)

    3.RC can write successfully to EP.

    4.The read fails, because there is a file wirte in the procedure, and the file is null. 

  • 0 in reply to aichen wang
    TI__Guru* 95265 points

    "and the procedure works well when 6678EVM works as PCIE EP" =========> do you mean the read also works in this case?

    What is the SW running on PCIE RC side, this is your own driver code? The RC is a Linux or Windows PC? Instead of writing what you read into a file, can you see what you read in your driver code?

    Regards, Eric

  • 0 in reply to lding
    Intellectual 380 points

    Eric,

    1.Everything is ok when 6678EVM work as EP.

    2.The SW is driver code as well as a simple test. The RC is a Windows PC.

    3.It still results in rebooting when there is no writing.The fill is null.

    Can you provide me some possible reasons or tests?

    Thanks!

    Wang aichen

  • 0 in reply to aichen wang
    TI__Guru* 95265 points

    Just plug-in your customized 6678 card into PC without running the driver code, will PC reboot as well? If yes, this is HW compatibility issue.

    Regards, Eric 

  • 0 in reply to lding
    Intellectual 380 points

    Eric,

    I am sorry that maybe I did not make myself understood.

    The driver code is ok, and the PC dose not reboot. But when running the simple test which reads data from DSP, the PC reboots.

    Have you ever met problems like this? I am expecting you could give me some advice.

    Thanks.

    Wang aichen

  • 0 in reply to aichen wang
    TI__Guru* 95265 points

    Wang aichen,

    Thanks for the additional explanation, now I understood the problem. Is possible when you read the data from EP, the data landed in some memory region conflict with your Windows PC? We have some Linux PCIE driver code (not Windows) and didn't have such problem.

    Regards, Eric

  • 0 in reply to lding
    Intellectual 380 points

    Eric

    Would you like to share your driver code , or just the read part? 

    Thanks for your patience and look forward to hearing from you.

    Regards

    Wang aichen

  • 0 in reply to aichen wang
    TI__Guru* 95265 points

    The Linux driver code is under ti\mcsdk_2_01_02_06\tools\boot_loader\examples\pcie\linux_host_loader\pciedemo.c, there are functions like: uint32_t readDSPMemory(uint32_t coreNum, uint32_t DSPMemAddr, uint32_t *buffer, uint32_t length)

    Regards, Eric