• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 41 subscribers
  • Views 1112 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.

TIDC-BLE-TO-WIFI-IOT-GATEWAY: Launch Pad approach is not booting

kayathri m
Intellectual 290 points
Part Number: TIDC-BLE-TO-WIFI-IOT-GATEWAY
Other Parts Discussed in Thread: CC2650, CC3200, CC3200SDK

Hi,

We are trying to test BLE to WiFi gateway using CC3200 and CC2650 Launch Pads. 

We followed the steps given in this link:

http://processors.wiki.ti.com/index.php/Bluetooth_Smart_to_Wi-Fi_IoT_Gateway_-_Launchpad/Boosterpack_approach.

if we are flashing application_bootloader.bin as /sys/mcuimg.bin then the board is not booting up.

If we are flashing blefi.bin as /sys/mcuimg.bin then the board is booting up but it is getting stuck in "[NPI] Waiting for SBL to be complete ...".

We have also referred to the following links:

https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/t/543219

e2e.ti.com/.../393909

tidua62.pdf

Any inputs are helpful to proceed  further.. 

Regards,

Kayathri

  • 0
    TI__Expert 5285 points
    Hi Kayathri again,

    sorry my mistake - for some reason this keeps showing in the wrong forum,
    I'll check and make sure the right forum can also see this issue.

    BR,
    Chen Loewy
  • 0 in reply to Chen Loewy
    Intellectual 290 points
    Hi,

    Thank you Chen Loewy.

    Meanwhile, I am testing some of the example projects like "getting_started_with_wlan_ap" , "connection_policy" from CC3200SDK_1.3.0 and it seems to get stuck in there configureSimpleLinkToDefaultState() and getting error like
    [GENERAL EVENT] - ID=[0] Sender=[0]

    Error [-3] at line [512] in function [ConfigureSimpleLinkToDefaultState]

    I am using CCS & version is 8.0.0.00016 .


    Regards,
    Kayathri
  • 0 in reply to kayathri m
    Guru 39650 points

    Hi Kayathri,

    What CC3200 LaunchPad version do you use? What chip number is on CC3200 chip at  LaunchPad? It is marked XCC3200HZ or XCC3101GZ?

    Jan

  • 0 in reply to Hnz
    Intellectual 290 points
    Hi,

    I am using CC3200 Launch Pad and chip number is marked as XCC3200HZ. I have tried to link simplelink.a from OS debug to the project but it is not helping. i am getting same error again.


    Regards,
    Kayathri
  • 0 in reply to kayathri m
    Guru 39650 points
    Hi Kayathri,

    You have pre-production LaunchPad. CC3200 LaunchPads with pre production silicone are not supported anymore. You have following options:
    - buy new CC3200 LauchPad
    - downgrade to SDK version 1.1.0 ( www.ti.com/.../1.1.0 ) and stay at this version with particular service pack

    I not recommend 2nd option. Your CC3200 will be vulnerable to security threats including KRACK attack ( CVE-2017-13077, etc.). Other informations you find here e2e.ti.com/.../2009814

    Jan
  • 0 in reply to Hnz
    Intellectual 290 points
    Hi Jan,

    Thank you very much.

    I have downloaded SDK1.1.0 and Service Pack 1.0.0.10.0 and Now I am able to test examples projects in CC3200SDK1.1.0.

    We have ordered new CC3200 Lanuch Pad. Till it arrives, Is it possible to test BLE to WiFi Gateway code with any modifications.

    Regards,
    Kayathri
  • 0 in reply to kayathri m
    Guru 39650 points
    Hi Kayathri,

    I am not familiar with this design. But I think you can continue at development with pre-production device and SDK 1.1.0.

    It looks that that this design was originally released even with older SDK 1.0.0 ( processors.wiki.ti.com/.../CC32xx_Release_Notes_1.0.0 ).

    Jan
  • 0 in reply to kayathri m
    Intellectual 290 points
    Hi Jan,

    When application_bootloader.bin (/sys/mcuimg.bin), blink.bin ( /sys/mcuimg1.bin ) are flashed then, the board is not booting up.

    The same problem is there in BLE to WiFi gateway firmware also.

    Regards,
    Kayathri
  • 0 in reply to kayathri m
    Guru 39650 points

    Hi Kayathri,

    This secondary bootloader is joined with OTA update. Please read documentation for OTA update. Please make sure that you have disabled FAST_BOOT option during compiling of bootloder. Also I know that pre-production devices does not support OTA updates. I am not sure if this also cannot be reasons of issues.

    Unfortunately secondary bootloader from OTA update is hard to debug, due to relocation mechanism. My only advice for you is to follow documentation for OTA update.

    Jan

  • 0 in reply to Hnz
    Intellectual 290 points
    Hi Jan,

    Thanks for the reply. We got a new launch pad and we are able to work with it.

    Regards,
    Kayathri