https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/<p style="display:none;">blank</p>en-USTelligent Community 13https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646505/lp-em-cc1354p10-inquiry-regarding-j3-external-antenna-configuration/6347815Sun, 17 May 2026 21:13:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b0af3f11-8208-4dbd-abe3-5c3db9ecafc6ZCHi Muhammad, You just need to resolder the C18 capacitor to the position of C17 in order for that RF path to be connected; nothing else is required. Regards, Zackhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646505/lp-em-cc1354p10-inquiry-regarding-j3-external-antenna-configurationSun, 17 May 2026 12:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5eef2ede-9b8d-4c99-b2db-17cea7a2efcbHUZAIFAH MAHMUDPart Number: LP-EM-CC1354P10 Dear Support Team, I am currently analyzing the RF section of the board and would like to inquire about the correct method to enable and use the J3 external antenna connector. Based on schematic and continuity measurements: The onboard antenna (A1) is functioning properly. J3 outer shell has continuity to GND. J3 center pin has continuity to the C17 footprint. J3 center pin does not have continuity to the RF line near C18/Z1. C17 is marked as DNM in the schematic. From my understanding, the current configuration appears to route RF only to the onboard antenna, while the J3 path may require additional population or reconfiguration. Could you please advise: The correct method to enable/use J3 external antenna. Whether C17 needs to be populated. The required component value/type for C17, if applicable. Whether any additional RF matching component changes are required when using J3 instead of A1. Thank you for your assistance. Best regards, Muhammad HuzaifahLP-EM-CC1354P10Wireless Infrastructurehttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/6347711Sat, 16 May 2026 07:27:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d4f333c8-ea36-4979-971d-8741ee3073b2faker wangHi Daniel: I tested the method you provided May I ask if you forgot to upload the product_util_13x0.py file? From my observation, it seems that two constants have been added to this file: 1.FLASH_NV_BASE 2.FLASH_APP_BASE Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646449/cc1354p10-executing-mass-erase-from-uniflash-cli-on-protected-cc13x4Fri, 15 May 2026 22:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a2292211-7111-4927-9bbe-3e0c136cb50aAbraham GonzalezPart Number: CC1354P10 Other Parts Discussed in Thread: UNIFLASH Working with CC1314/CC1354 parts I&#39;m writing programming scripts to Flash internal memory by using an XDS110, under normal circumstances it works fine, but at runtime the firmware enables the JTAG protection that forces a mass erase prior access. Once that protection is set Uniflash GUI will prompt me to confirm unlock/chip-erase and then work normally. But for the cli I haven&#39;t been able to do the same unlock/erase, I get the following: fatal: IcePick_C: Error connecting to the target: (Error -241 @ 0x0) A router subpath could not be accessed. A security error has probably occurred. Make sure your device is unlocked. (Emulation package 20.4.0.3756) NOTE: I got the same error -241 while testing connection in CCS. For reference, I&#39;m following this guide, made the standalone cli and except for this JTAG protection thing it works well, I can erase and program without any issues: https://software-dl.ti.com/ccs/esd/uniflash/docs/latest_qsguide.html#standalone-command-line-tool I need to get this cli fully working to facilitate our team of developers on flashing their hardware. Thanks, AbrahamUniFlashCC1354P10https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1645636/cc1310-rom-bootloader/6347201Fri, 15 May 2026 15:50:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2b85dd9d-e306-4c49-b52c-e73fdcd33ef7Arthur R☑️Hi Danilo, This probably means that DIO3 is floating, which is maybe caused by the following: CC1310: CC1310 crash issue - Sub-1 GHz forum - Sub-1 GHz - TI E2E support forums Regards, Arthurhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1645636/cc1310-rom-bootloader/6347196Fri, 15 May 2026 15:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6977ae2c-9fa5-40b5-951c-ca1a76595624Danilo A.Hi Arthur, Please see our customer&#39;s response below. Thank you for your prompt response. The CC1310F128RGZ devices we are using were purchased directly from Mouser Electronics, an authorized Texas Instruments distributor, so we are confident the flash memory is empty (factory state) and the ROM bootloader should be enabled by default. Current measurements (CC1310 powered with 3.3 V, no UART adapter connected): Supply current: ~1.7 mA Voltage at Pin 8 (DIO_3 / bootloader UART TX): &lt; 1 V Questions: Is a DIO_3 reading below 1 V normal at idle, or should DIO_3 be actively driven to 3.3 V whenever the ROM bootloader is running? Does DIO_3 require an external pull-up resistor, or is the chip&#39;s internal output driver sufficient? Could this low DIO_3 voltage be the root cause of the bootloader not responding to our UART sync attempts? Thank you again for your support. Regards, Danilohttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1640287/cc1352p-optimizing-proprf-tx-pa-time-in-a-tdma-network/6347105Fri, 15 May 2026 14:43:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ec7536ee-ca01-4401-b9ad-1efd92ab5589Mike SnyderHi Arthur. Good to see you. We touched on this in email, but good to post for the forums. We&#39;re using the BLE5 500 kbps PHY with PropRF commands. I was unable to get the ADV API&#39;s working reliably with a few hours of effort. With your help, we were able to shorten the pilot tone from 35 us to 20 us because we&#39;re not using the high power pins. We did take a stab at shortening the pre-ample and sync word, but because we&#39;re on the BLE5 PHY with PropRF commands, that did not seem possible. -Mikehttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/6346924Fri, 15 May 2026 12:18:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2f0cf6ea-b8bb-4fb4-823f-1505d2c3a596faker wangHi Daniel: Thank you, I will verify the following as soon as possible. Thank you again Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/6346923Fri, 15 May 2026 12:13:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8f9474ad-f475-4b0c-9131-52af96e7863dDaniel Guarecuco AguiarHi faker, I apologize for the delay, it took quite some work to find the issue, I appreciate your patience. Please replace the following 3 files: 1. On the Linux side, replace example/collector/collector.c There were two issues here: first, there was a wrong offset in fseek(oadFile, IMG_HDR_ADDR, SEEK_SET); it was hardcoded to 0x00 which didn&#39;t work for TIRTOS_IN_ROM. Second, sizeof(&quot;TURBOOAD&quot;) returns 9 due to the null terminator. This caused the image to be recognized as a regular OAD and not a Turbo OAD. After replacing the file, rebuild your Linux host: ./build_all.sh clean ./build_all.sh e2e.ti.com/.../4265.collector.c 2. After fixing the first part, the image was still rejected because a fail in the boundary check, so I replaced a &quot;less than&quot; with a &quot;less than or equal&quot;. After this change, rebuild your project. Since the CCS project is copying (instead of linking) from the source code, you have to replace it locally inside your project and in the SDK for future use. simplelink_cc13x0_sdk_4_20_02_07/source/ti/ti154stack/apps/sensor_oad_offchip/CC13X0_LAUNCHXL/ oad_client.c CCS project/Application/oad_client.c Now rebuild your project and generate a new .hex e2e.ti.com/.../oad_5F00_client.c 3. Finally, the image would still compute a wrong CRC because the tool was covering the NV region were the network information is stored. Update the implelink_cc13x0_sdk_4_20_02_07/tools/ti154stack/turbo_oad/toad_image_tool.py Generate a new a.bin, b.bin, ab.dim e2e.ti.com/.../toad_5F00_image_5F00_tool.py Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1640287/cc1352p-optimizing-proprf-tx-pa-time-in-a-tdma-network/6346871Fri, 15 May 2026 10:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a496db74-239e-4cd1-98f3-644e87366cf3Arthur R☑️Hi MIke, Are you using the BLE5 commands, like ADV in such, or are you using the PropRF api? Regards, Arthurhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646250/cc1352p-ti-synchronous-serial-interface-example/6346869Fri, 15 May 2026 10:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ea1c7aa7-0843-450b-9bbb-c34eb17d63d3Arthur R☑️Hi Jacky, This is our example for the CC1352P: i2ctmp Regards, Arthurhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1645763/cc1354p10-standard-dmm-samples-not-working-for-cc1354p10-dev-kit-on-sub-ghz/6346760Fri, 15 May 2026 09:31:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b1b370fa-3a21-4550-ae7b-5ec80d69e5ceBrenton ChettyHi Arthur, I did not make any changes to get the DMM working. I used the collector sample on 1 dev kit and the dmm_154sensor_remote_display_app sample on another CC1354P10 dev kit. I used SDK 7.41 as you suggested. It did not work on first attempt; but only works when I reset the board with DMM Sample. I verified that the BLE and 802.15.4 sensor works correctly on the dev kit, i.e. I can toggle LEDS on both sensor and collector. Regards Brentonhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646250/cc1352p-ti-synchronous-serial-interface-exampleFri, 15 May 2026 08:47:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:bdff89f4-699b-4a2a-a2bd-095f8c88e507Jacky HungPart Number: CC1352P Hi Sirs, I need implement TI Synchronous serial interface protocol. Could you help recmmend related SDK example ? Thanks Jacky~Wired networkingCC1352Phttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1645763/cc1354p10-standard-dmm-samples-not-working-for-cc1354p10-dev-kit-on-sub-ghz/6346676Fri, 15 May 2026 08:35:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e0b78eab-3cfe-43f5-b801-d1f0e57f3e7dArthur R☑️Hi Brenton, Did you change anything to make them work? As to the other query, it should be possible by mostly following this guide: DMM Integration , but by applying 15.4 specific modifications instead of BLE ones of course. Regards, Arthurhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1645267/lp-cc1312r7-interference-packet-received-when-wi-sun-mode/6346646Fri, 15 May 2026 08:14:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:45dac942-36a8-433b-b229-42486d3c7410Arthur R☑️Hi Chun, In order to know, I would have to look at the registers from your radio settings. Can you export those from SmartRF Studo and post them here? Regards, Arthurhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646212/cc1312r-possible-how-to-implement-frequency-hopping-with-25--50-channels-and-still-meet-fcc-15-247-requirementFri, 15 May 2026 07:27:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e292debd-8692-4757-b562-b45e79de9c75Zhiyong Li (FT)Part Number: CC1312R Hi, According to application reports swra529a and swry025, CC13XX devices can be configured to be compliant with FCC 15.247 requirement by setting up certain parameters. The part that involves 50+ channels seems clear to me. We just need select more than 50 channels in channel mask and ensure transmission power is less than 30dBm. But I am not sure about hopping with 25 - 50 channels. swry025 seems to indicate that we just need to ensure transmission power is less than 24dBm, then SDK will take care of the rest. On the other hand, the text in CFR47-15.247 states that we need use 20dB bandwdith needs to be greater than 250KHz if we want to reduce hopping channels down to 25+. if the 20 dB bandwidth of the hopping channel is 250 kHz or greater, the system shall use at least 25 hopping frequencies and the average time of occupancy on any frequency shall not be greater than 0.4 seconds within a 10 second period. The maximum allowed 20 dB bandwidth of the hopping channel is 500 kHz The mesured 20dB bandwidth with default settings is 100KHz per SWRA529A. This doesn&#39;t seem to meet 15.247 requirement if we only want to hop with 25 channels. I am a bit confused here. Can someone help clarify? Btw, I believe there is a typo in SWRA529A. The marked number should be 500KHz.CC1312Rhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1645763/cc1354p10-standard-dmm-samples-not-working-for-cc1354p10-dev-kit-on-sub-ghz/6346410Fri, 15 May 2026 05:21:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ad9e99dd-5337-4e7c-b2ec-ed840f33ceb4Brenton ChettyThanks Arthur, The DMM samples now work with DMM on Sub_GHz with the CC1354P10. Do you know if it&#39;s possible to use DMM with IEEE802.15.4 alongside Proprietary_RF (Custom_RF)? Kind Regards Brentonhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/6346226Fri, 15 May 2026 01:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a244032c-4739-4a8c-8c57-92ddd8d2ca98faker wangHi Daniel: Excuse me, is there any progress Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1645763/cc1354p10-standard-dmm-samples-not-working-for-cc1354p10-dev-kit-on-sub-ghz/6345160Thu, 14 May 2026 09:58:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3dab2629-166c-4ceb-8724-636ce15bae1bArthur R☑️Hi Brenton, This is unfortunately a known issue we have been meaning to track down: LP-EM-CC1354P10: [DMM BLE + PROP] Hitting SYS/BIOS Error: Stuck in for(;;) after RF scheduling - Site support forum - Site support - TI E2E support forums The workaround for the time being is to use SDK 7.41.. Regards, Arthurhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1645636/cc1310-rom-bootloader/6345133Thu, 14 May 2026 09:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d76594b8-6f58-4969-b950-c1ed9b7bc89cArthur R☑️Hi Danilo, I assume that the customer has read https://www.ti.com/lit/an/swra466e/swra466e.pdf There are several reasons it may not work: There is already an image flashed on the CC1310, and it did not enable the bootloader backdoor pin The device&#39;s flash is not empty. The empty device will have its serial bootloader enabled when the flash is empty. Regards, Arthur