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 init process

Hello,

I'm using a CC3000 for a IoT project and I get stocked during the init process.

First step : HCI_CMND_SIMPLE_LINK_START

I send the init frame  {0x01, 0x00, 0x05, 0x00, 0x00, 0x01, 0x00, 0x40, 0x01, 0x00}

And receive the normal answer : {0x02, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00}

 

Second step : HCI_EVNT_SIMPLE_LINK_START command complete

I wait for the IRQ from CC3000 and send :  {0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF}

And expect to get   {0x02, 0x00, 0x00, 0x00, 0x05, 0x04, 0x00, 0x40, 0x01, 0x00}

While I receive {0x02, 0x04, 0x04, 0x04, 0x04, 0x04, 0x04, 0x04, 0x04, 0x04} wich is wrong.

I didn't found explanation on that frame in the documentation. I used an Arduino to test that and got the same behaviour all the time.

Does someone have an idea of what is happening ?

Thank you.

  • Hi Harly,

    Can you please confirm if the Chip Select and IRQ lines are still asserted when you are reading the data from MISO?

    Also please check the power to CC3000. Is it as per the "Recommended Operating Conditions" CC3000 data sheet?

    Thanks & Regards,
    Raghavendra

  • Hello,

    Thank you for your answer. Actually as you suggested, the power voltage was not exactly what it needed to be.

    Now I can communicate satisfactory with the CC3000 Chip.

    I can still observe sligth difference beetween what I expect according to the web documentation and what I get.

    For example during a HCI_CMND_READ_BUFFER_SIZE, the last byte of the answer being the padding byte is 0x09 instead of 0x00.

    Is the web documentation located on TI wiki up to date or is there another documentation available ?

    I didn't patch the CC3000 software for now. Can it be linked ?

    Thanks & Regards ,

    Alexandre