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.

RTOS/TM4C1294NCPDT: Upgrading from 2.1.2.111 to 2.1.4.178 kills the USB

Part Number: TM4C1294NCPDT

Tool/software: TI-RTOS

Hello. 

this thread is related to this one, which was not solved.

I can run examples using the 2.1.4.178 and they run correctly. but I have a running code to maintain and develop. in this code, when I upgrade from 2.1.2.111 to 2.1.4.178 and keep all environment identical, USB does not connect. the most I get is a "USB Device not recognized", and not input in the embedded side.

I am woring on the TM4C129x development board

any ideas?

Shlomo

  • Hello Shlomo,

    Are you using TI-RTOS for Tiva-C along with the TivaWare_C_Series-2.1.1.71b for this application as indicated in your Tool/Software selection? If so, that is a very big difference from the post you referenced, and we need to understand that upfront.
  • Hi Ralph,

    Busy morning I'm sure - poster has flagged, "Use of TI-RTOS."     Unclear if that was PAST used - as well...

  • Hello cb1,

    If you are referring to the post from Saurabh in Aug/Sept of last year, I can assure that wasn't TI-RTOS based. I saw his source code at one point and it was devoid of RTOS mechanisms. Therefore, if Shlomo would be using TI-RTOS, that would be a significant architecture difference from the prior referenced inquiry.
  • Hello
    I am using TI-RTOS.
    tirtos_tivac_2_16_00_08
    xdctools_3_32_00_06_core
    using CCS 7.20

    I saw the same phenomenon in an earlier project, when changing from 2.111 to 4.178
  • Hi Shlomo,

    Sorry, we really need to nail down the versions here. I see you are using TI-RTOS for TivaC 2.16.00.08. This ships TivaWare_C_Series-2.1.1.71b. Are you saying you are using TI-RTOS for TivaC 2.16.00.08 but were using TivaWare 2.1.2.111 instead. Then when you tried TI-RTOS for TivaC 2.16.00.08 with TivaWare 2.1.4.178 it stopped working.

    Finally for clarity...Are you using the TI-RTOS kernel (also called SYS/BIOS)?

    Todd
  • Hi Ralph,

    No - no reference to post from last year!    (While crazy - I'm not that far gone.)    Poster HAD included his use of TI-RTOS.     (evidence revealed, via screen cap, below)

  • Hello

    I am using TI RTOS.

    latest version for TIVA is 2.16.01.14.

    I am using 2.16.00.08 with tivaware 2.1.2.111  and it is working.

    tried both 2.16.00.08 and 2.16.01.14 with tivaware 2.1.4.178, everything (other peripherals) seems to work but USB does not connect.

    I am using TI-RTOS kernel. 

  • Hi Shlomo,

    I just imported the USB Serial example from TI-RTOS 2.16.01.14 (with TivaWare 2.1.1.71b that is included). I verified it worked. I then changed the include path and both the usblib and driverlib libraries in the project settings to point to the 2.1.4.178 release instead.

    After rebuilding, the example still worked. Did you change both?

    Why do you want to move to the new TivaWare?

    Note: we have not validated TI-RTOS with this newer version of TivaWare.

    Note: I did not rebuild the TI-RTOS drivers (e.g. UART, I2C, etc.) in the TI-RTOS product with the new driverlib. For completeness, I would do that also if you must move to the newer TivaWare. Instructions for rebuilding the TI-RTOS drivers is in the User Guide. The tirtos.mak file are the top has the location of the TivaWare to use.

    TIVAWARE_INSTALL_DIR      ?= $(TIRTOS_INSTALL_DIR)/products/TivaWare_C_Series-2.1.1.71b

    Todd

  • Shlomo,

    Did this get resolved?

    Todd

    [update 3/29...no word back from original poster so I'm marking this as TI thinks resolved. If you disagree, please reject the claim and post a followup].

  • I am sorry. I am burried with work and did not manage to log in from my phone. the problem is NOT solved, but I am waiting to resolve this for more quiet times
  • Hi Shlomo,

    No problem. I'm going to mark this as TI thinks resolved, but when you get to it and post a response, it will get opened again.

    Todd