Other Parts Discussed in Thread: UNIFLASH, CC3220SF
Hi everyone,
I get the exact same error in the same situation: a custom made CC3220modSF board.
I tried working with Uniflash GUI and Uniflash CLI with the same result. Here is what the cmd line gives me:
C:\ti\uniflash_4.1>dslite --mode cc3220 project program --name customBoard1 --port COM8 --dev
Executing the following command:
> C:\ti\uniflash_4.1\simplelink\gen2\bin\SLImageCreator.exe project program --name customBoard1 --port COM8 --dev
Config file load error ([Errno 2] No such file or directory: 'cfg.json'), using defaults
INFO:slbootloader.slbootloader:Connecting to device
INFO:slbootloader.slbootloader:--- Please power off the device ---
Press ENTER to continue
INFO:slbootloader.slbootloader:Power off
INFO:slbootloader.slbootloader:Set break signal
INFO:slbootloader.slbootloader:--- Please power on the device ---
INFO:slbootloader.slbootloader:Power on
INFO:slbootloader.slbootloader:Clear break signal
INFO:slbootloader.slbootloader:Connection succeeded
INFO:slbootloader.slbootloader:Received storage list
------------------------
Copyright 2014 TI.com. All rights reserved, SimpleLink programming image builder
Builder = 3.0.1.3
Interface version = 1.0.2.16
Recommended command line window resolution W124 X H67
The output directory is :[C:\Users\kdriessens\.SLImageCreator\projects\customBoard1\sl_image]
The XML file is :[C:\Users\kdriessens\.SLImageCreator\projects\customBoard1\sl_image\ImageConfig.xml]
Validate the XML against the schema.
The XML validation passed.
------------------------
Commands Set Number = 0
CommandNum = 0
CommandFormatStorage:
CommandNum = 1
CommandWriteCertificateStore:
FileLocation = ../files\certstore.lst
FileSystemName = /sys/certstore.lst
File max size is 7000 bytes, actual size 3640 bytes
After running the extracting the file will require 4 blocks on the device
CommandNum = 2
CommandWriteSystemFile:
FileLocation = C:\Users\kdriessens\.SLImageCreator\projects\customBoard1\sl_fs\sys\ipcfg.bin
FileSystemName = 17
File max size is 200 bytes, actual size 200 bytes
After running the extracting the file will require 2 blocks on the device
CommandNum = 3
CommandWriteSystemFile:
FileLocation = C:\Users\kdriessens\.SLImageCreator\projects\customBoard1\sl_fs\sys\device.name.bin
FileSystemName = 5
File max size is 98 bytes, actual size 98 bytes
After running the extracting the file will require 2 blocks on the device
CommandNum = 4
CommandWriteSystemFile:
FileLocation = C:\Users\kdriessens\.SLImageCreator\projects\customBoard1\sl_fs\sys\ap.cfg.bin
FileSystemName = 1
File max size is 158 bytes, actual size 158 bytes
After running the extracting the file will require 2 blocks on the device
CommandNum = 5
CommandWriteSystemFile:
FileLocation = C:\Users\kdriessens\.SLImageCreator\projects\customBoard1\sl_fs\sys\mode.cfg.bin
FileSystemName = 0
File max size is 80 bytes, actual size 80 bytes
After running the extracting the file will require 2 blocks on the device
CommandNum = 6
CommandWriteSystemFile:
FileLocation = C:\Users\kdriessens\.SLImageCreator\projects\customBoard1\sl_fs\sys\sta.cfg.bin
FileSystemName = 12
File max size is 116 bytes, actual size 116 bytes
After running the extracting the file will require 2 blocks on the device
CommandNum = 7
CommandWriteSystemFile:
FileLocation = C:\Users\kdriessens\.SLImageCreator\projects\customBoard1\sl_fs\sys\dhcpsrv.cfg.bin
FileSystemName = 3
File max size is 12 bytes, actual size 12 bytes
After running the extracting the file will require 2 blocks on the device
CommandNum = 8
CommandWriteFile:
FileLocation = ../files\tmp.tmp
FileSystemName = @@.tmp
File max size is 255 bytes, actual size 0 bytes
After running the extracting the file will require 1 blocks on the device
CommandNum = 9
CommandWriteFile:
FileLocation = ../files\CrashMiniDump.bin
FileSystemName = /tmp/CrashMiniDump.bin
File max size is 24576 bytes, actual size 1 bytes
After running the extracting the file will require 7 blocks on the device
For Set Number = 0 ,
Set Files will require 24 blocks on the device after running the extraction ( Programming image is not included )
------------------------
The actual size of the image data is 9728 bytes
=> The image data requires minimum of 4 blocks on the device.
Block size is 4096 bytes.
Configured Storage size is 1024 blocks.
Total size of image( 4 blocks )
Total size of user files after extraction( 8 blocks )
Total size of FileSystem( 4 blocks )
Total System files after extraction(includes reserved space for system files)( 40 blocks )
Total reserved for system files ( 40 blocks )
Service pack after extraction size ( 0 blocks )
Application code after extraction size ( 0 blocks )
Kept for system files ( 32 blocks )
System files after extraction size (includes the service-pack) ( 16 blocks )
Reserved size for the Image (includes image protecting) ( 32 blocks )
==> After the extraction the set will require total size of 84 blocks.<==
==> During the extraction process the set will require total size of 84 blocks.<==
Non-encrypted files generated successfully !!!
Finished successfully !!!!
The products are available in : [c:\ti\uniflash_4.1\simplelink\gen2\bin\C:\Users\kdriessens\.SLImageCreator\projects\customBoard1\sl_image\Output ]
------------------------
INFO:slbootloader.slbootloader:Received error : error number = -10317 , extended error = 4071
Traceback (most recent call last):
File "<string>", line 2611, in <module>
File "<string>", line 2607, in main
File "<string>", line 2587, in cmdline
File "<string>", line 2128, in command_project_program
File "<string>", line 1079, in program_image_from_project
File "<string>", line 1186, in program_image
File "U:\slbootloader\slbootloader.py", line 766, in fs_programming
slbootloader.slbootloader.BootLoaderError: fs_programming error: ret: -10317, ex_err: 4071 - FS_ERR_FAILED_WRITE_NVMEM_HEADER
SLImageCreator returned -1
From what I understand, uniflash sees the chip (same in uniflash) but cannot program it... I've put in bold two things that look strange to me:
1. Config file not found (first line) and
2. the error itself at the end of the report.
Someone from TI (Jan Dospel, who already helped a lot) already told me that it had something to do with my SFLash. I work with the MX25R3235FM1IL0. I replaced the chip and verified all the connexions: everything seems fine.
I monitored CS, it seems to behave normally (not stuck at high or low).
I work with the XDS110 probe to connect to my board. SOP is set to 010 when working with uniflash.
I tried to program on the board an image that worked on the CC3220SF launchXL, but it failed with the same error.
I'm "reposting" my question from here with the exact error message hoping more people will see it...
Voilà... If anyone has any idea... I'll take it!
Thanks a lot in advance to anyone who will read this!
Kateline
