CC3230SF: external flash size increase from 4MB to 8MB

Thanks, Jan D.Please check the schematic of the external flash and check if it's ok. If you need the full MCU schematic, please let me know. 

The part used is GD25WQ64ESIGR as given in the document you sent. 

my.mouser.com/.../GD25WQ64ESIGR

Hi,

Sorry, but I don't have time to fully check datasheet of this memory. This is up to you or maybe you can wait for answer from TI support.

Jan

Can you check attached external flash schematic only ? That's enough. 

Hi,

Sorry, without studding datasheet from flash I can't if connection is correct (e.g. I don't know how works pins WP and HOLD at this particular flash memory). I don't want to be responsible to providing you not right answer.

Jan

Ok, I will wait for another Expert to help me. 

thank you so much

Hi,

Just a one reminder. Do you use vendor authentication? If so, be aware that this gigadevice flash is likely not supported for vendor authentication.

Jan

hi Jan D,

Are you saying that Gigadevice dont have TI vendor authentication? Only saw one 64 Megabit flash. If you have another 64 Megabit flash, please propose. 

Hi,

Vendor authentication, as is described here, was designed/validated with MX25R3235FM1IH0 only. Maybe if exist bigger memory from Macronix (MX25R6435F?) at same family I suppose it may to work. But I am not searched if such flash chip exist. Maybe you can wait for confirmation from TI side.

Jan

hi Jan D,

I found a 64 MegaBit flash memory from Macronix. The part number is MX25R6435FM2IL0. I made sure every spec, including clock frequency, matches MX25R3235FM1IL0, MX25R3235FM1IL0 is a TI-approved part. Can I use MX25R6435FM2IL0? for datasheet, please refer to the link below. 

www.digikey.com/.../5702224

Hi,

I have not validated this flash chip that means I can confirm that. But is seems at e2e forum some other users successfully used MX25R6435. But vendor authentication you will likely need to validate by yourself. Use your hardware, swap sFlash and test it by yourself. This is best advice which I can give you.

Jan

hi Jan D ,

Can I say that you recommend MX25R6435FM2IL0, but you're not sure if it has vendor authentication? meaning MX25R6435FM2IL0 will work but may have problem for OTA and MQTT access without vendor authentication? 

Hi,

No. This is not my recommendation. I say that best chance for compatible SPI flash if you are using vendor authentication is SPI flash from same family as MX25R3235. MX25R6435 is from same family but with higher capacity. Important part for compatibility with vendor authentication is OTP part inside SPI flash. It seems that MX25R6435 have OTP part similarly working as MX25R3235. But without validation at my side I can't recommand you anything.

Vendor authentication is used for safe boot. CC32xx are safe devices. For development purpose you can use device at development mode with TI playground certificates. But for shipment to end-users you should to use device at production mode. And here are two options. You can buy code signing certificate from supported CA in certificate catalogue or as alternative you can use own self-signed certificate for safe boot with vendor authentication feature (as described at document linked above).

Jan

hi Jan D , 

MX25R6435 is better than GD25WQ64ESIGR, is what you saying correct? Thank you so much.I know you cannot confirm MX25R6435 working since you didn't test it. 

I will wait for someone who has tested MX25R6435 to confirm if it will work.

BR

pragash

Hi pragash,

I think if you are using vendor authentication is better chance for compatible flash MX25R6435. If you are not using vendor authentication that better flash is up to your preferences (price, power consumption, erases speed, availability...).

Jan

Hi Jan D,

We are using vendor authentication for OTA (over-the-air software update) and WiFi MQTT, so that I will use MX25R6435. In the meantime, I appreciate anyone who has used MX25R6435 can comment on OTA and WiFi MQTT performance. 

Hi,

It seems you are not understanding what vendor authentication is. Please read that document. Vendor authentication is not about validating certificate chain pro TSL sockets.

Jan

hi Jan D,

i dont think im wrong. The very 1st line in the document you sent sounds

" The SimpleLink Wi-Fi® Internet-on-a chip family of devices from Texas Instruments provides a suite of integrated protocols for Wi-Fi® and internet connectivity to simplify the implementation of internetenabled devices and applications." 

MQTT is internet connectivity. 

Hi,

If, you think... It's your choice do not follow my advice(s).

Last question what certificate do you use for code signing? It is your own self signed certificate with own certificate catalogue programmed by Uniflash into OTP part of SPI flash?

Jan

Jan D ,

So you're going to deny that the document is not talking about internet access? The problem is that you are only advising me to read, providing no other definitive answer, except to select a part from the same vendor! 

We are not using OTP. We are not programming OTP. We are only using the catalog provided by TI to sign our certificate. 

Hi,

That sentence is just a "marketing" description of CC32xx devices. Nothing less, nothing more. You will find same sentence at almost all manuals for CC32xx devices.

If you are not using preprogramed vendor catalogue into OTP  part of SPI flash that means you are not using vendor authentication. If you don't want to use vendor authentication, you will need to buy code signing certificate from one of supported CA. Because shipment CC32xx devices at development mode to end-users is very bad idea.

Jan

Hi Jan D,

Is vendor authentication required to verify the authenticity of SPI flash?

Hi,

Vendor authentication does not authenticate SPI flash. Vendor authentication is one of options for safe boot of CC32xx device at production mode.

Jan

hi Jan D,

I have a stupid question. Why is a safe boot needed for production devices? 

Hi,

Because at development mode device is not secured and content of SPI flash can be read by Uniflash via UART and JTAG is not locked (content of on-chip XIP flash can be read by JTAG). Image with firmware is tided to MAC address of each particular CC32xx chip. And this is pretty impractical for production.

Btw ... why you need bigger flash? I hope that you don't want to use SPI flash for datalogging purpose.

Jan

Jan D,

Our code consumes 80% of 4MB since we have many hardware components like sensors on the PCB. That's why 8MB flash is not an option, but a must for us. 

we are adding more and more features so 4MB needs to be changed to 8MB.