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.

LAUNCHXL-CC3235SF:I cannot program an external CC3235SF.

Other Parts Discussed in Thread: LAUNCHXL-CC3235SF, CC3235SF, UNIFLASH, SYSCONFIG

Parça Numarası: LAUNCHXL-CC3235SF

Araç/yazılım:

LAUNCHXL-CC3235SF geliştirme kartı üzerinden cc3235sf kullanarak kendi geliştirme kartımı flaş etmeye çalışıyorum ancak başaramıyorum. Resimde gösterildiği gibi jumper ayarlarını yaptım ve düz kabloyu göründüğü yere taktım. Hatamın nerede olduğunu merak ediyorum, bana yardım edebilir misiniz? 

  • Hi,

    Are you able connect your hardware with Uniflash software (using UART)? At first step try Uniflash connection then you can move to JTAG (SWD) connection with IDE.

    Was your hardware revised by TI? Do you use QFN or MOD package? How many layer board do you use? What is your SOP mode? How looks power consumption of your board? How looks voltage VDD_ANAx and VDD_DIG?

    Jan

  • 1-) VDD_ANA voltage shows 0 volts.
    2-) VDD_DIG1 voltage is 1.19v
    3-) Sop mode is set to 010.
    4) pcb 4 layers.
    5) qfn sheath is used.
    6-) The board is designed according to TI LAUNCHXL-CC3235SF reference design. The same materials were used.

  • Hi,

    Please compare VDD_ANAx and VDD_DIG1 with LaunchPad. But I think you should have (~VDD_ANA = 1.8V, ~VDD_DIG = 1.2V). I think missing VDD_ANA means problem with internal DC-DC. That means wrong layout, wrong schematic, soldering issue, etc.

    Jan

  • Is our connection method, sop setting, etc. correct. After solving the problem with VDD_ANA, can we program the device as we show. 

  • Hi,

    Because I don't know your schematic, I can't confirm that. But be aware that JTAG connector (J7) does not contain UART which is mandatory for image programming. That mean with J7 connection only, you will not be able program your device.

    Solving issue with internal DC-DC is crucial. Without this your hardware is not functional. After this will be solved you can focus for UART connection with Uniflash.

    Jan

  • VDD_ANA1 voltage shows 0 volts even though there is no error on the board. launchpad shows this value as 1.9v. Where should we look for the error. 

  • Will I connect the uart pins via launchpad. Can you give more detailed information about how to connect to uniflash with uart? 

  • I want to ask you this.
    Suppose we solve the hardware problems.
    In this case, how can I program my own board through the launcpad development board. actually I am asking you this, this is what I need.

  • Hi,

    It may to be issue with DC/DC return paths ... see swru536 at chapter 4.2. This is pretty common issue when PCB layout was not properly done and TI recommendation was not taken into account.

    Please see production line guide chapter 5.4. There is described that Image programming is needed RX, TX, RST and GND. For JTAG (4-wire) connection with IDE you need TDI, TDO, TCK, TMS, GND and set proper SOP mode.

    In case your issue is related to internal DC-DC it is likely you will need to change your layout.

    Jan

  • I am confused. It is not clearly explained in the documents you sent.

    Please answer my questions one by one. Thank you for your attention.

    Question 1-) Is it possible to program an external card with jtag via Launchpad?
    Question 2-) If it is not possible to program with jtag via Launchpad, we can only program by connecting the uart pins to the external card.
    Question 3-) How do I need to connect my launchpad and external card together to program via Ide.

    Please answer these questions assuming that I have solved the hardware problem.

  • Hi,

    For programming of SPI flash you need to use UART (using Uniflash or Sysconfig Image Creator). JTAG is used for debugging from IDE. You cannot program SPI flash using JTAG.

    1) It depends that you mean by word "program".

    2) JTAG for development. UART for SPI flash programming.

    3) Connect JTAG (4-wire or 2-wire) and UART. Both are needed for development. For production is UART enough.

    Jan

  • Thanks for your answer. I understand that I need to connect both jtag and uart pins from launchpad to my own private card to develop.

    How can I discover the reason why I am not getting VDD_ANA voltage which is the other problem. The layout of the board is the same as on the launchpad.

  • Gördüğünüz gibi düzen launchpad ile aynı ancak VDD_ANA, VDD_DIG voltajı neden 0 volt olarak gösteriliyor.  

  • Could it be that the VDD_ANA and VDD_DIG voltages are zero because the board has never been programmed?  

  • Hi,

    No. Issue with DC-DC is not software related.

    Hard to say what exactly can be issue.

    Jan

  • I solved the problems with the voltages.
    Now I ask for your help.

    Please write step by step how I can program my external card with my Launcpad card.
    I don't want to do anything wrong because I am new to this subject.
    If you can show me what to do step by step, it will be very healthy.

  • Hi,

    At first step connect your hardware using UART (as described a production line guide) with Uniflash and program blank image in development mode. How to use Uniuflash you find a SimpleLink academy. After that you can try JTAG connection with IDE (4-wire or 2-wire JTAG according SOP mode).

    Jan

  • İlk resimde görüldüğü gibi uniflash programıyla cihaza bağlanıyorum. 

     

    Ancak 2. resimde görebileceğiniz gibi harici entegrasyonuma kod atarken bu hatayı alıyorum. Hem JTAG hem de Uart pinlerim bağlı. 

    SOP_MODU=010

  • Hi,

    It is likely that you have problem with SPI flash. Because "SFLASH codes" at Uniflash is zero.

    At fist stage you need fix issue with SPI flash. After that you can program in development mode image to unlock JTAG.

    Jan

  • I changed the flash integrator but the result is as in the image. do you think the problem is related to the flash integrator. 

  • Hi,

    You have hardware issue with SPI flash. CC3235 is not able communicate with SPI flash or you are using non compatible SPI flash.

    Jan

  • I am using the same SPI Flash integration as Lauchpadxl.
    In this case, could the problem be related to the soldering on the spi line?

  • Hi,

    Who knows... soldering issue, design issue, PCB manufacturing issue...

    At first step you should inspect your hardware (visually, electrically). After that inspect voltage levels and communication at oscilloscope. At final stage capture communication at logical analyser and check SPI commands.

    Jan

  • Thank you for your help. we were able to code the device but there is a problem. The device detects fewer acces points than the launchpad device. It also cannot detect 5GHZ broadcasts.
    In this case, I wonder where the error is, can you help me.

  • Hi,

    This looks like issue at RF 5GHz path (layout, issue with diplexer, etc.) if your software works at LP and not at your board.

    Jan

  • I sent it to you before. The card slice is the same as the launchpad. Could the problem be due to soldering?

  • Hi,

    It may to be possible...

    Jan

  • What steps would you suggest to follow to solve this problem. 

  • Hi,

    It is hard to provide advice because it depends on your equipment and experiences with RF debug. At first stage check assembly RF components. Because it seems your board have many soldering issues.

    But personally I would start with testing of RF switches and filters. After that I would validate antenna path at VNA. Usage spectrum analyser with near field probes may to be interesting as well (5GHz will be likely out of range of common E probes, but there still could be something interesting).

    Jan

  • Hello; I am running my device in Acces point mode but it works as 2.4Ghz. How can I run it as 5Ghz. 

  • Hi,

    You need to set proper channel by API SL_WLAN_AP_OPT_CHANNEL. Personally I never tested this, but according SWRU455 this should work.

    Jan

  • i just changed it here i made the channel 36 but it still shows as channel 1 and it works 2.4 gHz. 

  • Hi,

    No. You cannot modify host driver by that way. You need to call proper sl_ API to set option. For mode details see SWRU455.

    Do not modify host driver files. If you do that, that you have chance that you broke something.

    Jan

  • Gönderdiğiniz dosyadaki yöntemi denedim ama işe yaramıyor. Kodum bu şekilde erişim noktası olarak çalışıyor. Buradaki koda ne eklemeliyim, lütfen örnek kod parçasını yazabilir misiniz? Yardımınız için teşekkürler. 

  • Hi,

    Add into your initialisation code settings for AP mode (somewhere after calling sl_Start()). Be aware after changing AP mode settings it is needed NWP reset (calling sl_Stop() and sl_Start()). Maybe you can also try change settings via Sysconfig (but I am not sure if there is option for channel for AP mode). Sorry, I will not write code for you, I haven't time for such things.

    As I said you cannot modify macros at host (sl_) driver. This is best way to broke wifi functionality completely and nobody will be able help with issues with modified host driver.

    Jan

  • Selamlar;
    Bakın ben bu şekilde 5ghz'i ayarlamaya çalışıyorum ama oluşturulan erişim noktası hala kanal 1 ve 2.4ghz olarak oluşturuluyor. Nerede hata yapıyorum acaba.

  • Hi,

    As I said at previous answer, after changing channel number you need to restart NWP. Also make sure that channel is enabled according set country code.

    Why you not add API to changing AP mode channel after changing device mode but before NWP reset?

    Jan

  • “Why didn't you add API to change AP mode channel after changing device mode but before resetting NWP?”

    I don't understand what you mean here

  • Hi,

    You should add API call SL_WLAN_AP_OPT_CHANNEL after changing device (sl_WlanSetMode()) mode and before NWP reset (sl_Stop()/sl_Start()).

    Jan

  • if (uiMode != lRetVal)
    {
    Display_printf(display, 0, 0, "Switching Networking mode on application request");

    lRetVal = sl_WlanSetMode(uiMode);
    ASSERT_ON_ERROR(lRetVal);

    /* Set the desired channel for AP mode before restarting NWP */
    unsigned char channel = 36; // Example 5 GHz channel
    lRetVal = sl_WlanSet(SL_WLAN_CFG_AP_ID, SL_WLAN_AP_OPT_CHANNEL, 1, &channel);
    ASSERT_ON_ERROR(lRetVal);

    /* Stop and start NWP to apply new settings */
    lRetVal = sl_Stop(SL_STOP_TIMEOUT);
    ASSERT_ON_ERROR(lRetVal);

    lRetVal = sl_Start(0, 0, 0);
    ASSERT_ON_ERROR(lRetVal);
    }  

    this is how I change it, right? 

  • Hi,

    Yes, this looks correct.

    Please see SWRU455 at appendix B1 where is stated which sl_ APIs need to NWP reset to be applied.

    Side note: If I could suggest something you according your questions at this tread. You should start with basic things around CC32xx devices (read documentation including SWRU455, check SDK examples, goes via SimpleLink academy). I think your project is inviably moving to disaster. By these words I don't want to harm you, but help you.

    Jan

  • Sevgili Jan;

    Ürünlerinizi TI teknik desteğine güvenerek satın aldık ve mevcut projemizi ürününüze çekmek istiyoruz ve fazla zamanımız yok.

    Size sorduğum soruları doğrudan yanıtlamak yerine beni belgelere yönlendiriyorsunuz. Ürünlerinizi yeni kullanmaya başlayan biri için bunun doğru yöntem olduğunu düşünmüyorum. Sorunlarımı doğrudan çözmeme yardımcı olmayacaksanız Ti ​​ile nasıl çalışabiliriz?

  • Hi,

    I am not TI employee, I don't have single penny for answering your questions here.

    Where I did not answered your question directly? My goal is to help to be familiar CC32xx this platform and answering your questions. I am not here to do your job and write code for you.

    Jan