Here 4 GPS stuck at white Light

Here GPS
1

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), :smiling_face_with_tear:

Media
Media1600Ă—1600 184 KB

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://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)
Screenshot (11)1920Ă—1080 232 KB

I am attaching a log file and videos for reference June_12_HERE4_Issue
Please help me to solve the issue.

Thank You

2

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.

3

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

4

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

5

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
IMG202506251354481920Ă—2560 101 KB

6

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.

7

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

8

Hi

Did you find solution for this

9

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

10

Maybe revert back to old firmware via SWD?

11

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

12

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

13

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

1 Like
14

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

15

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.

16

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.