• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 312 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

C6474 Trouble Writing Memory Block

Oleg Bugrov
Prodigy 20 points
Part Number: TMS320C6474

Tool/software: Code Composer Studio

Hello! I have a big project for triple-core processor C6474. When I tried to debug project on one of our processors, we had a problem: "C64XP_2: Trouble Writing Memory Block at 0x1287ff10 on Page 0 of Length 0x1f50: (error -1190@ 0x12880000) Unable to access device memory.... After that I created simple "Hello word" project, ran it and explored a "Memory Browser" tab. I saw this picture:

What could you advice me to do with that?

 

  • 0
    TI__Guru**** 161600 points
    Hi Oleg,

    I've notified the sw team. They will post their feedback directly here.

    Best Regards,
    Yordan
  • 0
    TI__Guru** 114410 points

    Oleg,

    It appears that the L2 memory for the part is divided into two 512 KB regions and it appears that emulation drivers are able to read and write from the first 512 KB that end at 12880000 but the upper 512 KB there is some memory read write issue.

    Can you type in 0x00880000 and see if the memory is accessible from DSP internal address? If is accessible from that address then I would think that this is an emulation driver issue? Could you indicate what emulator are you using and if the same issue doesn`t exist for core 1 and core 0? Are there any memory protection restrictions on that memory ?

    Regards,
    Rahul

  • 0 in reply to Rahul Prabhu
    Prodigy 20 points
    Thank you for your answer!
    1) Usually my project works on other processors c6474, that I’ve got. For example, hello-world project with the same configuration works well on them, there is no trouble with memory
    2) My emulator is SAU510-USB IsoPlus v2
    3) There is no protection restrictions on the memory
    4) When I record the program to the Core 2, I have “X” in memory browser after 0x12880000 and after 0x00880000.
    5) When I start same program on the Core 1 and Core 0, I have “0” after 0x12880000 (and I read random numbers from this address) and random numbers after 0x00880000.