mount: mount point /tmp does not exist
Well, do 'mkdir /tmp' before that command.
Doesn't matter, as long as there's "#" as that means you have root access.Also what prompter should I expect?
The board starts once in a few trials, I pasted three power ups - two failed to bootup on third, it was succesful. On eevery powerup it shows DM36x initialization passed.
1. Does it mean that my bootloader is fine and my boot image is corrupted? (why it starts sometimes?
The issue is in rootfs, but I'm not sure what it is exactly. From the logs:
awk: /proc/devices: No such file or directory
The 'awk' editor is used to edit config of devices before they are accessible. This can have many reasons, but it looks like race condition - a programming bug introduced by DJI. We may be able to fix that, but we need the firmware dumped to know where the 'awk' is executed.
Wait, are you pressing ctrl+c during boot? Are you sure you're not doing that too early? You may be cancelling important actions during boot, press that only near finish, preferably when you see the encoder loaded.I am not sure how to stop decoding process, I've never managed to stop autoboot, I am only succesful with Ctrl+C, but like in example pasted below it seems that if I am doing it too often, the cli is blocked for 5 minutes