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.

CC3100BOOST: cc3100BOOST

Part Number: CC3100BOOST
Other Parts Discussed in Thread: CC3100, CC31XXEMUBOOST,

We need urgent help connecting our host CPU  STM32F4 to the cc3100.

Problem description:

We connect STM32F40D7G-Discovery EVELUATION BORAD to cc3100Boost card & cc31xxEMUboost.

We follow the instructions guide as it was written in the following URL

http://processors.wiki.ti.com/index.php/CC3100_%26_STM32F4_Bringup_Guide

however it seems that the driver and porting to stm32host can’t be done strait forward.

At least 2 compilation errors were found. ( I tried my best by passing them)

And the SPI to my knowledge was not sufficient (As identification of alternate function to MISO/MOSI was missing)

When running the getting_started_with_wlan_station with IAR the application is stuck at begging in endless loop on the routine .

configureSimpleLinkToDefaultState()

sl_Start(0, 0, 0);

SlDrvSyncObjWaitTimeout()

I have emphasize that this routine is prior to sending any message to SPI so this is not issue of external connection but internal code issue.

Please help on this issue as we are stuck!!!

  • Yossi,

    I am debugging this on my end and will let you know my findings.

    What version of STM32F4Cube are you using?

    Thanks!

    Vince Rodriguez
  • Hi Rodrigues,

    I am  using version STM32Cube_FW_F4_V1.16.0.

    Please ignore the spi alternate function .my mistake it was well defined.

    But the rest still problem .

    Thanks!

  • Yossi,

    I was able to build and run the WLAN AP example and see the access point come up.

    I did run into two compile problems:

    1. _SlDrvHandleGeneralEvents is undefined, and then no definition is found while linking.

    • You can fix this by doing the following:
      • Add the following line to User.h
        • #define _SlDrvHandleGeneralEvents       SimpleLinkGeneralEventHandler

    2. APBPrescTable[] is not defined, and no definition is found when linking

    • You can fix this with the following:
      • Add the following line to system_stm32fxx.c
        • const uint8_t APBPrescTable[8]  = {0, 0, 0, 0, 1, 2, 3, 4};

    These were the problems I faced. Did you face similar ones?

    VR

  • Hi Rodriguez,

    Yes I faced similar errors and already correct them the same way you did.

    but still I am stuck with the above routine in endless loop.  (Seems that only interrupt from cc3100 will exit me from this).

    but I don't receive this interrupt. This leads me to the conclusion that something is wrong with the  physical connection between cards.

    The problem is that we posses only the boost3100 and emu3100 cards but we don't have at the moment the adaptor card.

    We think we made all the suitable connection between cards according to the document. but we may missed something so please advice.

    we connect the spi2 of the stm32 to cc3100boost,

    we connect vcc and ground.

    we connect uart to the cc3100emu  (we can see messages going on consul)

    we connect nhib port and the disable/enable port.

    We did not connect nreset (is that mandatory).

    Please advice also about the position of jumpers on both cards when there is no adaptor card.

    Best Regards Yossi,

     

  • Yossi,

    I would suggest ordering the adapter board if you can.

    Here is a picture of the pinout of the DISCOVERYADAPT Board and the CC3100 Side by side.

    /cfs-file/__key/communityserver-discussions-components-files/968/STMCC3100.docx

    Can you confirm all pins are connected in correctly?

    Regards,

    Vince Rodriguez

  • Hi Rodrigues,

    Thanks for your support!!!

    We finally got the adaptor card. At the beginning I suffered from the same phenomena. (endless loop waiting for interrupt from c3100 boost card).

    I thought that something with the voltage of the c3100 is wrong. So I changed JP8 to take power from LDO and this solved the problem.

    Now I see connection established .

    I suggest changing your  instruction guide to prefer the LDO when using stm32 discovery. And change the firmware with  the above 2 errors.

    next step will be to check the AP application.

     Thanks again!

    Best Regards Yossi Ferlandes,