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.

CCS V5=> Trouble Writing Memory Block

Hi,

I am using CCS V5 with à C6424 DSP and a XDS510 USB Jtag.

In Debug mode, my program is correctly loaded, but  after a while It stops and I get this message:

C64XP_0: Trouble Writing Memory Block at 0x83d48600 on Page 0 of Length 0xc: Error 0x00000002/-1177 Error during: Memory, The HW memory system has generated an fault condition for the IM memory request specified. This could be caused by incorrect access size or mis-aligned memory address.

It seems to be linked to a problem that  I can see in release mode, that implies an unexpected stop in one of my task after a non constant time.

My memory map seems OK, and the size of stack/heap also.

 

Any idea of a possible solution to my problem?

 

Best regards

  • Hello,

    Simon 14448 said:

    after a while It stops and I get this message:

    C64XP_0: Trouble Writing Memory Block at 0x83d48600 on Page 0 of Length 0xc: Error 0x00000002/-1177 Error during: Memory, The HW memory system has generated an fault condition for the IM memory request specified. This could be caused by incorrect access size or mis-aligned memory address.

    Note that it is very difficult to provide any suggestions for this kind of issue with more details. Would it be possible to provide a reproducible test case? And are you using the 6424 EVM or is it a custom board?

    Simon 14448 said:
    It seems to be linked to a problem that  I can see in release mode, that implies an unexpected stop in one of my task after a non constant time.

    Do you mean that it is the release configuration of your project that exhibits this error while the debug configuration does not?

    Thanks

    ki

  • Hi Ki,

     

    I am not using he 6424 EVM, I have a custom board.

    I am using a 512 Mb DDR2, so it seems that the address 0x83d48600 should be reachable.

    Do you mean that it is the release configuration of your project that exhibits this error while the debug configuration does not?

    Actually, I see an error in realase configuration (one of my tasks stops unexpectedly after a while) but I am not sure that this error is related to the one I see in Debug configuration (the "trouble writing memory" one)

    Best Regards,

     

  • Simon 14448 said:
    I am using a 512 Mb DDR2, so it seems that the address 0x83d48600 should be reachable.

    Is the program also being loaded to DDR2?

  • Hi Ki,

     

    Yes my program is also loaded to DDR2.

    (In my link.cmd file, I put   .text > DDR2  )

  • Ok, it seems like the debugger can access DDR2 fine. It looks like something specific to your application. I'm not sure what it can be, I'll try to get some help from other experts.

  • Hi Ki,

     

    My problem seems related to my task which is doing the acquisition on the ADC. If I remove this task I don't have the problem anymore? But I really don't know what can be the cause..

     

    Regards,

  • Hi Ki,

     

    An other information:  when I face my problem, I see that the McBSP SPCR register RFULL is set to 1.

    As I understand, this is an overrun error, but how can I undergo this problem?

     Any suggestion?

    Regards,

  • Simon 14448 said:

    An other information:  when I face my problem, I see that the McBSP SPCR register RFULL is set to 1.

    As I understand, this is an overrun error, but how can I undergo this problem?

    Sorry, I am not much help with this question. I would post your question in the C6000 forums where the expertes there can help you best.

    Thanks

    ki