<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[OTA UART flashing irreversible error]]></title><description><![CDATA[<p>we are currently testing BLE chip FR8000 FW update procedures over UART, and we got a situation that we think requires further analysis.</p>
<p>we downloaded over UART a new FW version in the chip and commanded reboot but after reboot the BLE chip does not work anymore meaning that the new FW does not start and we cannot erase or program anymore the chip using SWD interface.</p>
<p>probably we did some error in the UART update procedure (is under development), but the serious problem is that, from that moment, the chip can't be re-flashed with a valid FW even using the SWD interface.</p>
<p>when using JFlash we successfully connect to the device it's ok but sending Erase chip command we got errors or sending Erase sector we got errors also trying to Program the device results in errors.<br />
During JFlash SWD operation, the FR8000 chip seems to reset itself several times.</p>
<p>Considering this problem from a general perspective, an error during FW transfer over UART is always possible and there should be a way to recover this situation by starting a new FW download over UART.</p>
<p>From FW upload documentation is seems that the new FW is copied in an alternative flash bank and only after checking CRC consistency the new FW is applied at reboot.<br />
Is that statement, correct?<br />
<img src="/assets/uploads/files/1781359497621-connect.png" alt="3_1781359445506_connect.png" class="img-responsive img-markdown" /> <img src="/assets/uploads/files/1781359497592-erase-chip-resized.png" alt="2_1781359445506_erase chip.png" class="img-responsive img-markdown" /> <img src="/assets/uploads/files/1781359497586-erase-sector-resized.png" alt="1_1781359445506_erase sector.png" class="img-responsive img-markdown" /> <img src="/assets/uploads/files/1781359497634-programming-resized.png" alt="0_1781359445505_programming.png" class="img-responsive img-markdown" /><br />
which is the root cause of the situation we generated with our UART FW update attempt?</p>
<p>Thank You for your support</p>
]]></description><link>http://www.freqchip.net:4567/topic/1835/ota-uart-flashing-irreversible-error</link><generator>RSS for Node</generator><lastBuildDate>Sat, 13 Jun 2026 22:43:36 GMT</lastBuildDate><atom:link href="http://www.freqchip.net:4567/topic/1835.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 13 Jun 2026 14:07:03 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to OTA UART flashing irreversible error on Invalid Date]]></title><description><![CDATA[<p>we are currently testing BLE chip FR8000 FW update procedures over UART, and we got a situation that we think requires further analysis.</p>
<p>we downloaded over UART a new FW version in the chip and commanded reboot but after reboot the BLE chip does not work anymore meaning that the new FW does not start and we cannot erase or program anymore the chip using SWD interface.</p>
<p>probably we did some error in the UART update procedure (is under development), but the serious problem is that, from that moment, the chip can't be re-flashed with a valid FW even using the SWD interface.</p>
<p>when using JFlash we successfully connect to the device it's ok but sending Erase chip command we got errors or sending Erase sector we got errors also trying to Program the device results in errors.<br />
During JFlash SWD operation, the FR8000 chip seems to reset itself several times.</p>
<p>Considering this problem from a general perspective, an error during FW transfer over UART is always possible and there should be a way to recover this situation by starting a new FW download over UART.</p>
<p>From FW upload documentation is seems that the new FW is copied in an alternative flash bank and only after checking CRC consistency the new FW is applied at reboot.<br />
Is that statement, correct?<br />
<img src="/assets/uploads/files/1781359497621-connect.png" alt="3_1781359445506_connect.png" class="img-responsive img-markdown" /> <img src="/assets/uploads/files/1781359497592-erase-chip-resized.png" alt="2_1781359445506_erase chip.png" class="img-responsive img-markdown" /> <img src="/assets/uploads/files/1781359497586-erase-sector-resized.png" alt="1_1781359445506_erase sector.png" class="img-responsive img-markdown" /> <img src="/assets/uploads/files/1781359497634-programming-resized.png" alt="0_1781359445505_programming.png" class="img-responsive img-markdown" /><br />
which is the root cause of the situation we generated with our UART FW update attempt?</p>
<p>Thank You for your support</p>
]]></description><link>http://www.freqchip.net:4567/post/4481</link><guid isPermaLink="true">http://www.freqchip.net:4567/post/4481</guid><dc:creator><![CDATA[gianfyu]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>