• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 39 subscribers
  • Views 240 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.

CC3000 HCI_CMND_SIMPLE_LINK_START problems

Ing. Bruno Palacios
Prodigy 170 points


Hello,

I am trying to interface an stm32f4 uC with the CC3000EM board. The thing is I am having problems with the HCI_CMND_SIMPLE_LINK_START command.

I have read a lot of post and I think I figured out the possible problem, but I don´t know how to solve it or why is happening. The thing is when I call wlan_start(0) I send the properly HCI_CMND_SIMPLE_LINK_START package in the properly way (with 1ms delay between the first 4 and thelast 6 bytes). At this point the CC3000 answer :

0x00 0x40 0x81 0x02 0x01 0xFE 0x00 0x00 0x00 0x00

Which is not a valid answer so the code hangs waiting for the correct answer. I tried 2 different CC3000EM boards with same results.

What I figured out is that there is not I2C communication between eeprom and CC3000. The pins remains at 1.5v both. Then after reading some post and recommendations I tried to put a 5.6K and 10K resistor pulled up to 3v with same results (1.8v level)

Does anybody know what is the problem? The jumpers of the board are in user mode(2-3)

Thanks in advance.

Bruno


  • 0
    Prodigy 170 points

    UPDATE:

    I found that there is I2C communitaction but only when I don not use the ST-Link v2 debbuger. Now the answer is:

    0x02 0x00 0xFF 0x00 ... 0x00 for the HCI_CMND_SIMPLE_LINK_START which is correct and then the module send:

    Host send: 0x03  0x03 0x03 0x03 0x03 0x03 0x03 0x03 0x03 0x03

    CC3000:    0x02  0x00 0xFB 0x00 0x00 0x00 0x00 0x00 0x00 0x00

    But still not the right answer.

    Something I forgot to tell is that this answer is sent by the cc3000 immediately, not after 1s as should be.


    Any idea?

  • 0 in reply to Ing. Bruno Palacios
    Prodigy 170 points

    Solved. I had a couple of errors. Firstone the IRQ Interrupts was configured in Rising edge instead of Falling.

    And the Debugger shares the SWO pin with the SPI3 CLK pin. I don´t know why but even if the clock was working well (I am able to see the signal in the logic analyzer) if those pins are connected together the module behaves weird.

    So this particular problem is solved.