• State Resolved
  • Locked Locked
  • Replies 17 replies
  • Subscribers 64 subscribers
  • Views 4971 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.

UCD3138 Training Lab error in execution

Rose Merlyn Prakash
Prodigy 100 points
Other Parts Discussed in Thread: UCD3138064, UCD3138OL64EVM-031, UCD3138

Hi,

I am using CCS 6.1.2 and Im using evaluation board UCD3138064EVM.


Build is successful. I've changed configuration to UCD3138064.Also, the .xo file has been downloaded successfully.


But,While trying Labs, I am not able to get device ID + I am not able to get any updates in memory debugger tool + No outputs on pins; in Labs 1-4. It appears the code is not actually executing.

It appears to be working from Lab5. What could be problem with first four labs?

Any help is appreciated

Thanks

  • 0
    TI__Expert 4970 points

    Hi Rose,

    Is this with the latest labs from here?

    Regards,

    Brandon Vonk

  • 0 in reply to Brandon Vonk
    Prodigy 100 points

    Sorry, I am not sure about the source..It was set-up by a Senior..I guess its from Training Labs 1.0

  • 0 in reply to Rose Merlyn Prakash
    TI__Expert 4970 points

    If that was the case, there might have been an error introduced if he converted it from CCSv3 to CCSv6. Try using the source I mentioned, they are for CCSv6.

    Also, see if you can get compiler version 5.2.4. You can do this through the Help --> install new software option in CCS. Work with: --All Available Sites--, and then make sure you UNCHECK the Show only the latest versions of available software checkbox option at the bottom of the window. scroll down and expand TI Compiler Updates, and then select Arm Compiler Tools version 5.2.4. We haven't tested if there are issues with newer versions of the compiler yet.

    Hope this helps!

    Regards,

    Brandon Vonk

  • 0 in reply to Brandon Vonk
    Prodigy 100 points
    Hi Brendon,

    I tried the link you provided. But, I am not able to access it.It seems the folder form that link has been removed!!

    Also, I will try with compiler version 5.2.4 today.

    Thanks
  • 0 in reply to Rose Merlyn Prakash
    TI__Expert 4970 points
    Hi Rose,

    Thanks for bringing the problem with the box link to my attention. I will let you know when the link is fixed. Also note that the post was modified and now contains a link to the powerpoint training presentations.

    Regards,

    Brandon Vonk
  • 0 in reply to Brandon Vonk
    Prodigy 100 points
    Thanks for the powerpoint presentations Brendon.
    Please inform me when u fix the link so that I can try with that. Meanwhile, I will try with the compiler 5.2.4
    Thanks for the help
  • 0 in reply to Rose Merlyn Prakash
    TI__Expert 4970 points
    Rose,

    The link should now be updated and fixed. Please confirm. Thanks!

    Regards,

    Brandon Vonk
  • 0 in reply to Brandon Vonk
    Prodigy 100 points
    Brendon,
    I guess the training-labs I had was the same. Because I re-installed and got the same results with this. Labs 1-4 seem to be not working. Lab5 is fine.
  • 0 in reply to Rose Merlyn Prakash
    TI__Expert 4970 points

    Rose,

    Did you see in the main.c source code that you need to tie FAULT 3 to GND? If you don't do this, this pin may be floating, and it's possible it could be read as a 1, in which case the device would be told to stop program execution (Program Mode) and move to ROM mode.

    Could this be the problem you are having?

    Regards,

    Brandon Vonk

  • 0 in reply to Brandon Vonk
    Prodigy 100 points

    Yes, I had ensured that. Moreover, this part is the same in Lab5 which works...

  • 0 in reply to Rose Merlyn Prakash
    TI__Expert 4970 points

    Rose,

    Well then this is very interesting indeed. After you download the compiled FW .x0 file to the device and the device GUI commands the device to begin execution immediately (default), then close the download window.  What happens when you click the following buttons in the main device GUI window?

    • scan for device in ROM mode
    • scan for device in Program Mode

    Please provide screenshots, of the Device GUI output log.

    -Brandon Vonk

    LoadRegulation_Put-Anything-Here-But-An-Underscore_Temperature-25C_Vin-380VDC_Iout-13.8A_blah250A_blah-25.0B_blah--250C_250D_-250E_--250FGH_blah---250I_---250J_bl4ah250K.png

  • 0 in reply to Brandon Vonk
    Prodigy 100 points

    Brendan, Please find the attached screenshots.

    First one was in ROM mode and second one in Program mode.

    Appreciate your help

  • 0 in reply to Rose Merlyn Prakash
    TI__Expert 4970 points

    Rose,

    I just ran Lab_1 on my side to see if it works. Everything ran fine, and I received the following:

    There must be something different between yours and my setup.

    A couple things:

    1. Just to clarify, you are running this on a UCD3138OL64EVM-031 open loop board EVM right?
    2. Can you verify through the memory debugger while you are in ROM mode that you are indeed changing the value of the FLT3_IN bit between 1 and 0 when you tie it to +3_3V and DGND respectively? To do this, open the memory debugger in the Fusion Device GUI (password is forestln). Expand the + signs to navigate to GioRegs->FAULTIN->bit->Bit Fields->FLT3_IN. Once you select the FLT3_IN row, you can hit the blue refresh button that shows up. Tie the pin to 3.3V, and refresh to make sure the bit shows a 1. Then tie it to DGND and make sure the bit shows a 0.
    3. In CCS, in the project explorer, what is the active build configuration after you build the project for UCD3138064?
    4. Are there any warnings after you compile the FW other than the one that says the project is in manual Parser Preprocessing mode?

    Please let me know. Screenshots always help. Thanks!

    Regards,

    Brandon Vonk

  • 0 in reply to Brandon Vonk
    Prodigy 100 points

    Hi Brandon,

    You were absolutely right about the FAULT3 pin..Actually, I was assuming the wrong pin for FAULT3. The actual one was infact floating and might have been interpreted as 1.

    And the reason why it worked from Lab5 was that the condition is like below in all labs from Lab5 which I didnt notice.

    if(GioRegs.FAULTIN.bit.FLT3_IN == 0)
    {
    clear_integrity_word();
    }

    Anyways..I am glad it works now :-)

    Thanks a lot for your time 

    Really appreciate your help

    -Rose

  • 0 in reply to Rose Merlyn Prakash
    TI__Expert 4970 points
    Rose,

    It actually happened to me when I re-ran lab_01. :-)
    The open loop board doesn't have a pull-up/pull-down circuit for it so you need to actually use a jumper wire to ground it.

    Glad to help. Thanks!

    Regards,

    Brandon Vonk
  • 0 in reply to Brandon Vonk
    Prodigy 80 points
    Dear Brandon,
    May I ask you a question, I have trouble generating .xo file

    Dear all,

    I have successfully installed UCD3138 training lab and imported it in CCS 6.1.3.

    I set UCD3138064 as active device (followed procedure from video tutorial)

    then I built the project and following comments appeared in console:

    'Tektronix Extended format'
    ("C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/bin/armhex.exe" -x "Lab_2_UCD3138064.out" -o "Lab_2_UCD3138064.x0" -memwidth 8)
    makefile:174: recipe for target 'post-build' failed
    process_begin: CreateProcess(NULL, (C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/bin/armhex.exe -x Lab_2_UCD3138064.out -o Lab_2_UCD3138064.x0 -memwidth 8), ...) failed.
    make (e=2): The system cannot find the file specified.

    gmake[1]: [post-build] Error 2 (ignored)

    Then I checked in Lab02/UCD3138064 and there's no new .xo file generated. When finish building the project, there should be an .xo file replace and cover the existing .xo file right? Please help me....I'm waiting online. Thank you!
  • 0 in reply to Brandon Vonk
    Intellectual 655 points
    Hello Brandon,
    The link is not working anymore.