• State Resolved
  • Locked Locked
  • Replies 56 replies
  • Subscribers 36 subscribers
  • Views 30020 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.

CCS/TM4C123GE6PM: "Project0" doesn't even work...

Christopher Weber
Genius 4995 points

Part Number: TM4C123GE6PM
Other Parts Discussed in Thread: TM4C123GH6PGE, TM4C123GH6PM, EK-TM4C123GXL, CC2650, EK-TM4C129EXL, ENERGIA, SYSBIOS, EK-TM4C1294XL, TMS320F28027

Tool/software: Code Composer Studio

Yet ANOTHER sample project that is supposed to help you lean, but doesn't work.

Steps to reproduce -  Just follow this:

processors.wiki.ti.com/.../Tiva_TM4C123G_LaunchPad_Blink_the_RGB

Then use this "quick start guide"

www.ti.com/.../spmu352.pdf

I plugged in my new TM4C123G right out of the box. I installed all the drivers, and they appear in the device manager. I installed the TIVA-C packages, and imported the projects.

The light was changing colors with the "factory" load of firmware.  I loaded the Project0. I built it.  I pressed debug.  It downloaded the new firmware.  And did nothing... Sat there no running.

I pressed "Break"  ...  The code is looping on (line 81 in Project0.c ):

while(!SysCtlPeripheralReady(SYSCTL_PERIPH_GPIOG))
{
}

Then I look closely at the project properties.  The device says it's TM4C123GH6PGE.   

I have NO idea why it's looping, I can speculate that the port address, RAM, something...  is different.  The little brochure that came with the launchboard says TM4C123GH6PMI.  So I change it.

Now, it won't build.  I get errors:  FLASH memory range has already been specified tm4c123gh6pm.cmd  because the properties page decided to throw a bunch of new files in there which have conflicting symbols.

I try to put it back by changing the properties and deleting the files it created.  Now it just says the program is not compatible with any of the CPUs in my target configuration.  REALLY??  What is my "target configuration??  Because none of the files I'm digging through seem to give me any hint as to what it thinks it is.  How did it think it knew what the "program" is generated for?  And what is it supposed to match to??

By the way, I've already completely deleted the project and re-imported it several times.  Same results.

I am on CCS 6.2.  I installed C:\ti\TivaWare_C_Series-2.1.4.178

Dealing with these perpetual failures and lack of accurate documentation, and lack or support is really getting old.  Especially since I've been fighting with it since December.

  • 0 in reply to Christopher Weber
    Guru 10570 points
    Just noticed this in your response to my suggestion that you check out Free-RTOS.

    Piccolo? You do realize that's a DSP? That makes at least the third unrelated processor you've mentioned in this thread (BBB, Piccolo and TM4C). Only on one of those could you expect much more than guesses here. They will have quite different environments.

    Robert
  • 0 in reply to Robert Adsett72
    Genius 4995 points
    Robert,
    Yes, the original post was only about the TM4C1294. And the tags reflect that.

    But to re-iterate my point, when you find a place that people answer questions, you ask more, even if they are unrelated. Also, being a newbie, (and I acknowledge myself as such) some of my questions are quite elementary and perhaps can be answered by anyone with some familiarity to the docs and environments, regardless of the specifics of the device.

    As LouEEEE seems to also realize it ( that's one of the ways I interpret his comment) "Wow. OK. It turns out this dark, scary corner of the TI E2E Community is exactly where I should be hangin' out..."

    The problem was answered on 19 Apr. Somehow, the thread was kicked back to life 41 days later. And has degenerated into discussions about the forums themselves, amount of help or sometimes lack thereof, and now asking other devices on this thread. From my point of view, my question is solved, marked as such, and should end there. But if people want to talk about the support or documentation issues, I sure have some comments/complaints there too :-) There doesn't seem to be a forum to address the forums. LOL!

    And my mention of the Piccolo was to comment that I didn't get answers, not specifically asking this thread to support an unrelated device.

    But I see you took the time to read back through the thread, and I appreciate that.
    (By the way, is TM4C really an "unrelated" processor in this thread? That was how I started the thread in the first place. )

    -Christopher
  • 0 in reply to Christopher Weber
    Guru 10570 points
    Christopher, I meant the three processors are unrelated to each other.

    Robert

    BTW you can ask questions in another thread on the same forum.
  • 0 in reply to Robert Adsett72
    Genius 4995 points
    Hehe...
    I wouldn't create a new thread in this TM4C forum to ask my piccolo questions, or my BBB questions. Then I would be scolded! LOL!

    The threads for those other devices are still out there. If (and when) I move back to the BBB, I will try more posting in that one. Multicore will be interesting as well, not just multi threads from Linux or Windows. For now, I've got things moving at a good clip with the TM4C, and it gives me a good ARM intro.

    By the way, the piccolo was just an arbitrary board chosen to attempt to learn the RTOS and CCS, based on those old Eric Wilbur videos. The choice was really rather random. The chip itself was just a means to that end. The ultimate goal is ARM, and since the Valvano books are so useful, the TM4C was straight out of his educational material. So I bought both the 1294 and the 123 boards his materiel covers.

    -CSW
  • 0 in reply to Christopher Weber
    Guru 10570 points
    It strikes me as a rather bad role of the dice if it lead you to using an unfamiliar DSP as a platform to learn an RTOS on.

    Robert
  • 0 in reply to Robert Adsett72
    Genius 4995 points

    Robert Adsett72 said:
    It strikes me as a rather bad role of the dice if it lead you to using an unfamiliar DSP as a platform to learn an RTOS on.

    Robert

    Believe me when I say it was not for a lack of trying to find *any* recommended starting point.  And every device was going to me "unfamiliar" since I had never worked closely with TI MCUs until now.

    Eric Wilbur's online videos, which was where I finally started, gave me a 7 sided die...  And the C2000 device was the second from the bottom.  The bottom was MSP430 which I didn't want to use (not ARM, only 16 bit, and only 25 Mhz).

    The C2000, also known as the C28x, but uses a TMS320F28027, (I've never been able to make sense of that consistency), is billed on the web site as "is an inexpensive, modular, and fun evaluation platform, enabling you to dive into real-time, closed-loop control development"

    Sure sounded like as good a place to start as any. A task is just a task, whether it's to flash an LED, PWM an actuator, or to correlate a magnetic waveform.  (Little did I know the bootstrapping was such a nightmare to find any documentation)

    Someone enthusiastic about learning shouldn't be left to roll dice anyway. 

    But, as I said, I'm past the startup issues now, and satisfied with the progress.

    -CSW