# Here 4 GPS stuck at white Light

**URL:** <https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400>\
**Category:** Here GPS\
**Created:** [23 June 2025 13:03 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400 "2025-06-23T13:03:28Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aman](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/a/90ced4/32.png) [@Aman](https://discuss.cubepilot.org/u/Aman)\
**Post date:** [23 June 2025 13:03 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/1 "2025-06-23T13:03:28Z")

</div>

Hello Experts,  
I am facing a issue where my Here 4 GPS is stuck at white light randomly after some flights (happened on 7 new GPS out of 100), 🥲

 ![Media](https://discuss.cubepilot.org/uploads/default/original/2X/9/9766f49f1e9ba6cc99b10138d35af686733e32c4.jpeg)

Configuration:-  
I am using PX4 (1.15.2) autopilot running on Cube orange+, with Here4 GPS

Once the solid white light appear, the GPS is not detecting by the PX4. I also uploaded Ardupilot but the problem remains the same.  
I also tried to update the firmware on the Here4 GPS using ardupilot and mission planner [[https://docs.cubepilot.org/user-guides/here-4/here-4-manual#id-3.-firmware-update](https://docs.cubepilot.org/user-guides/here-4/here-4-manual#id-3.-firmware-update)]([https://official](https://official) website)  
but a ? appears in the name column, No HW version, No SW version,  
I am not able to communicate with the GPS through Drone CAN GUI tool, nor by U blox U centre tool,

 ![Screenshot (11)](https://discuss.cubepilot.org/uploads/default/original/2X/b/b54f41a0e888ed03d89c2dedb49757d28d90276e.jpeg)

I am attaching a log file and videos for reference [June\_12\_HERE4\_Issue](https://redonsystems-my.sharepoint.com/:f:/g/personal/arunbalaji_madasamy_redonsystems_in/Elx6suqi_W5KuhosWFv2hRABPpGvLmYWOoa7ifVjm4hTWA?e=gmc1wh)  
Please help me to solve the issue.

Thank You

---

<div class="post-metadata">

**Author:** ![xfacta](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/x/5f8ce5/32.png) [@xfacta](https://discuss.cubepilot.org/u/xfacta)\
**Post date:** [24 June 2025 05:29 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/2 "2025-06-24T05:29:20Z")

</div>

White LEDs are usually a physical connection problem as far as I know.  
Try setting `BRD_BOOT_DELAY,5000` too, this allows the Here to boot up before the flight controller so CAN communication will be ready to go when the FC starts interrogating.

---

<div class="post-metadata">

**Author:** ![Aman](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/a/90ced4/32.png) [@Aman](https://discuss.cubepilot.org/u/Aman)\
**Post date:** [24 June 2025 05:59 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/3 "2025-06-24T05:59:41Z")

</div>

Hi @xfacta Thank you for your reply,  
the cube and GPS are brand new, and I am doing the connection as per the document  
I tried to change BRD\_BOOT\_DELAY to 5000, But the problem remain same,  
any other solution.

Thank you

---

<div class="post-metadata">

**Author:** ![xfacta](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/x/5f8ce5/32.png) [@xfacta](https://discuss.cubepilot.org/u/xfacta)\
**Post date:** [24 June 2025 12:54 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/4 "2025-06-24T12:54:28Z")

</div>

Do you have more than one connector coming out of the Here4?  
Or did you wire up connectors yourself?  
Show a photo

---

<div class="post-metadata">

**Author:** ![Matino](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/m/ba8739/32.png) [@Matino](https://discuss.cubepilot.org/u/Matino)\
**Post date:** [25 June 2025 12:18 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/5 "2025-06-25T12:18:12Z")

</div>

I am also facing the same issue on 10 units out of 120 new Here4 GPS modules.

The problem also appeared randomly after a few flights and affected GPS units get stuck with a solid white light and are no longer detected by Ardupilot (No GPS) and the CAN node isn’t visible in DroneCAN in Setup tab in Mission Planer.

The HERE4 units were all on the latest firmware available from Mission Planer.

Here is the picture that shows the cable used (it is stock HERE4 cable). There is no difference between CAN1 or CAN2 connector.

 ![IMG20250625135448](https://discuss.cubepilot.org/uploads/default/original/2X/6/6abf1845ea2547df9860fe43e4c40214f463e9db.jpeg)

---

<div class="post-metadata">

**Author:** ![Aman](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/a/90ced4/32.png) [@Aman](https://discuss.cubepilot.org/u/Aman)\
**Post date:** [25 June 2025 12:37 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/6 "2025-06-25T12:37:09Z")

</div>

Hi @xfacta I have extended the wire in some GPS, and some with Here 4 original cable, but the problem is occurring in both configuration.

---

<div class="post-metadata">

**Author:** ![arunbalaji.madasamy](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/a/e8c25b/32.png) [@arunbalaji.madasamy](https://discuss.cubepilot.org/u/arunbalaji.madasamy)\
**Post date:** [3 July 2025 07:04 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/7 "2025-07-03T07:04:36Z")

</div>

Hi All,

I am also facing the same issue

Need the urgent attention from CubePilot

And if anyone facing this same issue or found the solution please give us the solution here

Thanks

---

<div class="post-metadata">

**Author:** ![hoverit](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/hoverit/32/8970_2.png) [@hoverit](https://discuss.cubepilot.org/u/hoverit)\
**Post date:** [11 July 2025 17:04 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/8 "2025-07-11T17:04:19Z")

</div>

Hi

Did you find solution for this

---

<div class="post-metadata">

**Author:** ![Matino](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/m/ba8739/32.png) [@Matino](https://discuss.cubepilot.org/u/Matino)\
**Post date:** [14 July 2025 04:45 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/9 "2025-07-14T04:45:10Z")

</div>

Hi,  
Unfortunately, not yet. I’m still waiting for an official response from the developers.

---

<div class="post-metadata">

**Author:** ![RedbullF1](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/redbullf1/32/8107_2.png) [@RedbullF1](https://discuss.cubepilot.org/u/RedbullF1)\
**Post date:** [15 July 2025 01:28 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/10 "2025-07-15T01:28:21Z")

</div>

Maybe revert back to old firmware via SWD?

---

<div class="post-metadata">

**Author:** ![Aman](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/a/90ced4/32.png) [@Aman](https://discuss.cubepilot.org/u/Aman)\
**Post date:** [4 August 2025 11:57 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/11 "2025-08-04T11:57:28Z")

</div>

> [@RedbullF1](#):
>
> aybe revert back to old firmware via SWD

Hi,  
can you please give me some more details on how to go back to older firmware, or can you share me some documents for reference.

Thank You

---

<div class="post-metadata">

**Author:** ![RedbullF1](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/redbullf1/32/8107_2.png) [@RedbullF1](https://discuss.cubepilot.org/u/RedbullF1)\
**Post date:** [4 August 2025 19:47 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/12 "2025-08-04T19:47:14Z")

</div>

Wait for @philip update. There’s procedure he’ll be sharing to get them working.

---

<div class="post-metadata">

**Author:** ![NWBlue](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/nwblue/32/8988_2.png) [@NWBlue](https://discuss.cubepilot.org/u/NWBlue)\
**Post date:** [5 August 2025 14:35 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/13 "2025-08-05T14:35:06Z")

</div>

Hello everyone. Here is the mandatory update for the Here4. It must be applied to all Here4’s before further flight.

> [@SB\_0000010 Mandatory Here4 bootloader update before further flight](https://discuss.cubepilot.org/t/sb-0000010-mandatory-here4-bootloader-update-before-further-flight/15630):
>
> BEFORE FURTHER FLIGHT Urgent Bootloader Update needed on Here4 If your Here4 doesn’t breath blue on boot, then you MUST do this bootloader update All Here4 users need to update the bootloader on their Here4 units BEFORE FURTHER FLIGHT. For units NOT showing blue breathing at boot The process for doing this update is as follows: Follow the steps here to update the firmware [https://docs.cubepilot.org/user-guides/here-4/here-4-manual#id-3.-firmware-update](https://docs.cubepilot.org/user-guides/here-4/here-4-manual#id-3.-firmware-update) Once the Update is done, set parameter on Here4 FLASH\_BOOTLOADER to 1 wait for either Bootloader Flash OK or Bootloader Unchanged message An updated bootloader boots with Blue Breathing at boot. It will breathe purple if CAN1 on here4(blue/white cable) is not connected or Cube is still booting, so to check best to unplug and plug Here4 without power cycling the Cube itself. Use the Blue/white Can cable on the here 4 to CAN 1 or 2 on the Cube carrier board For units already showing solid White LED (NOT breathing) If you have appropriate SWD connector (6pin JST SUR) to Here4 available, and are capable of doing a bootloader update. Follow the following steps: For STLink: Use this [bootloader file](https://github.com/CubePilot/GNSSPeriph-release/raw/refs/heads/release/bootloaders/Here4_bl.bin) and flash at address 0x08000000 For JLink: Use this [bootloader file](https://github.com/CubePilot/GNSSPeriph-release/raw/refs/heads/release/bootloaders/Here4_bl.hex) use JFlashLite to flash. Important: For users that are not capable of opening Here4 unit and updating using JST SUR and Debug probe to fix solid white LED, please contact your Reseller for further support. For units that are still healthy make sure to follow primary bootloader update method. Additional Resources: [Batch Update Tool](https://github.com/CubePilot/DroneCAN-Batch-Updater/blob/v0.0.1/Here4%20Batch%20Update%20User%20Manual.md)[Here4 FW Release 1.15.0](https://github.com/CubePilot/GNSSPeriph-release/releases/tag/v1.15.0)

---

<div class="post-metadata">

**Author:** ![sdhall102](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/s/ee7513/32.png) [@sdhall102](https://discuss.cubepilot.org/u/sdhall102)\
**Post date:** [23 October 2025 12:38 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/14 "2025-10-23T12:38:55Z")

</div>

I am attempting to reload firmware using ST-LINK v2, and also with v3, but not having luck seeing “the target” from Stm32cubeprogrammer. Trying to identify SWDIOand SWCLK pins on 6 pin JST-SUR header. Is there a description of the procedure somewhere?

Would appreciate any help or info.

Thank you

---

<div class="post-metadata">

**Author:** ![sdhall102](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/s/ee7513/32.png) [@sdhall102](https://discuss.cubepilot.org/u/sdhall102)\
**Post date:** [23 October 2025 12:46 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/15 "2025-10-23T12:46:50Z")

</div>

The procedure in the bulletin does not cover the firmware update using Stm32cubeprogrammer. If you have that procedure can you please share. Specifically, what is the pinout from the internal 6 pin JST-SUR connector to the ST-LINK 10 pin connector on st-link v2 or to the 20 pin connector on ST-LINK v3.

Thank you.

---

<div class="post-metadata">

**Author:** ![xfacta](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/x/5f8ce5/32.png) [@xfacta](https://discuss.cubepilot.org/u/xfacta)\
**Post date:** [24 October 2025 00:54 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/16 "2025-10-24T00:54:46Z")

</div>

> [@SB\_0000010 Mandatory Here4 bootloader update before further flight](https://discuss.cubepilot.org/t/sb-0000010-mandatory-here4-bootloader-update-before-further-flight/15630/19):
>
> The instructions are complete. As we have said earlier, if you’re not an advanced user who already knows how to use the SWD system without further instruction, please contact your reseller if your unit is bricked

You use an ST-Link V2  
Only connect the pins 4, 5 and 6.  
Power the Here4 via the CAN bus, from the flight controller like normal.

You can verify the ground or 0v pin by testing continuity to the tin shield over chipset.

---

<div class="post-metadata">

**Author:** ![KISHAN](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/k/e95f7d/32.png) [@KISHAN](https://discuss.cubepilot.org/u/KISHAN)\
**Post date:** [11 March 2026 14:00 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/17 "2026-03-11T14:00:05Z")

</div>

Hi @xfacta

I have few doubts can you please help me this matter.

1. I bought Here 4 GPS and as per the above solution for Bootloader updated i have done the same. But the after few flights normal suddenly at any random flight the GPS is having White LED light. Why the white LED is present in solid state. We couldn’t find the root cause why this is happen very eventually after updated with bootloader.
2. How to identify the bootloader is present in the HERE 4 GPS with correct method.
3. Whether we have to do the bootloader update for all the GPS which is being purchased recently. If bootloader is necessary whether it can be done by STLINK or Drone CAN updater
4. In few post `FLASH_BOOTLOADER` to `1` is advised to set but whether this process is also necessary to do for all the GPS which is purchased newly.

@philip @Chris @sidbh @Michael_Oborne Also request you shed some lights on this matter.

---

<div class="post-metadata">

**Author:** ![xfacta](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/x/5f8ce5/32.png) [@xfacta](https://discuss.cubepilot.org/u/xfacta)\
**Post date:** [12 March 2026 03:49 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/18 "2026-03-12T03:49:55Z")

</div>

I imagine new Here4’s already have the latest firmware and bootloader, you’d be able to easily verify that. Look for firmware version 1.15

The best way to update the bootloader (if required) is to do the firmware update, then set the bootloader update parameter. You can see in messages if the bootloader was updated, or didnt need to be updated.

---

<div class="post-metadata">

**Author:** ![Mauro.Tanure](https://discuss.cubepilot.org/letter_avatar_proxy/v4/letter/m/ecd19e/32.png) [@Mauro.Tanure](https://discuss.cubepilot.org/u/Mauro.Tanure)\
**Post date:** [9 April 2026 17:36 UTC](https://discuss.cubepilot.org/t/here-4-gps-stuck-at-white-light/15400/19 "2026-04-09T17:36:49Z")

</div>

We just received 20 units.

- 3 were stuck on white straight out of the box. First boot was already like that.
- 2 showed the issue after a few reboots. They were up to date.

CubePilot is assisting.
