Vocore2 reboots when wifi switched on
Posted: Sun May 18, 2025 2:25 pm
Hi,
I have a vocore2 which always reboots when wifi is switched on. As long as I keep it off, device works.
I have copied all /etc/config files from a working system to the failing one, without success.
I have the suspicion that the FACTORY partition might be faulty, however looking at three different boards, all of them have slight differences.
I have backup all mtd partitions from a working board, and would now like to re-program e.g. the factory partition.
I also found the MT7628.sh file, which generates a default configuration.
HOWEVER, I do not get mtd to work:
regardless what I do:
mtd unlock /dev/mtd2 or mtd unlock factory, it comes back with
could not open mtd device: factory (or /dev/mtd2)
Could not open mtd device: factory
Obviously I cannot write then as well.
As the board is now not networking, I cannot try to download any other flash_unlock program etc.
Partition factory is marked read-only in DTS file, so I tried to change this and removed /* read-only */. However then kernel wants to start, but somehow does not find a specific magic value pattern to identify a start of a partition.
1. Is there any other way to be able to flash the factory partition?
2. is my assumption correct at all, that a faulty factory partition MIGHT bring the wifi driver to crash?
I do not see any kernel panic, oobs or other messages though.
thank you
Martin
I have a vocore2 which always reboots when wifi is switched on. As long as I keep it off, device works.
I have copied all /etc/config files from a working system to the failing one, without success.
I have the suspicion that the FACTORY partition might be faulty, however looking at three different boards, all of them have slight differences.
I have backup all mtd partitions from a working board, and would now like to re-program e.g. the factory partition.
I also found the MT7628.sh file, which generates a default configuration.
HOWEVER, I do not get mtd to work:
regardless what I do:
mtd unlock /dev/mtd2 or mtd unlock factory, it comes back with
could not open mtd device: factory (or /dev/mtd2)
Could not open mtd device: factory
Obviously I cannot write then as well.
As the board is now not networking, I cannot try to download any other flash_unlock program etc.
Partition factory is marked read-only in DTS file, so I tried to change this and removed /* read-only */. However then kernel wants to start, but somehow does not find a specific magic value pattern to identify a start of a partition.
1. Is there any other way to be able to flash the factory partition?
2. is my assumption correct at all, that a faulty factory partition MIGHT bring the wifi driver to crash?
I do not see any kernel panic, oobs or other messages though.
thank you
Martin