Quantcast
Channel: Embedded Software (Read Only)
Viewing all articles
Browse latest Browse all 25965

Forum Post: RE: Difficulty with TI-RTOS Lab 5 for OMAPL138 LCDK

$
0
0

Chris,

Thanks for the attachments. I was able to import your project into my CCSv6.0, build (zero errors) and run (it blinks). I am using the C6748 LCDK. 

I am at a loss of what to suggest here. First, your code is "perfect". The quotes are meant to a) give you a warm fuzzy that you did everything correctly in the code and w/the BIOS .cfg file - so you succeeded in the lab; b) to give you a cold fuzzy that something is still wrong.  ;-)

It is hard to debug this from afar. The only difference between our boards is the ARM9 vs. no ARM9. The other differences are:

- you have System Analyzer checked (enabled) in your app.cfg file (UNCHECK that) - it is already used as part of the TI-RTOS SDK. I had mistakenly checked that in the solution (which I am now fixing FYI in all projects).

- you are using XDS100v2 and I am using XDS510USB - shouldn't be a problem

- I am assuming you are connecting to the ARM first, then 6748 CPU, then loading on the 6748 CPU. I assume yes because the timer (lab 5b) works fine for you

I am straining my brain for some "what if" scenarios that may lead to the answer. As an instructor and BIOS user, this BUGS me.  ;-)  So here are a few questions/ideas:

1. Did lab 2 and 4 work ok for you? If so, this takes the entire "environment" out of the picture. It means that you and I are the same in terms of building/running in our own environments using different target config files, different processors, but if lab4 works for you, but not lab5, this narrows the field. If lab4 does NOT work for you, well, then this opens the field a bit regarding the possible error.

2. Uncheck the system analyzer (right-click -> Properties -> RTSC tab -> System Analyzer (UIA)). I suspect this has NOTHING to do with the problem. Just trying to get closer to "equal". Your project worked fine in my environment even with it checked, so I suspect this will do nothing to solve the problem. Can you tell I grasping for straws here?  ;-)

3. The fact that the timer lab works fine, but the first part of Lab5 does NOT bothers me. The timer module in BIOS replaces the code used in hardware_init() and allows BIOS to set up the timer for you. Assuming our environments are identical (and lab 2 and lab 4 worked perfectly for you) - and the fact that your project built and ran perfectly on the C6748 LCDK that I just tested, points to a mystery. Can I say that?  I just did. I have no idea what the problem could be.

4. Wait - I just realized I HAVE an OMAP-L138 LCDK...let me run it on that... It didn't work. So, I have been able to verify your problem on the same board. Initially, I was using the OMAP-L138 board to do my initial development work before I chose to use the C6748 LCDK instead. SO, there is something we are NOT doing to get this to work. Duh. I have emailed a few experts to help out.

5. FYI - the GIE bit is set properly by BIOS. IER (bit 5) is also enabled via BIOS properly. However, IFR bit (5) is NOT set at all which means, as you said, the timer is not firing - otherwise it would blink.

I will get back to you when I get this lab to work on my OMAP-L138 LCDK via help from others. Still a mystery - but I hope to figure it out soon...sorry for the delay...but we will BOTH learn something in the process...


Viewing all articles
Browse latest Browse all 25965

Trending Articles