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.

EasyMX Pro - TI-RTOS - LaunchPad and UARTS

Other Parts Discussed in Thread: TM4C129XNCZAD, MAX232

Hi All:

I've written some programs using UART, I2C, ADC, etc features for both of the Tiva Launch Pad boards with no issues.

Due to some appealing features, I decided to take a look at the Easy MX Pro v7 board from MikroElectronika using the TM4C129XNCZAD chip.

I am using Code Composer 6.1, TI-RTOS with UART drivers with the Easy MX Pro hardware.

I can Load and Debug my program from the board; but, I can not get the UARTs to do anything.  I've tried all 8 sets of UART PINS.  Nothing.

I followed all of the recommendation on the Wiki.  The UART example is 'dated'.

I believe the Tiva Launchpads use a 25Mhz Oscillator along with the Mikro board.

Does anyone have any experience with this board?   Did you get these working together?  Is this a lost cause?

Thanks

Rick

  • Rick Faszold said:

    I am using Code Composer 6.1, TI-RTOS with UART drivers with the Easy MX Pro hardware.

    I can Load and Debug my program from the board; but, I can not get the UARTs to do anything.  I've tried all 8 sets of UART PINS.  Nothing.

    That you can download suggests that the micro is working.

    Simplify, remove the RTOS and strip down to a simple blinky program or a program that simply writes a stream of characters out a serial line (no reading).  Remember there are a few unflagged library incompatibilities between the 123 and 129 series (at least the clock routines). Check the eval board for H/W conflicts with what you are trying to do.  Once you've simplified, then you have something perhaps small enough to be reviewed.

    Robert

  • Rick Faszold said:
    I can not get the UARTs to do anything.  I've tried all 8 sets of UART PINS.  Nothing.

    While your diagnostic report trumps, "Does not work!" it is not of great help.

    Have you scoped the various UART Outputs - while sending a "looping" program?    In the past - both Robert & I have suggested the use of 0xAA or 0x55 as either emits an "alternating bit pattern" - recognizable by even lesser scopes.   Without a scope - yet w/baud rate slowed - even an Led may serve to monitor UART Output.

    Always unstated - that to which you are connecting!   MCU outputs CMOS levels - not USB nor RS232.   Thus you require line driver and/or USB>UART converter to connect to a PC.   (again - trusty diagnostic crue here - "in the dark")   (Not an unfamiliar place btw...)

    Completely agree w/Robert that you've "started" in near total violation of KISS.   Kill that RTOS - get one UART to work - only later add complexity.

  • Robert & cb1-:

    if (RTOS == Dead) Program = Works; // OK, let's face it, this completely violated KISS. Of course, hindsight is 20/20

    I was working with a MAX232 on the Tiva and the MX Pro. Regarding the scope, agreed. I need to break down and get one.

    I've been using TI-RTOS with various Drivers. I do not know if the Drivers can be used outside of RTOS, so I'll look that up.

    Thanks for your help!

    Rick
  • Rick Faszold said:
    completely violated KISS

    And (yet another) WIN for humble (but Oh so effective) KISS!    Long live KISS.

    Perhaps if KISS received (almost) as much promotion as, "Caution when selecting PF0/PD7" many more would note - & use KISS.     Or NOT!    (what was I thinking?)