• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 314 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.

MED STK debugging, Interrupt No. 13 dropped

Richard Fix
Prodigy 150 points

BIOS_5_41_10_36, C6455, CCS_4_2_3_00004, MedicalSoftwareTookkitVer2_0_0_usound, TI supplied test.c, debugging using bmode_1 vector.

When I attempt to debug and run using the above test scenario, I get the following message repeatedly:

"TMS320C64X+: Warning: CPU:Interrupt No. 13 dropped, and earlier interrupt  is pending to be taken".

While I suspect I have my memory definitions incorrectly set, I have no method in figuring out what exactly I need to do.  Does anyone have an idea what I need to do to correct this? 

 

 

  • 0
    TI__Expert 4920 points

    Hi Richard,

    Thanks for your interest in STK-MED. STK-MED v2.0 was tested and verified using CCSv3.3 and BIOS 5.33.03. Since you are trying this with CCSv4.2 and BIOS 5.41.10.36, it could be possible that the warnings you are seeing are related to the BIOS version difference. However, I'll let one of the BIOS experts comment here.

    In the meantime, here's an e2e post that though is not directly related to what you're seeing, might help: http://e2e.ti.com/support/embedded/f/355/p/61893/222297.aspx. You might also know, that earlier this week we released a new STK-MED v3.0 that is for both C64x+ and C66x based devices, and is based on BIOS 6.3x and CCSv5. The unit test benches for this v3.0 have been verified on the 6678 and 6472 EVMs, but it should be possible to port to 6455 with some memory and edma configuration changes in the test project, in case that is the path you choose to take. 

    Regards,
    Uday

     

  • 0 in reply to Uday
    Prodigy 150 points

    Ok, I didn't want to spend time with the older revision sw, so per your recommendation I embarked on trying to get the STK-MED v3.0 release working.  I have followed the readme.txt file included with stk-med-03.00.00.  I choose to make the ti install dir "C:\Program Files\Texas Instruments" instead of "C:\ti", but followed explicitly the instructions.  I can't get past instruction 4.b.c6472 build library.  One error exists, "This project does not contain a buildable RTSC configuration ...", and two warnings about "Invalid project path".  One of the two warnings seems to have an invalid include path (missing miAlgos in the scu_ires/src path), and the other warning claims duplicate path entries found.

    At this point I need assistance in going forward.

  • 0 in reply to Richard Fix
    TI__Mastermind 20805 points

    Richard --

    I don't know anything about STK-MED, but I can comment on this:

    When I attempt to debug and run using the above test scenario, I get the following message repeatedly:

    "TMS320C64X+: Warning: CPU:Interrupt No. 13 dropped, and earlier interrupt  is pending to be taken".

     

    This is related to some validation code in the simulator that checks to see if the IFR register gets set again when the IFR register was already set.   Problem is that on the C6x, there's an interrupt mux and one of the interrupts, probably the timer, is connected to interrupt 13 by default.   Even though interrupt 13 is not enabled in IER, the bit is still getting set in IFR.   The workaround is to use Hwi_eventMap() (or HWI_eventmap() in BIOS 5.x) to make interrupt 13 to one of the peripherals that is not active.   I think there's also a way to disable this validation in the simulator .xml file.

    -Karl-

     

  • 0 in reply to Richard Fix
    TI__Expert 4920 points

    Hi Richard,

    Apologize for the delay in getting back to you; was out of office last week.

    Are you using the same version of CCS (5.0.3) as listed in the readme or is it a different version? I'm asking this since I spotted an e2e post that talked about a user facing a similar issue when importing 5.0.x projects into CCS 5.1.
    Here's the e2e post I'm referring to: 
    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/134020/486073.aspx?PageIndex=2
    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/134020/486073.aspx# 

    Also please ensure that the software components are the same as listed in the readme.

    Once you've verified the above, please import the projects that you are seeing an error, do a clean project followed by build project and then copy-paste the build log that you see in the CCS console. Along with that please also attach a build log for a stk-med project that is building successfully in your environment. These build logs might give us a better idea of what could be going on. I've attached the build logs for scu_ires library on C64P, as a reference:
    1. 7624.buildlog_scu_ires_c64P_lib_Debug.txt
    2. 0066.buildlog_scu_ires_c64P_lib_Release.txt 

    Thanks,
    Uday