Remove 1s boot delay from parallella-next?

[olajep]

I added a 1 second boot delay to parallella-uboot/parallella-next.
3e9bf5c#diff-dfe3aa552f2a30fd1c63469710ada33fR38

The boot-flash images in https://github.com/parallella/parallella-flash are based on the parallella-next u-boot branch (https://github.com/parallella/parallella-uboot/tree/parallella-next).

However according to this below that was not a good idea:
https://github.com/parallella/parallella-examples/blob/master/rpi-camera/README#L29

    Note that you might need to have a serial cable plugged in or
    have it tied to GND because the u-boot in the parallella-flash
    repo has a 'press any key' to interrupt boot prompt and garbage
    during boot on the serial line can interrupt the start sequence
    if it's floating.

I think we could emulate this by adding:

echo "Press Ctrl-C to abort the boot sequence"
pause 1

to the boot env. Which should be ok since Ctrl-C is unlikely to be in the garbage.

[olajep]

@smunaut
How often do you see this?

[olajep]

@afaerber
I think you've mentioned the same issue to me. But I was under the impression this was with the stock flash image?

Boot delay in default image is already set to 0. Maybe -2 is the correct value then?

#define CONFIG_BOOTDELAY  0 /* -2 to autoboot with no delay and not check for abort */

https://github.com/parallella/parallella-uboot/blob/parallella-gen1/include/configs/parallella.h#L77

[smunaut]

How often ? Well everytime pretty much. It just won't boot if my serial cable isn't connected.

[afaerber]

@olajep: I set the bootdelay environment variable to something like 3 with the stock firmware. The trick for doing so was powering on without an SD card inserted, then the default boot fails, dropping back to a prompt, where setenv and saveenv can be used to modify the environment.

My assumption was that the RX pin is incompletely configured by U-Boot. It probably needs to be configured to have a safe value by default.

[olajep]

Ok, then it seems CONFIG_BOOTDELAY = 0 will work.
As I mentioned in the first post I think we can have almost the same functionality but the user will have to press Ctrl-C instead of the any-key.

Thanks,
Ola

[afaerber]

You really should fix the cause of this, or the next input after U-Boot (e.g., grub2 boot menu with any-key timeout) may be affected just as well.

Ctrl-C does not seem to be a common thing in U-Boot, is there a config to enable such behavior or would you be hacking that in yourself? Deviating from other U-Boot boards/platforms would not be good.