<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://e2e.ti.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sub-1 GHz forum - Recent Threads</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 24 Apr 2026 21:50:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum" /><item><title>CC1352P: optimizing propRf TX / PA time in a TDMA network</title><link>https://e2e.ti.com/thread/1640287?ContentTypeID=0</link><pubDate>Fri, 24 Apr 2026 21:50:13 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7cc0b864-a847-4cdb-a132-490675224a80</guid><dc:creator>Mike Snyder</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/1640287?ContentTypeID=0</comments><wfw:commentRss>https://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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC1352P&lt;/p&gt;&lt;p&gt;Hi!&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I&amp;#39;ve done just about all the optimization I can do with RF OP chaining and looping. I&amp;#39;m wondering if I can shave 60 us off the transmission/TX PA time measured with IOC_PORT_RFC_GPO1. I&amp;#39;m appending timestamps for receiver sync. Can I shorten the sync word or preamble? Are there any other overrides or knobs to turn? Is there some &amp;#39;dead time&amp;#39; before the transmission I can account for? I&amp;#39;m using the 500kbps BLE PHY.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>MSPM0G3507: The chip is locked and cannot be solved with Uniflash.</title><link>https://e2e.ti.com/thread/1640248?ContentTypeID=0</link><pubDate>Fri, 24 Apr 2026 16:46:29 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f752eee6-ed21-4ac6-aada-67806407d71d</guid><dc:creator>mi sj</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/1640248?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1640248/mspm0g3507-the-chip-is-locked-and-cannot-be-solved-with-uniflash/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; MSPM0G3507&lt;/p&gt;&lt;div&gt;Dear TI Technical Support Team,&lt;br /&gt;I am working on a project using the&amp;nbsp;MSPM0G3507&amp;nbsp;(80MHz Arm&amp;reg; Cortex&amp;reg;‑M0+ MCU, 128KB flash, 3&amp;times; comparator). During the development of the comparator configuration, the chip frequently became locked. Eventually the device became completely unreachable. The IDE (CCS) and debugger (XDS110) failed to connect to the target. The error messages are as follows:&lt;br /&gt;Error connecting to the target: Connection to MSPM0 core failed. Possible root causes: 1) Debug access within NONMAIN was disabled or enabled with password. 2) Peripheral mis-configuration (e.g improper watchdog or clock). To see a more detailed diagnostic of the issue, please press the &amp;#39;Read boot diagnostic&amp;#39; button. Error connecting to the target: (Error -6310) PRSC module failed to read a register. (Emulation package 20.5.0.3902)&lt;br /&gt;The complete information is in the picture.&lt;/div&gt;
&lt;div&gt;I would be most grateful if you could offer help.&lt;img src="https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/156/27d37a534d52f35543f4bd36586f96ed.PNG" alt="27d37a534d52f35543f4bd36586f96ed.PNG" data-temp-id="27d37a534d52f35543f4bd36586f96ed.PNG-289449" /&gt;&lt;/div&gt;</description></item><item><title>RE: MSPM0G3507: The chip is locked and cannot be solved with Uniflash.</title><link>https://e2e.ti.com/thread/6323175?ContentTypeID=1</link><pubDate>Fri, 24 Apr 2026 19:57:49 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d9c6f118-1ab1-4342-aecd-da800da378a4</guid><dc:creator>Brian Lee</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6323175?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1640248/mspm0g3507-the-chip-is-locked-and-cannot-be-solved-with-uniflash/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi Mi,&lt;/p&gt;
&lt;p&gt;Are you able to connect to the CS_DAP_0 core after starting a project-less debug session? If so, can you run the&amp;nbsp;&lt;span&gt;MSPM0_Mailbox_FactoryReset_Manual&amp;nbsp;script and follow the prompts in the GEL Output Console? This should unlock the device again.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If that does not work, try the&amp;nbsp;&lt;/span&gt;&lt;span&gt;MSPM0_DeviceDiagnosticRead script and view the output in the GEL Output Console.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If the device is unable to connect to the DAP, try again with the following procedure:&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span&gt;Hold NRST low&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Remove power&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Reconnect power&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Start projectless debug session&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Attempt to connect to DAP core&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Release NRST&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Attempt to run the script again&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;If the device can connect to the DAP core, but the Device Diagnostic Read returns a code 0f 0x36, the device is not recoverable. Additionally, if you are still unable to connect to the DAP, the device is also no longer recoverable.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best Regards,&lt;br /&gt;Brian&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>CC1310: Turbo OAD CRC Failed</title><link>https://e2e.ti.com/thread/1636875?ContentTypeID=0</link><pubDate>Wed, 15 Apr 2026 12:51:39 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:63a3e613-9263-4027-b5aa-cd4f42e9bc98</guid><dc:creator>faker wang</dc:creator><slash:comments>12</slash:comments><comments>https://e2e.ti.com/thread/1636875?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC1310&lt;/p&gt;&lt;p&gt;Hi guys:&lt;/p&gt;
&lt;p&gt;Example of using two CC1310 MCUs to test OAD&lt;br /&gt;SDK version: Simplelink_cc13x0usdk_4_20-02_07, ti154stack_Lux_x64_8_30_00_05&lt;/p&gt;
&lt;p&gt;I tried to send an OAD request on Linux, But the sensor will display CRC Failed&lt;/p&gt;
&lt;p&gt;The steps for me to create an incremental package are as follows:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&amp;nbsp;python hexmerge.py -o devices_1310.hex &amp;quot;--overlap=error&amp;quot; ../Release/devices_1310_v0.9.0.hex bim_1310.hex&lt;br /&gt;Download devices_1310.hex to MCU via UniFlash&lt;/li&gt;
&lt;li&gt;python oad_image_tool.py -v 0x0090 -t offchip -i app ../Release/devices_1310_v0.9.0.hex -ob a.bin -m 0x14F0&lt;/li&gt;
&lt;li&gt;python oad_image_tool.py -v 0x0091 -t offchip -i app ../Release/devices_1310_v0.9.1.hex -ob b.bin -m 0x14F0&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;python toad_image_tool.py -oimg a.bin -nimg b.bin -o ab.dim&amp;nbsp;&lt;br /&gt;Transfer ab.dim to Linux and issue it to the sensor using the &amp;#39;u&amp;#39; command&lt;img src="https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/156/6131.image.png" alt="image.png" width="296" height="151" data-temp-id="image.png-16845" /&gt;&lt;br /&gt;The above figure shows the output after the last instruction of sensor load&lt;br /&gt;&lt;br /&gt;I have also tried removing the offchip in steps 2-3 above, but the result was CRC Failed&lt;br /&gt;&amp;nbsp;Can you help me? Thank you&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>RE: CC1310: Turbo OAD CRC Failed</title><link>https://e2e.ti.com/thread/6322849?ContentTypeID=1</link><pubDate>Fri, 24 Apr 2026 15:21:52 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:300d4685-259e-4b2f-b68c-57157921bf08</guid><dc:creator>faker wang</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6322849?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;span&gt;Hi&amp;nbsp;&lt;/span&gt;&lt;span&gt;Daniel:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank you for continuing to investigate this issue, and I am still trying to resolve it&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Is the OAD of CC1312 and CC1310 incompatible? I tried to use the load command for CC1312 in the Linux I ported, but the first frame command reported an error, which means the packet length cannot be read&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;faker&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC1310: Turbo OAD CRC Failed</title><link>https://e2e.ti.com/thread/6322825?ContentTypeID=1</link><pubDate>Fri, 24 Apr 2026 15:10:56 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2294da28-c7e4-482d-8b8c-fdd929630565</guid><dc:creator>Daniel Guarecuco Aguiar</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6322825?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi faker,&lt;/p&gt;
&lt;p&gt;I haven&amp;#39;t found the issue yet, but I can definitely see the same. Not sure whether it is on the generated delta image or the embedded side when reading the headers.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Daniel&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: LP-CC1352P7: Not able to communicate with Thread RCP firmware from Linux(Ubuntu) using USB to UART hardware</title><link>https://e2e.ti.com/thread/6322707?ContentTypeID=1</link><pubDate>Fri, 24 Apr 2026 13:33:15 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:11326b94-5655-48a5-bffc-a99cf97faceb</guid><dc:creator>Ryan Brown1</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6322707?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1639971/lp-cc1352p7-not-able-to-communicate-with-thread-rcp-firmware-from-linux-ubuntu-using-usb-to-uart-hardware/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello Hiren,&lt;/p&gt;
&lt;p&gt;Please confirm that your host recognizes ttyUSB0 (ls /dev/tty*) and make sure that RX/TX is properly connected to DIO12/13, respectively, as well as GND.&amp;nbsp; How is the board powered: the on-LP XDS110, USB to UART converter cable, or otherwise?&amp;nbsp;&lt;a href="https://github.com/openthread/ot-br-posix"&gt;ot-br-posix &lt;/a&gt;is developed by a third party and you would benefit from inquiring whether they have any suggestions based on your log.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>LP-CC1352P7: Not able to communicate with Thread RCP firmware from Linux(Ubuntu) using USB to UART hardware</title><link>https://e2e.ti.com/thread/1639971?ContentTypeID=0</link><pubDate>Fri, 24 Apr 2026 05:35:24 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:87689273-839f-4f0b-8a58-dd5c7377783f</guid><dc:creator>Hiren Bhvua</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/1639971?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1639971/lp-cc1352p7-not-able-to-communicate-with-thread-rcp-firmware-from-linux-ubuntu-using-usb-to-uart-hardware/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; LP-CC1352P7&lt;/p&gt;&lt;p&gt;Hello TI Support Team,&lt;br /&gt;&lt;br /&gt;I am using LP-CC1352P7-1 Developement kit. I am running RCP firmware compiled using &lt;a href="https://github.com/TexasInstruments/ot-ti.git"&gt;&lt;strong&gt;ot-to&lt;/strong&gt;&lt;/a&gt; repo.&lt;br /&gt;I am able to Form Network using My Linux system as Host and &lt;strong&gt;/dev/ttyACM0 &lt;/strong&gt;port.&lt;br /&gt;Now, I have removed the &lt;strong&gt;Jumper4&amp;amp;5 &lt;/strong&gt;and connected USB to UART converter and trying to run the same RCP application using &lt;strong&gt;/dev/ttyUSB0 &lt;/strong&gt;port.&lt;br /&gt;But, using &lt;strong&gt;/dev/ttyUSB0 &lt;/strong&gt;port I am getting below error for &lt;strong&gt;otbr-agent &lt;/strong&gt;in my linux system. I am getting similar error with my actual host device as well.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB systemd[1]: Started OpenThread Border Router Agent.&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Backbone interface: wlo1&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Running 0.3.0-thread-reference-20250612-333-g5bcdd573&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Thread version: 1.4.0&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB systemd[1]: otbr-agent.service: Main process exited, code=exited, status=5/NOTINSTALLED&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Thread interface: wpan0&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB systemd[1]: otbr-agent.service: Failed with result &amp;#39;exit-code&amp;#39;.&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Radio URL: spinel+hdlc:///dev/ttyUSB0?uart-baudrate=921600&amp;amp;uart-flow-control=0&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Radio URL: trel://wlo1&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-ILS-----: Infra link selected: wlo1&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [INFO]-RCP_HOS-: OpenThread log level changed to 4&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: 55d.08:09:45.285 [C] Platform------: Init() at hdlc_interface.cpp:153: No such file or directory&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I tried to reduce the UART baudrate and still faces the same issue.&lt;br /&gt;I would like to understand the issue.&lt;/p&gt;
&lt;p&gt;Thanks in Advance&lt;br /&gt;Hiren Bhuva&lt;/p&gt;</description></item><item><title>CC1312R7: 2-GFSK whitening and CRC algorithm</title><link>https://e2e.ti.com/thread/1640096?ContentTypeID=0</link><pubDate>Fri, 24 Apr 2026 09:48:16 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:5177b681-44f1-4205-994a-1b9d37155a14</guid><dc:creator>chun dong</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/1640096?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1640096/cc1312r7-2-gfsk-whitening-and-crc-algorithm/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC1312R7&lt;/p&gt;&lt;p&gt;hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;we want to check the communication between LP-CC1312R7(RX) and other sub-1 GHz device(TX) which is not product of TI, we have verified they can commnucation well when we choose withening mode PN9, now we want to choose whitening mode as &amp;quot;7: Dynamically IEEE 802.15.4g compatible whitener and 16-bit or 32-bit CRC&amp;quot; like picture.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/156/2335.image.png" alt="image.png" width="486" height="266" data-temp-id="image.png-124669" /&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;but the LP-CC1312R7 can&amp;#39;t receive the correct data, we want to modify TX device packet build process to make they can communicate well, so can you tell us what we should do or what whitening and CRC alogrithm we should use when we choose this whitening mode.&lt;/p&gt;</description></item><item><title>RE: CC1312R7: 2-GFSK whitening and CRC algorithm</title><link>https://e2e.ti.com/thread/6322642?ContentTypeID=1</link><pubDate>Fri, 24 Apr 2026 12:47:37 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a4b30e04-e558-4034-906f-970b32048613</guid><dc:creator>Siri</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6322642?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1640096/cc1312r7-2-gfsk-whitening-and-crc-algorithm/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;You will need to purchase the IEEE 802.15.4g spec. if you want details on how whitening and CRC is implemented. This is not an open spec (I think), so we cannot share any info on how this is done.&lt;/p&gt;
&lt;p&gt;If you are making your protocol from scratch and can configure the TX as you want, why do you want to use this whitening compared to for example the 1101 compatible whitening?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Siri&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC115L: radio driver</title><link>https://e2e.ti.com/thread/6322350?ContentTypeID=1</link><pubDate>Fri, 24 Apr 2026 08:17:59 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:13106f58-5feb-4a2c-ab94-d57ee71d4500</guid><dc:creator>Siri</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6322350?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1639814/cc115l-radio-driver/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;There are no&amp;nbsp;&lt;/p&gt;
&lt;p&gt;There are no rf driver for the CC11x radios. etc&lt;/p&gt;
&lt;p&gt;The radio interface is very simple and consist of sending 8 bits strobe commands (STX, SRX, SIDLE) over SPI, plus reading and writing single register in single mode (address + 1 byte) or burst mode (address + several bytes)&lt;/p&gt;
&lt;p&gt;I have attached some examples that is written for the CC11xL + TRXEB and you can also find some examples here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://dev.ti.com/tirex/explore/node?isTheia=false&amp;amp;node=A__AK2Xbhji2LYN5xbtd.b72g__MSPM0-SDK__a3PaaoK__LATEST&amp;amp;search=CC110x"&gt;https://dev.ti.com/tirex/explore/node?isTheia=false&amp;amp;node=A__AK2Xbhji2LYN5xbtd.b72g__MSPM0-SDK__a3PaaoK__LATEST&amp;amp;search=CC110x&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The examples show how to set up a link between two devices.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/156/cc110L_5F00_app_5F00_ex.zip"&gt;e2e.ti.com/.../cc110L_5F00_app_5F00_ex.zip&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;BR&lt;/p&gt;
&lt;p&gt;Siri&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>CC115L: radio driver</title><link>https://e2e.ti.com/thread/1639814?ContentTypeID=0</link><pubDate>Thu, 23 Apr 2026 15:08:09 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:67264a58-5a3a-49a4-b901-15f33c59e890</guid><dc:creator>R.J.</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/1639814?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1639814/cc115l-radio-driver/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC115L&lt;/p&gt;
&lt;p&gt;Dear TI Support team,&lt;/p&gt;
&lt;p&gt;do you provide a fully implemented radio driver for the CC115L transmitter?&lt;/p&gt;</description></item><item><title>LAUNCHXL-CC13-90: LAUNCHXL-CC13-90 to perform the range test</title><link>https://e2e.ti.com/thread/1639978?ContentTypeID=0</link><pubDate>Fri, 24 Apr 2026 05:55:26 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:79e8cf26-9759-4393-ba25-1471dc22f76c</guid><dc:creator>chandrashekhar Venkatesh</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/1639978?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1639978/launchxl-cc13-90-launchxl-cc13-90-to-perform-the-range-test/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; LAUNCHXL-CC13-90&lt;/p&gt;&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;We have an requirement for minimum 500 meters of wireless data transfer for agriculture fields. Where Antenna will be placed with each node atlease of 10 feet height.&lt;/p&gt;
&lt;p&gt;We want to use LAUNCHXL-CC13-90 kit to test perfromace, Our data packet is not more that 100Bytes and it will be every 1Second interval trasnceiver.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We want to have maximum of 25nodes which can form an Start network.&lt;/p&gt;
&lt;p&gt;Suggest us best hardware chipsets to acheive below goal&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Transfer and receive of data with interval of 1Seconds, we can accept few retry mechanism too&lt;/li&gt;
&lt;li&gt;Datapacket size of 100Bytes&lt;/li&gt;
&lt;li&gt;Minimum range coverage is 500meters, no compromise here.&lt;/li&gt;
&lt;li&gt;Star network topology to support minimum 25 nodes.&lt;/li&gt;
&lt;li&gt;Actual deployment will in aggricultural feild, Tree hight is above the antenna height, Lets say antenna will be placed in 10Feet height, Trees will go as high as &amp;gt;20 feets. Think case when they still young trees they will be small. Still our system must be working.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Rgds&lt;/p&gt;
&lt;p&gt;Chandra&lt;/p&gt;</description></item><item><title>RE: CC1310: Turbo OAD CRC Failed</title><link>https://e2e.ti.com/thread/6321004?ContentTypeID=1</link><pubDate>Thu, 23 Apr 2026 14:32:18 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d82e4434-bc6e-42be-9b93-a59397289c6c</guid><dc:creator>Daniel Guarecuco Aguiar</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6321004?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi faker,&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t have an answer yet, but I have my environment working, I believe you have already done these steps, but for those reading:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;TIRTOS_IN_ROM is defined by default in the CC13x0 projects but not for the TI 15.4 Linux SDK, so you need to define&amp;nbsp;&lt;pre class="ui-code" data-mode="c_cpp"&gt;CFLAGS += -DTIRTOS_IN_ROM&lt;/pre&gt;&amp;nbsp;in ti15stack_linux_/example/collector/Makefile and rebuild the host_collector by running build_all.sh&lt;/li&gt;
&lt;li&gt;if build_all.sh returns with errors, check&amp;nbsp;&amp;nbsp;&lt;a href="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1543728/cc1312r-ti154stack_linux_x64_4_40_00_03-examples-don-t-build-out-the-box"&gt;CC1312R: ti154stack_linux_x64_4_40_00_03 examples don&amp;#39;t build out the box&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Now, back to the TOAD, I can see in the collector_log.txt that the delta image &amp;quot;ab.dim&amp;quot; is being detected as a regular image and not as a TOAD image, I believe this might be the reason for the CRC error. I&amp;#39;ll get back to you later.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Daniel&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC1310: Turbo OAD CRC Failed</title><link>https://e2e.ti.com/thread/6320704?ContentTypeID=1</link><pubDate>Thu, 23 Apr 2026 11:00:16 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2e0c9c70-5302-40b7-bf5f-fbae4d9f509f</guid><dc:creator>faker wang</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6320704?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;span&gt;Hi&amp;nbsp;&lt;/span&gt;&lt;span&gt;Daniel:&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;okay, thank you. I will wait for your response&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;faker&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC1310: Turbo OAD CRC Failed</title><link>https://e2e.ti.com/thread/6320701?ContentTypeID=1</link><pubDate>Thu, 23 Apr 2026 10:57:59 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:60681c57-2ced-4cef-89ad-16cd9fac8b95</guid><dc:creator>Daniel Guarecuco Aguiar</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6320701?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi faker,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m sorry, I had issues with my Linux setup. I will start testing it now, I will give you and updated tomorrow.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Daniel&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC1310: Turbo OAD CRC Failed</title><link>https://e2e.ti.com/thread/6320035?ContentTypeID=1</link><pubDate>Thu, 23 Apr 2026 02:17:57 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:80872f85-f423-4a92-b4e7-b75a578761a0</guid><dc:creator>faker wang</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6320035?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1636875/cc1310-turbo-oad-crc-failed/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;span&gt;Hi&amp;nbsp;&lt;/span&gt;&lt;span&gt;Daniel:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Has it been tested&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;faker&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC1312R: WLCSP packaging</title><link>https://e2e.ti.com/thread/6319121?ContentTypeID=1</link><pubDate>Wed, 22 Apr 2026 14:21:43 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:75d7d1e5-8b3c-4d8c-8e4c-95cc246eceed</guid><dc:creator>ZC</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6319121?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1638922/cc1312r-wlcsp-packaging/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Unfortunately the CC1312R (and its related device family variants) is only available in a QFN package. There is also the CC1312PSIP available to reduce the required PCB footprint (if that is a factor here), but that is also QFN.&lt;/p&gt;
&lt;p&gt;The CC1311P3 has the smallest available (QFN) package size of the CC131xRx family; 5x5 mm (RKP).&lt;/p&gt;
&lt;p&gt;If 2.4 GHz is an option (probably not given the application), the&amp;nbsp;CC2340R5 is available in a WCSP package.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Zack&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>CC1312R: WLCSP packaging</title><link>https://e2e.ti.com/thread/1638922?ContentTypeID=0</link><pubDate>Tue, 21 Apr 2026 15:55:48 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:9938f8cf-e80c-4b5f-8783-a4975a4a8f7a</guid><dc:creator>Steven Van Heddegem</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/1638922?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1638922/cc1312r-wlcsp-packaging/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC1312R&lt;/p&gt;&lt;p&gt;Hi TI,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m looking into building a tracker for an asian hornet. Size &amp;amp; weight therefore matter big time.&lt;/p&gt;
&lt;p&gt;Is there a way to get hold of an MCU (sub 1-GHz or just above) in WLCSP packaging?&lt;/p&gt;
&lt;p&gt;If not directly buyable from you, does it exist? Can I obtain it elsewhere?&lt;/p&gt;
&lt;p&gt;I tried looking at alternates but I couldn&amp;#39;t find any suitable MCU in WLCSP packaging.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks up front&lt;/p&gt;</description></item><item><title>CC1312R7: Gaussian Filter BT value for 2GFSK</title><link>https://e2e.ti.com/thread/1639040?ContentTypeID=0</link><pubDate>Wed, 22 Apr 2026 03:13:05 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:63856471-4f38-437a-bcf5-52f5b53f5537</guid><dc:creator>chun dong</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/1639040?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1639040/cc1312r7-gaussian-filter-bt-value-for-2gfsk/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC1312R7&lt;/p&gt;&lt;p&gt;I want to know the 2-GFSK gaussian filter BT value of CC1312R7 launchpad, i can&amp;#39;t find it from datasheet.&lt;/p&gt;
&lt;p&gt;and we want to know if the BT value are related with symbol rate and deviation chosen by user.&lt;/p&gt;</description></item><item><title>RE: CC1312R7: Gaussian Filter BT value for 2GFSK</title><link>https://e2e.ti.com/thread/6319116?ContentTypeID=1</link><pubDate>Wed, 22 Apr 2026 14:18:43 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f58d2d74-96fd-4df0-9311-a39d6f8f11c7</guid><dc:creator>ZC</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6319116?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1639040/cc1312r7-gaussian-filter-bt-value-for-2gfsk/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Please see:&amp;nbsp;&amp;nbsp;&lt;a href="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/932814/cc1312r-technical-reference-for-the-cc1312r-software-defined-radio/3448042"&gt;RE: CC1312R: Technical reference for the CC1312R software defined radio&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If there is a strong need to modify the BT please contact your local Sales team as we would need to support that directly for larger orders (rather than on E2E).&lt;/p&gt;
&lt;p&gt;The BT value&amp;nbsp;is not changed by users modifying the symbol rate/deviation.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Zack&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>CC1352P7: Not able to find the RPC firmware for the thread protocol</title><link>https://e2e.ti.com/thread/1635607?ContentTypeID=0</link><pubDate>Mon, 13 Apr 2026 04:16:45 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a9b47a68-cc9c-4be5-8935-d9b992f6e5d2</guid><dc:creator>Hiren Bhvua</dc:creator><slash:comments>10</slash:comments><comments>https://e2e.ti.com/thread/1635607?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1635607/cc1352p7-not-able-to-find-the-rpc-firmware-for-the-thread-protocol/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC1352P7&lt;/p&gt;&lt;p&gt;Hello Community,&lt;br /&gt;&lt;br /&gt;I am planning to use LP-CC1352P7-1 development kit to test the Thread Boarder Router feature with my Linux (Ubuntu 22.04) as host system and CC1352P7 kit as Radio.&lt;br /&gt;I am not able to find the example project (rpv-br) in &lt;strong&gt;simplelink_cc13xx_cc26xx_sdk_8_32_00_07 &lt;/strong&gt;sdk.&lt;br /&gt;Can anyone help to locate the example project for the same?&lt;br /&gt;&lt;br /&gt;Thanks in advance,&lt;br /&gt;Hiren Bhuva&lt;/p&gt;</description></item><item><title>RE: CC1352P7: Not able to find the RPC firmware for the thread protocol</title><link>https://e2e.ti.com/thread/6319032?ContentTypeID=1</link><pubDate>Wed, 22 Apr 2026 13:19:29 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:635e4ce8-95eb-490e-a1a0-755b39ac4298</guid><dc:creator>Hiren Bhvua</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6319032?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1635607/cc1352p7-not-able-to-find-the-rpc-firmware-for-the-thread-protocol/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi &lt;a href="https://e2e.ti.com/members/7092658"&gt;Arthur R&lt;span class="emoticon" data-url="https://e2e.ti.com/cfs-file/__key/system/emoji/2611.svg" title="Ballot box with check"&gt;&amp;#x2611;&lt;/span&gt;️ (7092658)&lt;/a&gt;&amp;nbsp;,&lt;br /&gt;I am able to test the Thread Network Formation using CC1352P7 developement board using /dev/ttyACM0 uart port.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;However, when I remove the UART RX/TX jumpers (to remove the debugger UART connections) and use USB to UART connector (/dev/ttyUSB0) tfor UART communication then I am getting below error in the otbr-agent.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB systemd[1]: Started OpenThread Border Router Agent.&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Backbone interface: wlo1&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Running 0.3.0-thread-reference-20250612-333-g5bcdd573&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Thread version: 1.4.0&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB systemd[1]: otbr-agent.service: Main process exited, code=exited, status=5/NOTINSTALLED&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Thread interface: wpan0&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB systemd[1]: otbr-agent.service: Failed with result &amp;#39;exit-code&amp;#39;.&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Radio URL: spinel+hdlc:///dev/ttyUSB0?uart-baudrate=921600&amp;amp;uart-flow-control=0&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-AGENT---: Radio URL: trel://wlo1&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [NOTE]-ILS-----: Infra link selected: wlo1&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: [INFO]-RCP_HOS-: OpenThread log level changed to 4&lt;br /&gt;Apr 22 18:47:22 hiren-ASUS-EXPERTBOOK-B1503CVA-B1503CVAB otbr-agent[1268822]: 55d.08:09:45.285 [C] Platform------: Init() at hdlc_interface.cpp:153: No such file or directory&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;Can you help to understand the issue?&lt;br /&gt;Thanks,&lt;br /&gt;Hiren&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>SMARTRF-STUDIO-7: Mac support</title><link>https://e2e.ti.com/thread/1638921?ContentTypeID=0</link><pubDate>Tue, 21 Apr 2026 15:55:45 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:76edb744-959f-4505-8b2c-b8f8a3751318</guid><dc:creator>Mark Szente</dc:creator><slash:comments>2</slash:comments><comments>https://e2e.ti.com/thread/1638921?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1638921/smartrf-studio-7-mac-support/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; SMARTRF-STUDIO-7&lt;/p&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I just downloaded SmartRF Studio. It&amp;#39;s a zip file, containing a Windows executable file. I use a Mac, and have no access to any Windows-based machine. How could I use the tool?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br /&gt;Mark&lt;/p&gt;</description></item><item><title>RE: SMARTRF-STUDIO-7: Mac support</title><link>https://e2e.ti.com/thread/6318853?ContentTypeID=1</link><pubDate>Wed, 22 Apr 2026 10:58:08 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0ffe0c6f-f3bb-44fa-a7d4-836a170fdce9</guid><dc:creator>Mark Szente</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6318853?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1638921/smartrf-studio-7-mac-support/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Thanks. If anyone&amp;#39;s facing this issue in the future, here&amp;#39;s what I did. Get UTM and CrystalFetch from App Store. You can have a Windows-based VM up and running in like 5-10 mins. Make sure you share the folder where your Studio installer is located.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>