Hello, thank you for your answers;
@danielt @Loic I tried to change the root to point to root=/dev/mmcblk0p10, see the command line below:
(not sure how I am supposed to know that mmcblk0p10 is the rootfs, though)
mkbootimg --kernel Image.gz+dtb
–cmdline “root=/dev/mmcblk0p10 rw rootwait console=ttyMSM0,115200n8”
But I still couldn’t get a correct boot (full logs here):
run-init: opening console: No such file or directory
No init found. Try passing init= bootarg.
You can also notice in the logs that I have no “disk” repository in /dev nor “udev” repository in initramfs…
For information, here are a few details about what I do:
sudo …/qdl prog_emmc_firehose_8916.mbn rawprogram.xml patch.xml
- then I can access fastboot mode and I flash successfully my board with 18.01 release, then getting problems such as described earlier
@ndec I couldn’t get a boot from SD yet but I am working on it.
About the missings bits in the logs: I notice sometimes the boot is completely different, maybe rebooting from the above state is causing more boot errors… The boots logs given above are those I have directly after the fastboot flash
Last information that could be interesting: in my board power come either from the USB port, or from a battery. Above logs are given when powering from USB port (that could be an issue as USB_HS_ID is then high). When I boot from battery (USB_HS_ID is low), I get the following logs. A bit different but the error is the same.
Sorry if something is not clear, I am not a linux expert and might miss something basic; hence do not hesitate, any help is welcome. Thank you very much !