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.

  • Resolved

Linux, no USB FET was found

Prodigy 175 points

Replies: 5

Views: 2670

Hello, everyone,

I am using MSP-EXP430G2 board with g2231 microcontroller. 

If I use the microcontroller in the bundle Ubuntu 14.04.1 + CCSv.6.0.1.00040 I am getting the following error:

Error initializing emulator: No USB FET was found.

In the bundle Windows 7 + CCSv.5.5.0.00077 everything works fine.

Could anyone suggest the way to solve this issue? 

Thank you in advance, 

Yevhen

  • Hello, everyone,

    Still experiencing the same issue. After searching in the internet I understood that many Linux users have the same problems. Is it not possible to use MSP-EXP430G2 boards in Linux?

    Thank you in advance, 

    Yevhen

  • In reply to Yevhen Yerko:

    Yevhen Yerko
    Is it not possible to use MSP-EXP430G2 boards in Linux?

    As per http://processors.wiki.ti.com/index.php/Linux_Host_Support_CCSv6#Not_Supported_2 CCS doesn't support the MSP-EXP430G2 board in Linux.

    MSPDebug does support the MSP-EXP430G2 board in Linux. Given that MSPDebug can act as a GDB stub, maybe it is possible to get CCS under Linux to debug a MSP-EXP430G2 board via MSPDebug?

  • In reply to Chester Gillon:

    Thank you, Chester,

    I will try to solve the problem in your suggested way)

  • In reply to Chester Gillon:

    Chester,

    Since Yevhen doesn't report on his solution of the problem, I try to go in the same direction myself. But the task is a little bit beyond my abilities, so far. I'll continue to make MSPDebug to serve as a GDB stub, but now my aim is more primitive: just to program the target MCU from CCS via MSPDebug.

    Let me describe the situation more precisely.

    1) I have an MSP-EXP430FR5739 Experimenter Board, but it's firmware is reprogrammed. So it's eZ430 probe now.

    2) A target MCU is MSP430FR5726, it's connected to the probe.

    All the stuff worked fine under Windows with Code::Blocks and gcc compiler. But I needed a Linux. There was a problem with C compiler under Linux, then that bug was fixed (Red Hat + TI compiler) but the size of my code was too big and I had to return to TI compiler - in CCS v6. So: 

    3) My OS is Linux Mint, I have a project in CCS v6 and it's built OK. But, as you know, eZ430 probes are not supported by CCS under Linux.

    4) I installed MSPDebug v.0.21. In a command line mode it programs the target MCU with the command:

    mspdebug -n --fet-force-id MSP430FR5739 rf2500 "prog ADC_CCS_brd_01_11.out"

    (I had to use forced ID because the mspdebug does not support MSP430FR5726 chip)

    To put it all together: if I launch both a CCS and a terminal, I can work. I use the Studio as an editor and compiler, then I switch to the terminal and program my target MCU. Is it OK? Nope! It would be much better to launch MSPDebug (as a programming tool) directly from the Studio. Can you tell me how to do it? If it is possible to launch an external program from Notepad++, from Code::Blocks, from other IDEs and editors...

  • In reply to Iurii Vlasenko:

    Hmmm... Some sort of a solution is here.

    1) Switch to a "Debug" perspective in a CCS. The "Run" item in pull-down menu appears.

    2) Now we can create our external tool configuration. "Run - External Tools - External Tools Configuration" brings us to a possibility to create a new Run Configuration.

    2) Name the configuration (I choose "mspdebug probe"), put the location (my: /usr/bin/mspdebug), set working directory in Debug where the output file is located) and write down the mspdebug arguments:

    3) I checked a "Build before launch", "The project containing the selected source" and "Include referenced projects" in a Build pane.

    4) The "Allocate console" is checked in a Common pane, while "Launch in background" is unchecked.

    5) After configuration saving I'm able to run the tool just after any editing (but only in the "Debug" perspective!): 

    "Run - External Tools - 1 mspdebug probe"

    or

    a key with "run" icon in a pull-down menu

    In a Console window I can see the result of building and programming. 

    That's all, folks!

    I think this solution may be optimized but my present level of CCS use is not enough for it. So all propositions are wellcome!

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.