• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 30 subscribers
  • Views 1855 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.

RM46L852 error FTDI driver(Error -154 @ 0x0)

Maria Wahono
Prodigy 170 points

Error connecting to the target:
(Error -154 @ 0x0)
One of the FTDI driver functions used to
write data returned bad status or an error.
(Emulation package 5.0.747.0)

so I tried resetting and unplugged-plugged the connections, but still got the same error message, the error message was not there two days ago, and the project run successfully. But now with the exact same project, I got this error, could someone possibly know the solution?

Thanks

  • 0
    TI__Guru 68920 points

    Maria,

    I think this usually means that you're not even connecting to the XDS100v2 on board.

    Do you have just one board / project or are you multitasking -- Sometimes this is as simple as changing the 'Active/Default' target configuration that you're using by accident, or unplugging the emulator.  I get this a lot when I'm switching between boards and just forget a step.

    If it's not something simple like that, then would it be possible for you to open your target configurtion and use the "Test Connection" button and then dump the results.    

  • 0 in reply to Anthony F. Seely
    Prodigy 170 points

    I already choose the XDS100v2 option in the CCS, and Iam also sure that the active/default target is right, and I tried unplugging-plugged in the emulator, non of that work

    Where do the test connection button located at?

     

    Thanks

  • 0 in reply to Maria Wahono
    Prodigy 170 points

    So I check the test connection and got this:

    it is an error, how do I solve this?

    Thanks.

  • 0 in reply to Maria Wahono
    TI__Guru 68920 points

    Maria,

    Yes, but I think it got further than I was expecting based on the other error message - it looks like it is finding the XDS100v2.   I've never seen the error message from the SCIF driver like that though. Are you on Windows 8?

  • 0 in reply to Anthony F. Seely
    Prodigy 170 points

    No, I am in Window 7, so what do you think might be the problem? Two days ago it was definitely fine

  • 0 in reply to Maria Wahono
    TI__Guru 68920 points

    Maria,

    Ok.  It's hard to say what the problem is just yet.

    There should be more information in the Test connection dialog - you have to scroll down.  It looks like it found the emulator so that's good but it might be reporting something like a cable break.

    Maybe you could paste the textual contents of the Test Connection dialog for me?

    Also there is a page here http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    That has some pointers on diagnosing JTAG problems. 

    Coming at this from a different angle - did you do anything like update CCS since this last worked?
    How about installing any other new USB devices or running one of our safety demos?

     

  • 0 in reply to Anthony F. Seely
    TI__Guru 68920 points

    Also specific to your board,  when you plug in the emulator you should see some LEDs (probably blue) one near the FTDI chip should be on and a few near the USB should be intermittently blinking when you're trying to talk to the board.

    On the other side of the board near the power jack you should see a group of LEDs in a line. (4 of them).  These should all be on as well - if not then there is a problem with the power supply.  

    There is one more LED on the board that should not be on - this is the one marked "extjtag' below the 20 pin ARM JTAG header which is near the USB interface and near the SDCARD slot.  If this is on and you're trying to use the on-board XDS100v2 something is wrong there.

  • 0 in reply to Maria Wahono
    Prodigy 170 points

    I tried it on a different computer and it says error 180, power loss.

  • 0 in reply to Maria Wahono
    Prodigy 170 points

    this is the test connection dialog

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\Minto\AppData\Local\.TI\213602635\
    0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioserdesusb.dll'.
    The library build date was 'May 30 2012'.
    The library build time was '22:52:27'.
    The library package version is '5.0.747.0'.
    The library component version is '35.34.40.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    The controller has an insertion length of '0' (0x00000000).

    [End]

  • 0 in reply to Maria Wahono
    TI__Guru 68920 points

    Ok so the simplest would be if you had forgotten to plug in the wall wart.
    But if not that - then this is where those 4 leds come in.  Are they all on? If not some of the rails are out.

    Just saw your post on the test connection - was that really all that showed up? 
    There wasn't any more text if you use the scroll bar on the right of the window?

    If so I haven't seen that before but maybe it's something that goes along w. your USCIF error.  The USCIF is the lower level of jtag driver software and usually it's not something you interact with through CCS.

  • 0 in reply to Maria Wahono
    Prodigy 170 points

    Also specific to your board,  when you plug in the emulator you should see some LEDs (probably blue) one near the FTDI chip should be on and a few near the USB should be intermittently blinking when you're trying to talk to the board.(yes it is on)

    On the other side of the board near the power jack you should see a group of LEDs in a line. (4 of them).  These should all be on as well - if not then there is a problem with the power supply.  (only 3 of them are on, DS3 is off)

    There is one more LED on the board that should not be on - this is the one marked "extjtag' below the 20 pin ARM JTAG header which is near the USB interface and near the SDCARD slot.  If this is on and you're trying to use the on-board XDS100v2 something is wrong there.(not on)

    So with this, how can we solve the problem?

    Can you possibly talk on the phone?

    Thank you very very much for the immense help :)

  • 0 in reply to Maria Wahono
    TI__Guru 68920 points

    Hi Maria,

    Ok, this is getting somewhere except I'm a little confused by the power LEDs.   They should read +12V, +5V, +3.3V and +1.2V.    If your board is the same as mine DS3 would be from +5V and if this supply is out the +3.3V and +1.2V supplies should also be out.   What I'd normally expect to see is the +12V LED on, and the other three off.  This happens if you blow the fuse.   It is very easy to blow the fuse if you do probing on the connectors and are not super careful with the ground lead (say from your oscilloscope) - if you ever touch that to one of the pins on the connector it will pop the fuse.

    So just want to check that its' really 3 ON, 1 Off and not the other way around.

    If you want to talk this through you can send me an email and I'll reply w. a phone number to call.  email is a dash seely at ti dot com.