• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 354 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.

Suddenly after multiple repeated debug sessions, I get memory errors when starting up the board.

Philip Schröder
Prodigy 230 points
Other Parts Discussed in Thread: SYSCONFIG, AM2434

Hello,
I am programming on an AM243x Sitara Board using Code Composer Studio 11.2 and a project utilizing the TI- MCU+ SDK.
My code is C++.
After trying to find out why after set interrupt routing on triggering of an interrupt the ISR would not be entered,
I ran a debugging session, which produced the following error:



The full error line reads:

"MAIN_Cortex_R5_0_0: Trouble Writing Memory Block at 0x2400010 on Page 0 of Length 0x4: (Error -1205 @ 0x2400014) Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.7.0.00213) "

For the debugging I attach our board to an XDS110 JTAG Debug Probe which I plug into my computer over USB.

From the CCS Edit Perspective I launch the following Debug Configuration:



where the TargetConfig is set as follows:



<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
    
    <configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cortexR.xml" id="drivers" xml="tixds510cortexR.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cortexM.xml" id="drivers" xml="tixds510cortexM.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510pru.xml" id="drivers" xml="tixds510pru.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510csstm.xml" id="drivers" xml="tixds510csstm.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510ctset2.xml" id="drivers" xml="tixds510ctset2.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510etbcs.xml" id="drivers" xml="tixds510etbcs.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="AM243x_GP_EVM_0" href="boards/AM243x_GP_EVM.xml" id="AM243x_GP_EVM_0" xml="AM243x_GP_EVM.xml" xmlpath="boards"/>
            </platform>
        </connection>
    </configuration>
</configurations>


Using the launch script, I start by bringing the board into NoBoot mode.
Then there is a check for the existence of sysfw.bin and sciclient_set_boardcfg.release.out, which succeeds.
Afterwards sysfw.bin is loaded and DMSC starts up on the M§.

But then the R5 tries to connect, which does not seem to work.
And I get said memory error right after that.

Is there anything you can maybe recognize from this error?
Thank you for your time and trouble.


Best regards

Philip.


  • 0
    TI__Guru 54875 points

    Hi Philip,

    As we discussed in the meeting, can you send me the launch.js you used for initializing your board.

    Also the 0x2400000 is the TIMER0_CFG according to the Main domain Memory Map in TRM, but the 0x2400014 is invalid MMR address though.

    Best regards,

    Ming 

  • 0 in reply to Ming Wei
    Prodigy 230 points

    Hello Ming,

    sorry that I didn't do that already.
    We had an infrastructure change today and on friday I tried to fix all my git related stuff before the move.
    I am still working on the manual you requested, will finish that tomorrow.

    But also in the end of last week I fixed the error from this post.
    It seems that my CCXML file was corrupt somehow.

    I am still not sure in which way, but I will try to find it out and put a comment here as a final answer.

    Best regards

    Philip.

  • +1 in reply to Philip Schröder
    Prodigy 230 points

    Hello Ming,
    so the error is definitive in the "_0" endings:


    It seems that at one point, as in my syscfg file that I use for our board it says "package =ALV",



    also to be able to open my syscfg file in the standalone SysConfig and not get the no-package error, I needed to choose the following context:



    I tried out to set in the CCXML the board to AM2434_ALV instead of AM243x_GP_EVM


    which as a result adds those "_0" endings.

    When that didn't seem to work, I set the board back to AM243x_GP_EVM, but the "_0"-endings stayed in the CCXML file.
    I don't know why those are added in the first place but maybe you have an idea.

    As this answer solves my problem, I will mark this as resolved but would be happy in case you have an idea why those endings are added, if you could elaborate on that.

    Thank you for your time and trouble.


    Best regards

    Philip.

  • 0 in reply to Philip Schröder
    TI__Mastermind 27743 points

    Hi Philip,

    We confirmed this as issue/bug in our ccxml. Below is JIRA ID for tracking. I will let you know schedule once the fix version is assigned to this bug.

    SITARAAPPS-2257 - AM243x_ALV.ccxml file has invalid "_0"-endings

    Regards,

    Prasad

  • 0 in reply to Prasad Jondhale
    Prodigy 230 points

    Thank you for your answer.


    Best regards

    Philip.