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.

CCS/CC3220: CCS/CC3220: error loading internal flash in CCS "data verification error"

Part Number: CC3220
Other Parts Discussed in Thread: UNIFLASH, , , CC3200

Tool/software: Code Composer Studio

Good afternoon
CC3220SF LAUNCHXL when programming the debug card there is no problem.
When programming a project based on the CC3220SF circuit, almost like on a debug board with the difference in:
          power supply 1.85
          external memory 32MB (probyval and 4MB)
there is an error "date verification error occurred, file load failed"


I followed the directions from www.ti.com/.../swru461a.pdf and there is no problem with the CC3220SF LAUNCHXL debug card.
The problem starts when the program is written to the board (my production), there is an error "date verification error occurred, file load failed"

I also followed the directions from e2e.ti.com/.../656657

But the problem remained
 
Can suggest solutions to the problem

  • Dima,

    I would suggest a few things.

    first, use Uniflash (www.ti.com/.../uniflash) to check to make sure you can connect to your device, and see that your memory is being recognized.

    If this works, then check you .cmd file and make sure are mapping this correctly.

    If it doesn't work, then we are having trouble connecting to your device, and we can debug from there.
  • Good afternoon
    When using Uniflash, it connects to the board and it is detected and the memory is determined

    But I can not flash even with Uniflash

    Count the memory is obtained

  • Hi,

    You cannot upload .out file by the Uniflash software. You need upload .bin file.

    Jan
  • Hi,

    Hmm... that is strange. Can you attach here your .rom file?

    Jan

  • Hi,

    I did not notice something important inside your screenshots. You have connected CC3220SF using JTAG. This is not proper way. You need to use UART connection, create image using Image creator and upload image by UART into sFlash (external flash).

    Jan
  • Then it's unclear why when connecting to JTAG to the processor on CC3220SF LAUNCHXL I use the side programmer XDS110 DEBUG no problems

  • Hi,

    JTAG at CC3220 is for a development purpose. For production production programming is used image uploaded into sFlash.

    Just to be sure, I summarise. Let me correct if I am wrong.

    - you are able connect via UART to your own CC3220SF based hardware
    - you have uploaded image inside sFlash and your CC3220SF is in development mode
    - you have proper SOP configuration (SWD/JTAG?) and you cannot connect JTAG from CCS or other IDE
    - you have connected XDS 110 Debug Probe to your own board (not XDS-110 from LaunchPad)

    Jan

  • Yes.
    - I can connect via UART to my equipment based on CC3220SF

    - I uploaded the image inside sFlash, and my CC3220SF is in development mode

    - I have the correct SOP configuration (SWD / JTAG?), and I can not connect JTAG from CCS or another IDE environment (to my project)

    although I can connect JTAG from CCS (to the processor on CC3220SF LAUNCHXL)

  • - I connected the XDS 110 Debug Probe to my own board (not XDS-110 from LaunchPad)
  • Hi,

    But you cannot connect JTAG/SWD to you hardware from CCS, right? How you have set SOP configuration at your hardware? Can you verify that SOP configuration at your hardware is correct and set according set target configuration in CCS?

    Jan
  • Hello Jan,

    I'm a colleague of Dima. I would like to confirm all hi said and would like to summarize/clarify issue:

    1. We have custom preregulated, 1.85-V mode board with CC3220SF. Schematics is exactly as in "Figure 6-2. CC3220x Preregulated 1.85-V Mode Application Circuit" in datasheet.
    2. SOP [2:0] is: 010
    3. Flash chip is same as in LAUNCHPAD: MX25R3235FM1IL0. Initially we have used another chip but changed it to MX25R3235FM1IL0, to eliminate possible issue here.
    4. We are able to connect and flash our custom board with LAUNCHPAD over UART using Uniflash, but board doesn't start. We have flashed OOB Uniflash project (~/ti/simplelink_cc32xx_sdk_2_10_00_04/examples/rtos/CC3220SF_LAUNCHXL/demos/out_of_box/uniflash/OOB_SF_freertos.zip), process completed successfully but nothing happened after restart or power cycle. No LED flashing (we have LED on pin 64, as in LAUNCHPAD), no "mysimplelink" network, nothing. We tried different example projects from SDK with same result (nothing happened after power cycle).
    5. We flasing in DEVELOPMENT mode, but can't connect over JTAG with dedicated XDS110 from CCS to our custom board.
    6. We are tested connection over JTAG to LAUNCHPAD with same dedicated XDS100 and same CCS settings (except voltage), to test our environment and CCS setup. We can connect and debug LAUNCHPAD but not our custom board.
    7. We have followed PCB design guidelines. All capacitors and inductors are very close to CC3220SF, PCB is 4-layer with dedicated planes for GND and 1.85V. Power traces 0.3mm thick and very short. All other traces between 0.15 and 0.3 mm thick ans as short as possible.
    8. 1.85V supply can handle 1A and drops from 1.853V to 1.846V when 1A load added. Ripple voltage is less than 10mV.
    9. We have checked signals at all CC3220SF pins and all looks fine except pin 24 (VDD_PLL). There is no voltage, but I believe there should be 1.4V. There is only 0.1uF X7R 0402 ceramic capacitor on this pin. We have re-checked this connection and no shorts in capacitor or surrounding tracks.
  • Hi,

    Nice description. Now I understand all correctly.

    All described at post above sounds reasonable. From my point it looks like a hardware issue but I have no clue what can be wrong.

    Please wait for answer from TI side. Maybe guys from App Team will have any idea.

    Jan
  • Elman/Dima - 

    Please double check your schematic against the one i have attached here.

    WCS002B(CC3220SF - 1.85 V Pre-Regulated Mode)_Sch.PDF

    also, please use +1.9VDC and check the ripple on the supply is not greater than 40mV. 

  • Josh,

    In schematics you have attached, pin 47 of CC3220 connected to VBAT_CC with "DNP" 0-ohnm resistor. Please confirm does this mean that pin 47 should be connected to 10uF capacitor C27 only and NOT to VBAT_CC (1.85V)?
    At schematics in datasheet pin 47 connected to 10uF capacitor AND 1.85V
  • Dear Elman -
    Please see the note in the datasheet schematic (on page 69), where the comment is made that connection to VBAT on that pin would be for the -R and the -S variants. You indicated you were using the -SF variant.
  • Josh,

    These notes are very confusing, and refer to non-existing parts. If you check note above one you talk about, you can see "PIN 45 and 46: For CC3220S and CC3220R parts, leave pin 46 un-connected (DNP L5 and R8). Pin 45 can be used as GPIO_31 if a supply is provided on pin47", and you also can see there NO L5, nor R8 in this schematics. Yes, I understand (now) this just copy-pasted from wide voltage schematics without even reading. There also no remarks about SF variant and no 0-Ohm resistor or jumper, so not clear in DS.

    Anyway, thanks for corrected schematics. Very bad it is provided in forum, instead of DS, ant take us a lot of time to get. Issue now resolved.

  • Elman -

    Glad it was resolved - I see your points to some degree - in the context of the datasheet, please consider that both typical schematics (figure 6-1 and Figure 6-2) have the -SF variant called out (part # is bottom left hand corner of the IC block) and in figure 6-1, L5 and R8 are shown, so in that context, if one was reading the document serially, and comparing wide versus pre-regulated schematics, it should have been clear. But again, I do see your point and we can add some wording to refer back here from figure 6-2 to figure 6-1.

    Additionally, the -R and -S part variants do exist. The -R version is more or less directly updated version of the CC3200 (ipv6, increased # of sockets and client connections), and the -S version is including the built in MCU image protection that the -SF has, but without the onboard XIP flash.