CCS/CC3220SF-LAUNCHXL: Is J-Link support not available for CC3220SF12ARGKT?

Hello, Shlomi. Before closing this, I wish to check one thing.

Shlomi Itzhak said:

The device needs to be connected to a serial flash where the application code is storred (and loaded to the internal flash for execution).

You mean, the J-Link is only used for debugging, not for flashing the application code in the internal flash memory, right?

I thought the wrong way; I guessed that the internal flash memory would get rid of the "Uniflash" hassle. When creating custom PCBs with the CC3200, I had to use the FTDI module for flashing the application. I thought this would be over when I use the CC3220SF. Anyways, thanks for your reply.

Thanks, Shlomi. I should have read the datasheet with cautious.

Shlomi Itzhak said:

This is mainly for the secured device feature where upon each initialization

Looks like you are mentioning the below explanation from the datasheet.

BOM: U8 CMOS FLASH MEMORY MX25R3235FM1IL0

Wi-Fi Network Processor (NWP) Subsystem, Table 5-1 describes the NWP features.
The CC3220S and CC3220SF variants also support Secure Boot: Validate the integrity and authenticity of the run-time binary during boot

The Cortex-M4 application processor runs the user application loaded from an external serial flash,

or internal flash (in CC3220SF). The networking subsystem runs preprogrammed TCP/IP and Wi-Fi data link layer functions.

The CC3220SF device comes with an on-chip flash memory of 1MB that allows application code to execute in place while freeing SRAM exclusively for read-write data.

The flash memory is used for code and constant data sections and is directly attached to the ICODE/DCODE bus of the Cortex-M4 core.

The CC3220SF device includes application-dedicated 1MB of XIP (Execute in place) flash and 256KB of RAM for code and data,

ROM with external serial flash bootloader, and peripheral drivers.

The CC3220S and CC3220SF device options have additional security features, such as encrypted and authenticated file systems,

user IP encryption and authentication, secured boot (authentication and integrity validation of the application image at flash and boot time), and more.

Memory Map, Table 5-5
0x0000 0000 ~ 0x0007 FFFF: On-chip ROM (bootloader + DriverLib)
0x0100 0000 ~ 0x010F FFFF: On-chip flash (for user application code, CC3220FS device only)

External Memory Requirements - The CC3220x device maintains a proprietary file system on the sFLASH.

The CC3220x file system stores the MCU binary, service pack file, system files, configuration files, certificate files, web page files, and user files.

Thanks for your reply. Silly me, I thought the serial memory will be gone due to the internal flash.

P.S) I hope to see the day when I hear TI's new Wi-Fi MCU that doesn't need an external flash by adding a large internal flash or other methods.