A user's guide (manual) is really needed; the wiki page isn't enough

[dukla2000]

You're welcome!

ditto

Yes, I agree that a general thread devoted to the wiki in the "General" section of the forum is a good idea. But regarding the board-specific information for the RockPro64, I'd prefer that we continue the discussion here, at this thread.

Agree, and agree.

I am struggling with the NOOB wiki page and feel it is the same problem: on the one hand having a single page that references all Pine products is "nice". On the other it needs to cater for too many exceptions - Allwinner, Pine64 installer, 2A/3A/5A power supplies etc. I read the NOOB page at least 3 times while my Rockpro64 was in the post and was unable to decipher my path - I have been using arm SBC as my only PC for over 2 years (RPi 3, VIM2) so figure I am not too dumb!

As the NOOB page didnt help me, and in line with lucho OP, I figure we do need a ROCKPro64 specific "get it going" section: I have scoured the NOOB page again but cannot see a way to make ROCKPro64-specific info easily available. Because there is a lot of info to try cover for NOOBs (have they got eMMC, WifI card, NVMe etc etc) think we need a NOOB page for each model rather than trying to update the single existing. Or adding more to the main ROCKPro64 page.

Other thoughts/ideas for this welcome though.

Re: my SW4 table – I will then add it, if there are no objections, as the current information is not exhaustive (thorough). It doesn't, for example, answer the question what happens if both the microSD card and the eMMC module are installed, but the jumper is not. It just won't boot when power is applied.

No - it will boot from the eMMC. (Double checked this morning on my system and amended the wiki!)

And by the way, I haven't yet explained to myself the "jumper removal after power on" trick. How exactly does it work? Because of what? Can someone explain it in details? (I mean the internal mechanism due to which it works, not its usage, which has already been discussed.)

My reading of the schematic indicates this removes or shorts the eMMC clock. So if you have a bootable SDcard in place (and leave the jumper on) 111 effectively becomes 100 (as per your table) as there is no effective eMMC present. So u-boot can only find a bootable image on the SDcard and proceeds with that for an initrd etc.

The limitation of this is you cannot work on the eMMC at all after boot - /dev/mmcblk1 has not been initialised in the kernel. There are in fact 2 ways to work around this:
1) Remove the jumper before the white LED comes on. The means that rootfs has not yet been mounted - when it does mount it can see and enumerate the eMMC. (But as u-boot identified the SDcard in the first place all boot/kernel stuff comes from the SDcard.)
2) After boot completes and you get a command prompt you can also remove the jumper, and then run /usr/local/sbin
/rockpro64_reset_emmc.sh which will trigger initialisation of /dev/mmcblk1. Havent tested this myself.
(I needed this get out when I corrupted the eMMC enough so it would not boot. But not enough so that it still said to u-boot it had an image!)