CC3501E: EE3501E

Hi Peter,

I have a few clarification questions:

Was the vendor authentication successful? Only when trying the factory programming was there an error? Can you please share what error exactly came up? I don't see any error in the log you sent in the thread. 

As for the CCS debug attempt, did you follow all of documentation from the CC35xxE SDK about correct CCS setup? 

Regards,

Jonathan  

Hi Jonathan,

Thanks for replying. I was rush so forward the messages using my phone. Please find the detailed infromations.

We have a prototype board which has CC3501E on it. Instead of using IS25WJ032F, we have MX25R1635F as the flash chip for CC3501E. Please find the datasheet of MX25R1635F attached, also in the link:

We tried to activate the muc using the Vendor Authentication Bypass option. The activation was successful but the MCU is recognized as CC3561. Please find the device info. LP-XDS110ET was used.

After the MCU is activated, I tried to run "Factory Programming". After a few seconds, I got and error as shown here:

2025-02-11 20:30:00,323: Searching for free port ...
2025-02-11 20:30:00,324: Free port found at 7777
2025-02-11 20:30:00,348: Starting WebServer...
2025-02-11 20:30:00,367: Serving on http://127.0.0.1:7777
2025-02-11 20:30:01,361: Starting UI ...
2025-02-11 20:30:24,299: Programmer Version : 1.0.0-prog
connection_info_data post: {'interfaceType': 'XDS110', 'serialNumber': 'LS42086P', 'deviceFamily': ''}
interface: XDS110, sn: LS42086P
2025-02-11 20:30:30,742: Reading binary file: C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\images\tbl.sign.bin
2025-02-11 20:30:30,793: Loading binary using bulk function
2025-02-11 20:30:36,661: Writing binary size of 97956 bytes within 5.918709200000002 sec
2025-02-11 20:30:36,664: Successfully loaded binary
2025-02-11 20:30:37,427: Programmer Version : 1.0.0-prog
interface: XDS110, sn: LS42086P
2025-02-11 20:30:38,469: Reading binary file: C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\images\tbl.sign.bin
2025-02-11 20:30:38,488: Loading binary using bulk function
2025-02-11 20:30:44,344: Writing binary size of 97956 bytes within 5.875332499999999 sec
2025-02-11 20:30:44,345: Successfully loaded binary
2025-02-11 20:42:20,858: Saved vendor flash image with dummy signature bin file at C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\vendor_flash_image.unsign.bin
2025-02-11 20:42:20,860: Saved part of vendor flash image bin file to sign at C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\vendor_flash_image.forsign.bin
2025-02-11 20:42:20,907: Saved sign vendor image bin file at C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\vendor_flash_image.sign.bin
2025-02-11 20:42:20,915: Saved dssm request bin file at C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\dssm_req_programming.unsign.bin
2025-02-11 20:42:20,916: Saved dssm request to sign bin file at C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\dssm_req_programming.forsign.bin
2025-02-11 20:42:20,925: Saved sign dssm request bin file at C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\dssm_req_programming.sign.bin
2025-02-11 20:42:20,928: Saved TI Flash image GPE bin file at C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\ti_flash_image.bin
2025-02-11 20:42:20,939: Saved boot sector image bin file at C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\boot_sector_image.bin
2025-02-11 20:42:32,282: Reading binary file: C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\images\tbl.sign.bin
2025-02-11 20:42:32,308: Loading binary using bulk function
2025-02-11 20:42:38,176: Writing binary size of 97956 bytes within 5.893612599999983 sec
2025-02-11 20:42:38,659: Reading binary file: C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\dssm_req_programming.sign.bin
2025-02-11 20:42:38,662: Loading binary using bulk function
2025-02-11 20:42:38,895: Writing binary size of 240 bytes within 0.23531289999993987 sec
2025-02-11 20:42:39,017: Reading binary file: C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\flash_n_fuse_prog_inst_image.sign.bin
2025-02-11 20:42:39,020: Loading binary using bulk function
2025-02-11 20:42:39,314: Writing binary size of 1300 bytes within 0.2976618000000144 sec
2025-02-11 20:42:39,836: Reading binary file: C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\header_boot_sector_image.flashready.bin
2025-02-11 20:42:39,837: Loading binary using bulk function
2025-02-11 20:42:40,055: Writing binary size of 12 bytes within 0.2190175000000636 sec
2025-02-11 20:42:40,577: Reading binary file: C:\ti\simplelink_wifi_toolbox_win_3_0_10_ea\programmer\activation_and_initial_programming\tmp\content_boot_sector_image.flashready.bin
2025-02-11 20:42:40,580: Loading binary using bulk function
2025-02-11 20:42:42,252: Download process failed.
Error message: Last operation <function PyXds110._secap_bulk_write at 0x00000226FC357E50> return error code -1141 stopping process
2025-02-11 20:42:42,254: Failed load binary with error code: -1141
Error message: Last operation <function PyXds110._secap_bulk_write at 0x00000226FC357E50> return error code -1141 stopping process

I wonder if the error is caused by the flash chip on our board.

Regarding CCS, I should have followed all the documents. I am using CCS 20.0.1.4.

Cheers,

Peter

MX25R1635F, Wide Range, 16Mb, v1.6.pdf

Hi Peter,

I checked with our R&D, and it looks like the reason its not working is because of the flash. The only external flash that the SDK supports right now is IS25WJ032F-JNLE as used in our evaluation board. Support for additional flashes in software will be supported in future releases. 

Regards,

Jonathan