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/1649152/cc1311p3-cc1311p3-clarification-on-narrowband-mode-impact-on-tx-occupied-bandwidth-obw/6365924Mon, 01 Jun 2026 15:32:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4e177918-9a87-4b90-a937-4359ba1b2cfbDiego P[quote userid=&quot;608027&quot; url=&quot;~/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649152/cc1311p3-cc1311p3-clarification-on-narrowband-mode-impact-on-tx-occupied-bandwidth-obw&quot;]Does Narrowband Mode alter any of the following internally? Tx pulse shaping/filtering Modulation shaping Frequency deviation scaling Demodulator bandwidth IF/Rx filtering [/quote] The narrowband setting doesn&#39;t alter those settings. It allows the radio to set higher resolution RF frequencies. [quote userid=&quot;608027&quot; url=&quot;~/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649152/cc1311p3-cc1311p3-clarification-on-narrowband-mode-impact-on-tx-occupied-bandwidth-obw&quot;]For achieving minimum OBW while maintaining good sensitivity and demodulation robustness in a 25 kHz channel, would TI recommend enabling or disabling Narrowband Mode for this PHY?[/quote] For OBW &lt;= 25 kHz the narrowband setting is recommended. Can you share a plot with the issues you are seeing?https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646641/cc1311p3-cc1311p3-unable-to-decode-2-fsk-signal-at-19-2-ksps-with-2-khz-deviation/6365624Mon, 01 Jun 2026 11:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5a8e0e3d-64db-4858-a016-50dfc44c72b2Daniel Guarecuco AguiarHi Theiv, I suspect there might be a race condition, in your callback you set &#39;currentReadEntry-&gt;status = DATA_ENTRY_PENDING&#39; before the task has read the data. So the RF core is free to overwrite that entry. Are you calling UART_write passing the pointer directly to currentReadEntry-&gt;data or a separate copied buffer? What is rf_ctrl_pck_data_hdr doing ? Can you try something like this: copy the data into another buffer before setting PENDING void ReceivedOnRFcallback(RF_Handle h, RF_CmdHandle ch, RF_EventMask e) { if (e &amp; RF_EventRxEntryDone) { /* Copy data BEFORE freeing entry to RF core */ memcpy(uartTxBuffer, currentReadEntry-&gt;data, DATA_BUFFER_SIZE); /* Now safe to free entry */ currentReadEntry-&gt;status = DATA_ENTRY_PENDING; currentReadEntry = (rfc_dataEntryPartial_t*)currentReadEntry-&gt;pNextEntry; packet_RXCB == TRUE } } Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649628/cc1312r-1ma-generation-in-standby-mode/6365593Mon, 01 Jun 2026 11:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:70698c8d-e32f-4799-b1c2-6d5f1c4c1075Daniel Guarecuco AguiarHi Shingo, Once you reach 1mA. 1. Can you post a screenshot of the call stack when you pause the debugger. 2. Can you also export all the registers. Go to View -&gt; Register. Make sure the registers have updated and click on the arrow button, export all registers to a JSON file and upload them here. Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646641/cc1311p3-cc1311p3-unable-to-decode-2-fsk-signal-at-19-2-ksps-with-2-khz-deviation/6365540Mon, 01 Jun 2026 10:37:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2dca1017-06f5-4307-9a7e-d2504bec75a0Theiv Byes daniel, could you please deep dive into our sequence &amp; settings and let&#39;s know what could be the reason for intermittent data loss using partial read mechanism ? Thanks, Theiv Bhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646641/cc1311p3-cc1311p3-unable-to-decode-2-fsk-signal-at-19-2-ksps-with-2-khz-deviation/6365523Mon, 01 Jun 2026 10:22:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ff642ce0-3d08-40ea-98f5-dcafd700aedaDaniel Guarecuco AguiarHi Theiv, So have you tested the same PHY settings and they work? So is the issue with the partial buffer implementation? Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646641/cc1311p3-cc1311p3-unable-to-decode-2-fsk-signal-at-19-2-ksps-with-2-khz-deviation/6365442Mon, 01 Jun 2026 09:12:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d4f0e2af-0b4d-4e22-b69c-bac3b108a676Theiv BHI Daniel/RGW, Any update on my follow up response ?https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649152/cc1311p3-cc1311p3-clarification-on-narrowband-mode-impact-on-tx-occupied-bandwidth-obw/6365441Mon, 01 Jun 2026 09:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6a487adf-b5a1-43d2-8ded-f6dfdf8a8ef2Theiv BHi Diego, Any update on my follow up response ? Thanks, Theiv Bhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649628/cc1312r-1ma-generation-in-standby-mode/6364957Mon, 01 Jun 2026 00:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:25cfb4c8-c42d-421b-8ffa-3f86eb911ea5shingo sezakiI was told that the device&#39;s current consumption wouldn&#39;t return to normal without a reset, but I found that it returns to normal after about 2.5 to 3 hours, so I posted about it in the thread. I suspect the device is experiencing some kind of malfunction, but it hasn&#39;t fallen into any of the states mentioned as examples (nmi, fault). The application is running correctly.https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1645055/cc1125-cc1125-sleep-current-rises-to-2ma/6364922Sun, 31 May 2026 14:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4c70a98b-fb74-40f8-b821-bbd37ffa4516TheGhostOfAn undefined input cause random current consumption, in this case you have to define the signals that are inputs to the CC1125.https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649628/cc1312r-1ma-generation-in-standby-mode/6364407Fri, 29 May 2026 16:47:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2ed42a92-1ef2-4654-bd4e-1ca1b4f30a9cDaniel Guarecuco AguiarHi shingo, Thanks for the additional details. You said in the other thread that only a reset returns the device to the expected current consumption. I wonder if the device is trapped in a fault, like one of these static void nmiISR(void) { while (1) {} } static void faultISR(void) { while (1) {} } static void intDefaultHandler() { while (1) {} } Can run your device until you see the 1mA in the multimeter, then connect the XDS110 debugger and start a CCS project-less debug session, without resetting the device. Suspend the debug session and check the call stack. Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649152/cc1311p3-cc1311p3-clarification-on-narrowband-mode-impact-on-tx-occupied-bandwidth-obw/6364155Fri, 29 May 2026 13:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:153ce68e-7d3d-441b-bd0a-f08b6292173fTheiv Byes, I am referrring bSynthNarrowBand which is under RF_cmdPropRadioDivSetup CFG .config.bSynthNarrowBand Thanks, Theiv Bhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1643706/cc1310-communication-evaluation-using-launchxl-cc1310/6364043Fri, 29 May 2026 12:18:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b1fdc78e-5751-437d-8ff6-1209d38e7f16Diego PHi Yutaka, do you have more information on the PHY you would like to use in this frequency range?https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649152/cc1311p3-cc1311p3-clarification-on-narrowband-mode-impact-on-tx-occupied-bandwidth-obw/6364041Fri, 29 May 2026 12:17:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7ce59b15-ec45-4a06-9f10-f886a3823107Diego PHi Theiv, By &quot; Narrowband Mode&quot; are you referring to the bit called bSynthNarrowBand CMD_PROP_RADIO_DIV_SETUP. If that is the case this bit allows the modem to set higher resolution PLL frequencies. Setting the bSynthNarrowBand bit is recommend for PHYs with a OBW at or below 25 kHz. [quote userid=&quot;608027&quot; url=&quot;~/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649152/cc1311p3-cc1311p3-clarification-on-narrowband-mode-impact-on-tx-occupied-bandwidth-obw&quot;]We observed that enabling Narrowband Mode increases the measured Occupied Bandwidth (OBW) at the transmitter output. Could you please explain why this occurs?[/quote] Could you share a spectrum plot with your observations? Before answering the rest of your questions could you confirm that you are referring to bSynthNarrowBand if not could you point me to the setting you are referring to.https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649883/cc1352r-how-to-program-a-cc1352r-using-serial-bootloader/6364031Fri, 29 May 2026 12:04:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:fac85480-8564-434e-9173-b9e0e3fdaeb9Daniel Guarecuco AguiarHi Bill, Good to hear! IMAGE_VALID_CONF is the address of the vector table and should most likely be 0x00000000. The CCFG register values are defined in Chapter 10 of the Technical Reference Manual: CC13x2, CC26x2 SimpleLink Wireless MCU Technical Reference Manual (Rev. G) You can add the following as a post-build step in you Project Properties &gt; Build &gt; Steps, to generate a .bin you can flash with the SblAppEx tool with https://www.ti.com/lit/an/swra466e/swra466e.pdf ${CG_TOOL_ROOT}/bin/tiarmobjcopy -O ihex ${BuildArtifactFileName} ${BuildArtifactFileBaseName}.hex ${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin ${BuildArtifactFileName} ${BuildArtifactFileBaseName}.bin ${CG_TOOL_ROOT}/bin/tiarmofd ${CG_TOOL_ROOT}/bin/tiarmhex ${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1650530/smartrf-studio-7-can-i-use-smart-rf-studio-with-my-target-system/6364020Fri, 29 May 2026 11:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:33462d86-144e-4e85-86c6-504304b949e5Gullik WebjornThanks Daniel, Perfect, I will test this out. Gullikhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646641/cc1311p3-cc1311p3-unable-to-decode-2-fsk-signal-at-19-2-ksps-with-2-khz-deviation/6363970Fri, 29 May 2026 10:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4ae4e1e1-f57a-40ec-a925-f35d3f66d425Theiv BHi Daniel, Yes, we are using customer board. We have done basic sanity with example project then moved to our custom project with partial read mechanism. // RF customer configuration for your reference rfc_CMD_PROP_RADIO_DIV_SETUP_PA_t RF_cmdPropRadioDivSetup_cst_above_430 = { .commandNo = 0x3807, .status = 0x0000, .pNextOp = 0, .startTime = 0x00000000, .startTrigger.triggerType = 0x0, .startTrigger.bEnaCmd = 0x0, .startTrigger.triggerNo = 0x0, .startTrigger.pastTrig = 0x0, .condition.rule = 0x1,//0x0,//0x1, .condition.nSkip = 0x0, .modulation.modType = 0x0, .modulation.deviation = 0x13, .modulation.deviationStepSz = 0x0, .symbolRate.preScale = 0xF, .symbolRate.rateWord = 0x3127,//0x3127,//0xC4A .symbolRate.decimMode = 0x0, .rxBw = 0x4B, .preamConf.nPreamBytes = 0x0,//0x4,//0x0, .preamConf.preamMode = 0x0, .formatConf.nSwBits = 0x20, .formatConf.bBitReversal = 0x1, .formatConf.bMsbFirst = 0x0, .formatConf.fecMode = 0x0, .formatConf.whitenMode = 0x0, .config.frontEndMode = 0x0, .config.biasMode = 0x1, .config.analogCfgMode = 0x0, .config.bNoFsPowerUp = 0x0, .config.bSynthNarrowBand = 0x0, // Setting NarrowBand as 0 specifies operating freq range above 430MHz .txPower = 0x003F, .pRegOverride = pOverrides_cst_above_430, .centerFreq = 0x01C8, .intFreq = 0x8000, .loDivider = 0x0A, .pRegOverrideTxStd = 0, .pRegOverrideTx20 = 0 }; rfc_CMD_PROP_RX_ADV_t RF_cmdPropRxAdv_cst = { .commandNo = 0x3804, .status = 0x0000, .pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&amp;xxx .startTime = 0x00000000, .startTrigger.triggerType = 0x0, .startTrigger.bEnaCmd = 0x0, .startTrigger.triggerNo = 0x0, .startTrigger.pastTrig = 0x1, .condition.rule = 0x1, .condition.nSkip = 0x0, .pktConf.bFsOff = 0x0, .pktConf.bRepeatOk = 0x0, .pktConf.bRepeatNok = 0x0, .pktConf.bUseCrc = 0x0, .pktConf.bCrcIncSw = 0x0, .pktConf.bCrcIncHdr = 0x0, .pktConf.endType = 0x0, .pktConf.filterOp = 0x0, .rxConf.bAutoFlushIgnored = 0x0, .rxConf.bAutoFlushCrcErr = 0x0, .rxConf.bIncludeHdr = 0x0, .rxConf.bIncludeCrc = 0x0, .rxConf.bAppendRssi = 0x1, .rxConf.bAppendTimestamp = 0x0, .rxConf.bAppendStatus = 0x0, .syncWord0 = 0xB9E86C73 , .syncWord1 = 0xB9E86C73 , .maxPktLen = 0x0, .hdrConf.numHdrBits = 0x0, .hdrConf.lenPos = 0x0, .hdrConf.numLenBits = 0x0, .addrConf.addrType = 0x0, .addrConf.addrSize = 0x0, .addrConf.addrPos = 0x0, .addrConf.numAddr = 0x0, .lenOffset = 0x00, .endTrigger.triggerType = 0x1, .endTrigger.bEnaCmd = 0x0, .endTrigger.triggerNo = 0x3,/ .endTrigger.pastTrig = 0x0,//0x0,//0x1, .endTime = 0x00000000, .pAddr = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&amp;xxx .pQueue = 0, // INSERT APPLICABLE POINTER: (dataQueue_t*)&amp;xxx .pOutput = 0 // INSERT APPLICABLE POINTER: (uint8_t*)&amp;xxx }; // RF partial read initi packetRxCb = NO_PACKET; /* Initialise the RF core params */ RF_Params_init(&amp;rfParams); /* Partial read buffer initialization */ partialReadEntry1-&gt;length = DATA_BUFFER_SIZE + 4; partialReadEntry1-&gt;config.type = DATA_ENTRY_TYPE_PARTIAL; partialReadEntry1-&gt;status = DATA_ENTRY_PENDING; partialReadEntry1-&gt;config.lenSz = 0; // No length indicator byte in data partialReadEntry1-&gt;config.irqIntv = 0; partialReadEntry2-&gt;length = DATA_BUFFER_SIZE + 4; partialReadEntry2-&gt;config.type = DATA_ENTRY_TYPE_PARTIAL; partialReadEntry2-&gt;status = DATA_ENTRY_PENDING; partialReadEntry2-&gt;config.lenSz = 0; // No length indicator byte in data partialReadEntry2-&gt;config.irqIntv = 0; partialReadEntry1-&gt;pNextEntry = (uint8_t*)partialReadEntry2; partialReadEntry2-&gt;pNextEntry = (uint8_t*)partialReadEntry1; dataQueue.pCurrEntry = (uint8_t*)partialReadEntry1; dataQueue.pLastEntry = NULL; /* RX ADV command init &amp; set to unlimited length mode */ RF_cmdPropRxAdv_cst.pQueue = &amp;dataQueue; RF_cmdPropRxAdv_cst.maxPktLen = 0; RF_cmdPropRxAdv_cst.pktConf.bRepeatOk = 1; RF_cmdPropRxAdv_cst.pktConf.bRepeatNok = 1; // UART &amp; WDT enable /* Initialize UART with callback read mode */ UART2_Params_init(&amp;uartParams); uartParams.baudRate = 1000000; uartParams.readMode = UART2_Mode_CALLBACK; uartParams.readCallback = ReceiveonUARTcallback; uartParams.readReturnMode = UART2_ReadReturnMode_PARTIAL; uartParams.writeMode = UART2_Mode_CALLBACK; uartParams.writeCallback = uart_tx_callback; Watchdog_Params params; Watchdog_init(); Watchdog_Params_init(&amp;params); params.resetMode = Watchdog_RESET_ON; params.debugStallMode = Watchdog_DEBUG_STALL_ON; params.callbackFxn = watchdog_callback; watchdogHandle = Watchdog_open(CONFIG_WATCHDOG_0, &amp;params); if(watchdogHandle == NULL) { while(1); } uint32_t ticks = Watchdog_convertMsToTicks(watchdogHandle,3000); Watchdog_setReload(watchdogHandle, ticks); // RF core open sequence /* Request access to the radio */ rfHandle = RF_open(&amp;rfObject, &amp;RF_prop_cst, (RF_RadioSetup*)&amp;RF_cmdPropRadioDivSetup_cst_above_430, &amp;rfParams); /* Set the frequency */ RF_postCmd(rfHandle, (RF_Op*)&amp;RF_cmdFs_cst, RF_PriorityNormal, NULL, 0); /* Trigger the RX command */ rfPostHandle = RF_postCmd(rfHandle, (RF_Op*)&amp;RF_cmdPropRxAdv_cst, RF_PriorityHigh, &amp;ReceivedOnRFcallback, RF_EventRxEntryDone); // RF read entry INTR service #define DATA_BUFFER_SIZE 55 void ReceivedOnRFcallback(RF_Handle h, RF_CmdHandle ch, RF_EventMask e) { if (e &amp; RF_EventRxEntryDone) { //do { #ifdef UHF_TIME_PROFILING GPIO_setDio(22); #endif swip_counter++; // Get a pointer to the first byte packetDataPointer = &amp;currentReadEntry-&gt;rxData; //--------------------------------------------------------------------------- // Implement code for handling the incoming data // . // . // . // . //--------------------------------------------------------------------------- /* Handle the packet data, located at &amp;currentDataEntry-&gt;data: * - Data starts from the first byte */ packetLength = DATA_BUFFER_SIZE+1; /* Add the header info on received packet */ /* Store the updated packet info at circular buffer */ uint8_t store_data_sts = rf_ctrl_pck_data_hdr(packetDataPointer, packetLength); uint32_t cmdStatus = ((volatile RF_Op*)&amp;RF_cmdPropRxAdv_cst)-&gt;status; switch(cmdStatus) { case PROP_DONE_OK: // Packet transmitted successfully RF_ok++; break; case PROP_DONE_STOPPED: // Received CMD_STOP while transmitting packet and finished // transmitting packet break; case PROP_DONE_ABORT: // Received CMD_ABORT while transmitting packet break; case PROP_ERROR_PAR: //0x3800 // Observed illegal parameter in the posted RF command break; case PROP_ERROR_RXBUF: //0x3801 //No RX Buffer break; case PROP_ERROR_RXFULL: //0x3802 //No RX Buffer RF_error++; for(int i =0; i pNextEntry; rf_error_status[i] = currentReadEntry-&gt;status; } break; case PROP_ERROR_NO_SETUP: //0x3803 // Command sent without setting up the radio in a supported // mode using CMD_PROP_RADIO_SETUP or CMD_RADIO_SETUP break; case PROP_ERROR_NO_FS: //0x3804 // Error case. Due to CMD_FS failing during power-up, CMD_PROP_TX // could not succeed. The RF core is powered up and the synth is not running. // One possible work-around is: Ignore it and power the RF core down // manually. CMD_FS will be re-executed on the next RF core power-up. RF_yield(rfHandle); break; case PROP_ERROR_RXOVF: //0x3805 // Command sent without setting up the radio in a supported // mode using CMD_PROP_RADIO_SETUP or CMD_RADIO_SETUP break; case PROP_ERROR_TXUNF: //0x3806 // Command sent without setting up the radio in a supported // mode using CMD_PROP_RADIO_SETUP or CMD_RADIO_SETUP break; default: break; // Uncaught error event - these could come from the // pool of states defined in rf_mailbox.h } currentReadEntry-&gt;status = DATA_ENTRY_PENDING; currentReadEntry = (rfc_dataEntryPartial_t*)currentReadEntry-&gt;pNextEntry; packet_RXCB = TRUE; } // Task UART write the RF demod data while(1) { Watchdog_clear(watchdogHandle); /* Packet RX CB check */ if(packet_RXCB == TRUE) { GPIO_clearDio(6); /* Trigger the DMA */ UART_write(); --&gt; UART write /* Reset the flag */ packet_RXCB = FALSE; } let me know if anything else need from our end. Thanks, Theiv Bhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1649883/cc1352r-how-to-program-a-cc1352r-using-serial-bootloader/6363957Fri, 29 May 2026 10:30:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ffb799fe-d1d0-4965-9365-c7a43c6a9dcbBill GarlandFinally got it working. I was using UniFlash to program the board. There is an option to manually configure the CCFG which I had disabled however it did not program the CCFG. I had to resort to looking at the .hex file then manually entering the CCFG using Flash Programmer 2. All a bit of a mess but I can now make progress. I have tried to find the format of the CCFG. Is it ARM specific? Billhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1650530/smartrf-studio-7-can-i-use-smart-rf-studio-with-my-target-system/6363953Fri, 29 May 2026 10:27:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e5eb08ca-8231-42ee-b67e-fadce2300a04Daniel Guarecuco AguiarHi Gulik, Yes, that works, SmartRF Studio uses JTAG connection. If you still have the CC1312 Launchpad, you can easily test this by removing the jumpers for all pins except GND, 3V3, Reset, TMS and TCLK. Best regards, Danielhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1640478/cc1200-cc1200-receiver-parameters-lo-if-for-en300220-compliance/6363952Fri, 29 May 2026 10:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:06351491-3f3c-4d1c-a787-b36005e6b2e9Mike Wu1Hi Richard, Thank you for your feedback. To answer your questions: 1. Data Rate / Symbol Rate: We are using 55 ksps (2-FSK). This can be derived from the customer&#39;s register settings: - CC120X_SYMBOL_RATE2 = 0x96 (SRATE_E = 9, SRATE_M[19:16] = 6) - CC120X_SYMBOL_RATE1 = 0x87 - CC120X_SYMBOL_RATE0 = 0x2B Using 40 MHz reference clock, the calculation is: R_symbol = ((427819 + 2^20) * 2^9 * 40,000,000) / 2^39 = 55,000 sps (55 ksps). 2. Target Countries and Output Power: - Target: European countries (targeting EN300220 compliance for CE marking). - Operating Frequency: 865.00 MHz. - Target Output Power: 14.0 dBm max (complying with the 14.0 dBm ERP limit for the 863-870 MHz frequency band). Based on these configurations (55 ksps, 865 MHz operating frequency), we are calculating the receiver parameters for the test lab declaration. Could you please help to confirm if our previous derivation for the IF and LO are correct? - CC120X_IF_MIX_CFG = 0x18 -&gt; CMIX_CFG is 6 (positive mixing). - CC120X_CHAN_BW = 0x0F -&gt; ADC_CIC_DECFACT is 00 (Decimation Factor = 12). - Derived IF: f_IF = 40,000 kHz / (12 * 6) = 555.56 kHz. - Derived LO: f_LO = f_nom + f_IF = 865.00 MHz + 0.55556 MHz = 865.55556 MHz. For your reference, here is the full register configuration from the customer: {CC120X_IOCFG2, 0x06}, {CC120X_SYNC_CFG1, 0xA8}, {CC120X_SYNC_CFG0, 0x13}, {CC120X_DEVIATION_M, 0x68}, {CC120X_MODCFG_DEV_E, 0x0B}, {CC120X_DCFILT_CFG, 0x26}, {CC120X_PREAMBLE_CFG0, 0x8A}, {CC120X_IQIC, 0x80}, {CC120X_CHAN_BW, 0x0F}, {CC120X_MDMCFG1, 0x40}, {CC120X_MDMCFG0, 0x05}, {CC120X_SYMBOL_RATE2, 0x96}, {CC120X_SYMBOL_RATE1, 0x87}, {CC120X_SYMBOL_RATE0, 0x2B}, {CC120X_AGC_REF, 0x27}, {CC120X_AGC_CS_THR, 0x01}, {CC120X_AGC_CFG1, 0x16}, {CC120X_AGC_CFG0, 0x84}, {CC120X_FIFO_CFG, 0x00}, {CC120X_FS_CFG, 0x12}, {CC120X_PKT_CFG2, 0x00}, {CC120X_PKT_CFG0, 0x20}, {CC120X_PA_CFG1, 0x76}, {CC120X_PA_CFG0, 0x50}, {CC120X_PKT_LEN, 0xFF}, {CC120X_IF_MIX_CFG, 0x18}, {CC120X_FREQOFF_CFG, 0x22}, {CC120X_TOC_CFG, 0x03}, {CC120X_MDMCFG2, 0x00}, {CC120X_FREQ2, 0x56}, {CC120X_FREQ1, 0x80}, {CC120X_FREQ0, 0x00}, {CC120X_IF_ADC1, 0xEE}, {CC120X_IF_ADC0, 0x10}, {CC120X_FS_DIG1, 0x07}, {CC120X_FS_DIG0, 0xA5}, {CC120X_FS_CAL1, 0x40}, {CC120X_FS_CAL0, 0x0E}, {CC120X_FS_DIVTWO, 0x03}, {CC120X_FS_DSM0, 0x33}, {CC120X_FS_DVC0, 0x17}, {CC120X_FS_PFD, 0x00}, {CC120X_FS_PRE, 0x6E}, {CC120X_FS_REG_DIV_CML, 0x1C}, {CC120X_FS_SPARE, 0xAC}, {CC120X_FS_VCO0, 0xB5}, {CC120X_IFAMP, 0x0D}, {CC120X_XOSC5, 0x0E}, {CC120X_XOSC1, 0x03}, {CC120X_PARTNUMBER, 0x20}, {CC120X_PARTVERSION, 0x11}, {CC120X_MODEM_STATUS1, 0x10} We look forward to your verification. Best regards, Mikehttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1646641/cc1311p3-cc1311p3-unable-to-decode-2-fsk-signal-at-19-2-ksps-with-2-khz-deviation/6363934Fri, 29 May 2026 10:15:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:676c93d3-6124-4653-9103-236595ca5255Daniel Guarecuco AguiarHi Theiv, Can we step back a run some sanity check. Could you flash the examples rfPacketTx and rfPacketRx with a default RF setting, to validate your hardware. If everything is ok, take the exact same RF settings from the example and move them into your software implementation. Does is it still work properly? We want to understand whether the problem is in the software or the RF settings. Are you using a custom board or CC1311P3 launchpads? Best regards, Daniel