• State Resolved
  • Locked Locked
  • Replies 19 replies
  • Subscribers 42 subscribers
  • Views 784 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.

CC3220: No start

Shamil Farsiev
Expert 1515 points

Part Number: CC3220

Hi guys!
i finished my second relies of my custom pcb.

i solder it and...

UniFlash connecting to chip at my custom pcb/

SOP is 010 or 000 (I switch it if need)

it programmable by UniFlash

But it doesn't start.

What is the check list? where did I a mistake?

  • 0
    Guru 39650 points

    Hi,

    - Are you able connect by JTAG and run your firmware from CCS (important is to know if you are able start NWP by sl_Start())?
    - What kind of CC3220 chip do you use (R, S, SF)?

    Did you follow recommandations in desing checklist ( www.ti.com/.../swru462 )?

    Jan

  • 0 in reply to Hnz
    Expert 1515 points
    1) no JTAG solder out
    2) SF
    important UPD:
    2.7k resistor at SOP2 pin GND is 0V and pin is 3.25V
    resistor is ok.
  • 0 in reply to Shamil Farsiev
    Guru 39650 points

    Hi,

    You have no ability to use JTAG/SWD at your new hardware? In case of that you not have JTAG available, determining reason of issue will be hard. For a first tests please use firmware where you not enable NWP (without calling sl_Start(), just a simple of LED blinking, etc.).

    You can try this procedure:
    - set to SOP 010 (or better 100) and restart your board
    - connect by Uniflash and upload firmware image in development mode
    - set SOP to 000 (not only to 010)
    - restart your board and wait let say 60sec
    - restart your board and wait moment again
    - set SOP 100 and connect by Uniflash
    - list files by Uniflash by user file browser (check if you are able list files and see you there system files like a /tmp/phy.cal)

    Update: use oscilloscope to show how looks voltage at SOP2 pin during device boot. You should see there short pulse to low during boot.

    Jan

  • 0 in reply to Hnz
    Expert 1515 points

    i'm going to do your advice but i see something.

    I just load leb blink program with sl_Start (0,0,0); in init.

    void main (void)

    {

        Board_initGPIO();
        Board_initSPI(); 
        sl_Start(0,0,0);

     while(1)

    {

       GPIO_write(board_id, Board_LED_ON);
        ClockP_usleep(NS_BLINK_SLEEP_50MS);
        GPIO_write(board_id, Board_LED_OFF);
        ClockP_usleep(NS_BLINK_SLEEP_50MS);

    }

    }

    it load by uniflash at flash and start. and it stop.

    just init, led_on and stop.

    sometimes it blink 1 or 2 times. and stop.

    where can be a(the?) problem(s)?

    p.s. where can i read about chip cc322sf internal dc_dc converters?

  • 0 in reply to Shamil Farsiev
    Guru 79975 points

    Hi,

    Yes, your thoughts are right. For me it also looks a issue with power source. At first step you should check if does not drop voltage at your power source at moment of sl_Start(). Please make sure that your power supply is able provide peak current for device calibration (450mA at 3.3V for 24ms). I am not aware about document which which provides additional information about internal DC-DC.

    Maybe you can try measure voltages at CC3220 pins, as done at your previous discussion threads:

    Unfortunately I am not able help you with this kind of hardware issue. Please wait for more advices from TI side.

    Jan

  • 0 in reply to Hnz
    Expert 1515 points

    did as you say

    no file .cal

  • 0 in reply to Shamil Farsiev
    Guru 79975 points
    Hi,

    Your NWP does nto start, from this reason no calibration file in flash.

    It could be interesting to look to power supply voltage at moment of sl_Start(). You can check for drop of voltage.

    Jan
  • 0 in reply to Jan D
    Expert 1515 points

    pin V at launchpad (as reference) V at my custom board
    9 1,15 1,23
    10 3,25 3,25
    21 0,88 3,15 (2,7k res is OK!)
    24 0 0
    25 1,9 1,9
    32 1,8 1,8
    33 1,8 and going down 1,8 and going down
    34 0 0
    35 0 0
    36 1,92 1,9
    37 3,25 3,25
    38 1,92 1,9
    39 3,25 3,25
    40 0,8 0,43
    41 0,8 0,43
    42 1,8 and going down 1,8 and going down
    43 1,15 1,4
    44 3,25 3,25
    45 1,4 1,3 and going down
    46 1,4 1,3 and going down
    47 3 3 and going down
    48 1,92 1,9
    49 1,22 1,21
    54 3,25 3,25
    56 1,15 1,21
  • 0 in reply to Shamil Farsiev
    Guru 79975 points
    Hi,

    Please wait for answer from TI. Voltages at DCDC_PA_SW_P and DCDC_PA_SW_N looks suspicious. But I am not sure...

    Jan
  • 0 in reply to Jan D
    Expert 1515 points

    thats why i need chemes of internal converters)

    i forget: at launchpad and my custom board i have 10uH (ten) 0805 inductors. all.

    at launchpad it works.

    upd: i return legacy iinductors (1, 2.2, 10, 10 uH)  to luanchpad, but solder them to my custom board. no result. luanchpad is work ok.

  • 0 in reply to Jan D
    Expert 1515 points
    power supply is fine. stable 3.3V
  • 0 in reply to Hnz
    Expert 1515 points
    >>Update: use oscilloscope to show how looks voltage at SOP2 pin during device boot. You should see there short pulse to low during boot.
    i see it.

    luanchpad SOP2 oscil pic
    https://tlgur.com/d/p8DVXyWg
    it was 3.3v -> rst -> delay -> PWM


    custom board SOP2 oscil pic
    https://tlgur.com/d/9gjAONOG
    it was 3.3v -> rst -> delay -> 3.3v
  • 0 in reply to Shamil Farsiev
    Guru 79975 points
    Hi,

    Thank you for updated pictures. From previous information we know that your firmware is loaded by and executed properly by bootlaoder. Your hardware failed at moment of sl_Start() when is required calibration current. From my point of view it looks as issue with DC-DC at CC3220 chip as I said before. Unfortunately I haven't experiences with diagnostic such kind of issue. You should wait for answer from TI side.

    Jan
  • 0 in reply to Jan D
    Expert 1515 points
    if i don't use sl_Start() - same problem
  • 0 in reply to Shamil Farsiev
    Guru 79975 points
    Hi,

    I think your hardware failed after you execute some part of your code which increase power consumption.

    Jan
  • 0 in reply to Jan D
    Expert 1515 points
    int main(void)
    {
    for (;;);
    /* Call board init functions */
    // Board_initGeneral();
    //
    // /* Start NoRTOS */
    // NoRTOS_start(); /* <- DO NOT TOUCH!*/
    //
    // /* Start the main function */
    // mainThread(NULL);
    return (0);
    }

    nothing. just for(;;); without any init.
    same problem
  • 0 in reply to Jan D
    Expert 1515 points

    i think same.

    i had 7 chips and 2 of them are burned and 3 are nonstartable.

    how i had burned first two of them:

    1) make my custom board

    2) solder all R,C,L chips for cc3220 only.

    3) load my firmware by uniflash

    4) ok. program start. i had wrote the log out by uart and normal working is 20-25 log strings per cycle.

    5) BUT! now it had been working for 4-5 strings and do a reboot. reboot and reboot...

    6) it became HOT. maybe 100-120 C degrees. Current was 1,5A (powered from cc3220sf-launchpad)

    it is about tho burned chips

    about 3 instartable: i had solder them to luanchpad. uniflash connect to them they programmable but firmware doesn't start.

    i check pcb designe many times.

    i wrote only led blinking program.

    and always sl_Start() is cause of burning.

  • 0 in reply to Shamil Farsiev
    Guru 79975 points
    Hi,

    I am not able determine what you can have wrong at your board / schematic.

    I think you should post your schematic and layout for review from TI side. Better will be open new thread for this topic.

    Jan
  • 0 in reply to Jan D
    Expert 1515 points

    i'll start a new thread