• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 40 subscribers
  • Views 1329 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.

CC3200 gcc - windows support not working

Delbert Johnson
Prodigy 20 points
Other Parts Discussed in Thread: CC3200, CC3100

When I try compile a sample application using make -f Makefile, as instructed, I get an error like the following:

$ make -f Makefile
CC ../main.c
arm-none-eabi-gcc.exe: error: CreateProcess: No such file or directory
../../../tools/gcc_scripts/makedefs:175: recipe for target 'obj/main.o' failed
make: *** [obj/main.o] Error 1

  • 0
    TI__Mastermind 26205 points
    Hi Delbert,

    Did you follow the steps in the section 5.3 of 'CC3200-Programmers_Guide' available in SDK?

    Regards,
    Ankur
  • 0 in reply to Ankur Baranwal
    Prodigy 20 points
    The quick answer is no. I'm not using the IAR workbench option but rather am trying to set up the windows GCC environment. I'm following the setup instructions in the CC3200 Getting Started Guide. I did solve the problem with compiling the sample problem but am still unable to configure the Build OpenOCD for FTDI Interface ( section 3.3.3 of the Guide). The problem with compiling the sample program stem from having both the new arm compiler/linker and an old one associated with Coocox. I discovered it by compiling with the -v option which showed references to the Coocox installed arm/bin.

    When I went through the setup of Cygwin and the FTDI interface I got Cygwin errors that modules we missing (when I ran the FTDI interface setup). I went back into the Cygwin setup and found the modules. Then the script started working. The first attempt resulted in the following error:

    script executed: ./configure --enable-maintainer-mode --disable-werror --disable-shared --enable-legacy-ft2232_ftd2xx --with-ftd2xx-win32-zipdir-ftd2xx

    result:
    configure: error: The ft2232 driver is deprecated, use --enable-ftdi to build its replacement, or force the old driver with --enable-legacy-ft2232_ftd2xx

    next I tried:

    $ ./configure --enable-maintainer-mode --disable-werror --disable-shared --enable-legacy-ft2232_ftd2xx --with-ftd2xx-win32-zipdir-ftd2xx

    and got:

    checking for ftd2xx.lib exists (win32)... configure: WARNING: ASSUMPTION: The (win32) FTDICHIP.COM files: ftd2xx.h and ftd2xx.lib are in a proper place
    checking whether ftd2xx library works... configure: error: Cannot build & run test program using ftd2xx.lib

    then I tried

    $ ./configure --enable-maintainer-mode --disable-werror --disable-shared --enable-ftdi --with-ftd2xx-win32-zipdir-ftd2xx

    and got

    checking for LIBUSB1... no
    configure: WARNING: libusb-1.x not found, trying legacy libusb-0.1 as a fallback; consider installing libusb-1.x instead
    checking for LIBUSB0... no
    checking for HIDAPI... no
    checking for HIDAPI... no
    checking for HIDAPI... no
    configure: error: libusb-1.x is required for the MPSSE mode of FTDI based devices

    None of these attempts worked with the next steps
    7. Run the command ‘autoreconf --force --install.'
    8. Run the command ‘make.’

    I don't have the reference right now but there was a update on the Ti website that indicated that we must use an older version of Cygwin to install the ftdi interface - I'm writing this from memory. I went the Cygwin website and searched the website for older Cygwin version. I didn't find any but did get information that indicated the Cygwin team discourages use of old version and do not support it nor provide old versions.

    I would suggest that the documentation in the getting started guide is outdated concerning setting up the GCC windows environment. The setup of the Arm GCC tools is ok as is the instructions for executing the make files.

    Any assistance that you can provide would be greatly appreciated.

    Also there is at least a suggestion in the product literature that the Visual Studio IDE can be used. Is there any documentation on how to do that.

    Thanks

    Del Johnson
  • 0 in reply to Delbert Johnson
    TI__Mastermind 26205 points
    Hi Johnson,

    Apologies for the delayed response.
    I am will test the process with the new cygwin and OpenOCD and update if any changes are required.

    The Visual Studio IDE solution is for CC3100 and is can't be used with CC3200.

    Regards,
    Ankur