• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 42 subscribers
  • Views 869 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Flashing a custom board CC3100

Luke Dolan
Prodigy 160 points
Other Parts Discussed in Thread: CC3100, CC31XXEMUBOOST

Hi,

I'm currently in the process of designing a custom board that includes the CC3100. I want to ensure that I will still be able to flash updates to the device.

My initial understanding was that I would only need to break out  the UART lines (Pins 32, 50, 55, 57, and 61) for the CC31XXEMUBOOST, however, the reference designs make mention of leaving the nHIB line floating for control by the CC31XXEMUBOOST. I communicate between the host MCU and the CC3100 via the SPI lines, as such I was curious as to what lines the CC31XXEMUBOOST needs broken out in order to flash the device.

Please let me know if any of this is unclear and I'll try to clarify.

Kindest Regards,

Luke.

  • 0
    TI__Mastermind 27390 points
    Hi Luke,
    Formatting and/or writing files to the serial flash device through the CC3100 UART interface requires the use of the following CC3100 pins:
    • 55 - UART1 TX
    • 57 - UART1 RX
    • 2 - nHIB or 32 - nRESET (either can be used)

    For the CC31XXEMUBOOST for programming you can use:
    (UART TX) P1.3
    (UART RX) P1.4

    Regards,
    Aaron
  • 0 in reply to made4engineering
    Prodigy 235 points
    Did you manage to get your custom board yet?

    I've been trying to get mine to work without any success.

    I can format, update service pack, all successful

    But I cannot really use either simplelink studio or talk to it using one of the examples by spi with Tiva Launchpad

    CC3100R1 does't respond to either one, as if there is no software in its rom.

    simplelink studio and tiva getting started example both stuck at same location:

    OSI_RET_OK_CHECK(sl_SyncObjWait(&g_pCB->ObjPool[ObjIdx].SyncObj, SL_OS_WAIT_FOREVER));

    The booster pack with older chip works fine in doing everything

    Actually, if anyone got a custom board with CC3100R1 and could share his experience. or how they managed to get it to work.

    details on my experience on this thread:
    http://e2e.ti.com/support/wireless_connectivity/f/968/t/390152

    Any help would be highly appreciated!

    P.S. one thing I've noticed and might be helpful with others, that the Micron chip used as serial flash M25PX80-VMN6TP (its used on all BoosterPacks with the pre-production cc3100) in the datasheet and in the reference design doesn't work with CC3100R1. I've wasted quite a lot of time trying to get it to work until I found in the CC3100 wiki FAQ that its not supported, where as in the datasheet it says any Serial flash in the list beside the one in the reference application schematic !!!!!

    I've ended up using : S25FL208K0RMFI011 which worked fine with CC3100R1 and its being formatted
  • 0 in reply to Khalefa Mohammed
    TI__Mastermind 26155 points
    Hi Khalefa,

    Can you please check and re confirm if the serial flash part you were using is M25PX80 and not M25P80?

    Regards,
    Ankur
  • 0 in reply to Ankur Baranwal
    Prodigy 235 points

    Hello

    sorry for delay in getting back

    Yes I'm pretty sure its M25PX80-VMN6TP

    The weird thing that I've tried using it with boosterpack, and it worked just fine. But my custom boards with CC3100R1 never worked.

    This one works however: S25FL208K0RMFI011

  • 0 in reply to Khalefa Mohammed
    TI__Genius 11120 points
    Can you comfirm what voltage is your board working at. The M25PX80 is rated from 2.3V to 3.6V.
    Also do you have a pull-up resistor on the CS# input of the s-flash. this can cause some instability during power on.
    Note that the same s-flash is used on all our booster-packs and launchpads and across multiple customers on their custom boards without any issues.
    The issue you are seeing is mostly related to the in-rush current taken by the device when it comes out of RESET. Can you check it your system is capable of sourcing about 500mA(Device would draw about 380mA from 3.3V). Check if there are any dips in the supply.