NavQ is not being detected by uuu on windows or mac, when NavQ is set to boot from USB. Trying to flash it just says "waiting for known USB device to appear.."
When NavQ is setup to boot from SD card, it seems to go through a boot from mmc1 and seems to be in a loop. Here is the snippet of the log from this mode.
switch to partitions #0, OK is current device 28447232 bytes read in 1220 ms (22.2 MiB/s) Booting from mmc ... 39567 bytes read in 17 ms (2.2 MiB/s) ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Using Device Tree in place at 0000000043000000, end 000000004300ca8e Can't find cec device id=0x3c fail to probe panel device adv7535@3d failed to get any video link display timings probe video device failed, ret -22 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.4.24-2.1.0+gbabac008e5cf (oe-user@oe-host) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT Fri Jul 24 23:17:18 UTC 2020 [ 0.000000] Machine model: NXP i.MX 8M Mini NavQ Board with LPDDR4 memory [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: UEFI not found.
Any tips on getting NavQ up and running?
The issue has been resolved - seems to have been due to power supply.
When using a fast USB-C charger to supply power, the device seems to be stuck in a boot cycle, although I re-call reading in the guide somewhere that a fast charger should work..
When power to the NavQ was supplied from the laptop, I was able to boot up fine and get to the Linux shell.
Can you send some pictures of your boot switches and screen when you're getting these errors?
Also, are you connected using the USB-C cable? You can not flash the board using the microUSB port.
Thanks for your post - Let me get someone to reply on this.
Q: please confirm - did your NavQ boot from the factory? They were all tested before they were sent out.
I assume by your question you have already followed our guides here?