Hello! I have somehow gotten the Sonix board on my SkyViper into a state where it doesn’t broadcast a WiFi network anymore.
After the first few flights out of the box, I decided to look around in the web interface and changed the SSID and password. I didn’t have the correct SSID format so the SkyViper app didn’t recognize the network anymore. I decided the easiest way to set it back was to hit the factory reset button in the web interface. The WiFi went down as expected, but never came back up.
SkyRocket support directed me to try placing FACRESET.TXT and WIFI.TXT files on the microSD, as well as a flight board initiated reset by holding down the PHOTO and VIDEO buttons on the controller. However, none of these methods seemed to have any effect. The card was 16GB formatted FAT32 and was completely empty besides the TXT or firmware files I was trying.
This function in the Sonix board code seems to remove the FACRESET.TXT file is if’s being read. However, my FACRESET.TXT file is never removed from the card.
This is the output from the UART (115200 baud) on TP2 of the Sonix board. The output is the same upon power-up no matter what I do and nothing else is printed after about 1 second:
bootsel...G=iI[D4B0091B][002BFE40]Srtos run in NORMAL snx i2c:0 controller at 0x98300000 (irq = 1) snx i2c:1 controller at 0x98400000 (irq = 2) isp camera driver loaded Audio Driver: audio driver init ok. Audio Middleware: audio middleware init ok. serial_flash ID=c2,20,15 ### serial_flash speed = 0 serial_flash(MXIC) , size = 2MB
Traffic on the cable from the flight board to the Sonix board consisted only of HEARTBEATs and NAMED_VALUE_INTs corresponding to the controller button presses. There was no traffic from the Sonix board to the flight board. Mission Planner connects fine via this cable, and the rest of the drone flies fine after IMU and Mag calibration.
I am not sure whether I should be seeing periodic text messages on TP2. Nor am I sure whether it’s possible for the firmware (or NVRAM?) to be corrupt. I put FIRMWARE_660R_F.bin (also renamed to FIRMWARE_660R.bin) onto the microSD, but I don’t think the board is booting from it. SkyRocket’s README says that this file is for “when the bootloader pin is used on the Sonix board”. Presumably, that means I should pull a pin to 3.3V or Gnd. However, I do not know what pin or test point is the bootloader pin since I haven’t gotten a detailed datasheet nor reference manual for the chip, bootloader, or SDK from Sonix.
My goal is to get the SkyViper to how it was when it came out of the box juuuust last week, I would greatly appreciate any help or ideas of what I should poke at.