Other Parts Discussed in Thread: SEGGER, CC1350
Hi All!
We are using the cc1310 64Kbyte Flash version in our product.
The production flashing would be done via the J-Flash through J-Link Base from Segger.
Is there any advised way to know when the flashing is performed, if the device is a 64KiB version, or a 128KiB version of the cc1310?
Normally this would not matter, if the flash was bigger, but as the ccfg section is supposed to be located in the last page, flashing the executable of a 64KiB into a 128KiB will make it not execute its code correctly.
In the J-Flash only thing I can do is to check for the core ID
But basically this means it just checks for the cortex core.
Obviously if wrong cc1310 were sourced, with 128KiB, it would be found at the final verification testing in the production, but it would be great if a false cc1310 would be caught just when the flashing takes place.
For Atmel devices for example every device has its own ID, see post:
So I was wondering how would one do a check for this?
I was looking at the SmartRF Flash Programmer 2 ver. 1.8.2. The gui seems to know which chip is attached.
But in the console, if I tell it to erase the device cc1350, which is false, because I have actually connected a cc1310F128, it won't complain, it just erases it without checking:
If I would try to program, whilst defining a false device, it would also not complain.
Oddly enough, the device_inof.xml contains entries about devices like CC1310F128, CC1310F64, CC1310F32,
but using these in the command does not yield any valid result:
So it seems I can not target a specific device from the command line of SmartRF Flash Programmer.
Also I have noticed, that the xml file is incomplete for the cc1310f128 device, whereas the flash size information and many more is missing.
Can anyone help about how a production programming is supposed to happen?
Any pointers would be appreciated.
Thanks!





