# #1 Flash memory corruption causes bootloop

**Type:** <mark style="color:red;">**Critical**</mark>

## Problem:&#x20;

Some teams have returned radios that were stuck in a bootloop. This means that while the radio is coming up, it reboots on its own.&#x20;

## Investigation

Upon further investigation, these units appear to have part of their flash memory corrupted. The corrupted flash memory is factory burned and contains calibration and regulatory limits.&#x20;

Here's an example:&#x20;

<figure><img src="https://4239402461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzaDthb1gXvbj84qIfOUE%2Fuploads%2FWqdJJiMyTLASBgd14otN%2Fmemory-corruption-behavior.gif?alt=media&#x26;token=24ba3ffd-40f2-462f-9566-79606775cb31" alt=""><figcaption></figcaption></figure>

### Affected Units

It's possible that all units can be affected by this issue.&#x20;

Anecdotally, it appears that this corruption can happen when upgrading from firmware versions prior to 1.2.0. At the moment we believe that radios from the first production run are affected. These would have been distributed at the 2024 FIRST Championship and some units sold during 2024. These units can be identified by having a S/N that starts with 2401:

<figure><img src="https://4239402461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzaDthb1gXvbj84qIfOUE%2Fuploads%2FSr4MMhNAy3d3G08vQ9Q7%2Fimage.png?alt=media&#x26;token=d2f61934-894f-4f41-a2f4-802868effe58" alt=""><figcaption></figcaption></figure>

Additionally, radios from the first production batch will have numbered DIP switches and won't have the AUX1/AUX2/AP labels:&#x20;

<figure><img src="https://4239402461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzaDthb1gXvbj84qIfOUE%2Fuploads%2F8wBDwfd8I4KwwRokCCLU%2Fimage.png?alt=media&#x26;token=8c3a5626-6f88-4360-9e3a-80614b5c74cd" alt="" width="398"><figcaption><p>Radios from the first production batch will not have AUX1 PoE / AUX2 PoE / 2.4 GHz AP labels.</p></figcaption></figure>

<figure><img src="https://4239402461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzaDthb1gXvbj84qIfOUE%2Fuploads%2Fk18syZqeh9bd3kuUOOCR%2Fimage.png?alt=media&#x26;token=d80aa55c-bf28-4c06-b718-2f22f259c206" alt="" width="375"><figcaption><p>AUX1 PoE / AUX2 PoE / 2.4 GHz AP labels mean your radio is NOT part of the first production batch. </p></figcaption></figure>

## Solution

A mitigation has been developed and introduced in firmware version 1.2.5. <mark style="color:red;">**All teams should update their radios to v1.2.5 (or greater) ASAP to avoid potential issues.**</mark>&#x20;

### What if your radio is affected?

If your radio is affected by this issue, it can be recovered using remote support. Unfortunately the only way to recover this requires restricted access to the device as the partition we’re accessing was explicitly called out as a protected region during the regulatory approvals.

Please contact WestCoast Products support and they'll coordinate remote support.&#x20;

Here's an example of how remote support works:

{% embed url="<https://www.youtube.com/watch?v=pFfcw-5u2ro>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://frc-radio.vivid-hosting.net/overview/support/known-issues/1-flash-memory-corruption-causes-bootloop.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.