[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Göran Lundberg]

Hi!
I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason 
it isn't autobooting on the SD-card.

Is it possible to get more debug output on the screen console? I don't 
have a serial console at the moment.
The output on the screen is:

Net:   No ehternet found.
starting USB...
USB:    Core Release 2.80a
scanning bus 0 for devices... 4 USB Devices found
        scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:   0
U-Boot>

Shouldn't it mention mmc somewhere in the boot message?

The first command I type on the prompt is always failing, it's not 
outputting anything. Just a new prompt on the next line. The next 
commands i type in are working. Which seems strange.
I got boot.scr set up right, except graphic settings which are wrong. It 
is booting the kernel when I type 'run bootcmd'. But only after I type 
in another command before it.
It seems like it's not detecting the SD-card (mmc0) until I have typed 
anything into the prompt.

Do I have to set any other env variable for it to autoboot? I would have 
printed the output of printenv here, but since I don't have a serial 
console, retyping everything is very time consuming.
printenv seems to have the right settings. It's basically a full console 
screen of variables. It just doesn't seem to load them until I type in 
another command before it.

boot_targets=mmc0 usb0 pxe dhcp
Which seems right to me.

I compiled the latest u-boot from github.

If you need more info please let me know and I'll post it.

Hope that anyone can point me in the right direction here. Would really 
appreciate it.

Regards
Göran Lundberg

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Peter Robinson]

On Fri, Mar 2, 2018 at 10:47 AM, Göran Lundberg <goran@lundberg.email> wrote:
> Hi!
> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason it
> isn't autobooting on the SD-card.
>
> Is it possible to get more debug output on the screen console? I don't have
> a serial console at the moment.
> The output on the screen is:
>
> Net:   No ehternet found.
> starting USB...
> USB:    Core Release 2.80a
> scanning bus 0 for devices... 4 USB Devices found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:   0
> U-Boot>
>
> Shouldn't it mention mmc somewhere in the boot message?
>
> The first command I type on the prompt is always failing, it's not
> outputting anything. Just a new prompt on the next line. The next commands i
> type in are working. Which seems strange.
> I got boot.scr set up right, except graphic settings which are wrong. It is
> booting the kernel when I type 'run bootcmd'. But only after I type in
> another command before it.
> It seems like it's not detecting the SD-card (mmc0) until I have typed
> anything into the prompt.
>
> Do I have to set any other env variable for it to autoboot? I would have
> printed the output of printenv here, but since I don't have a serial
> console, retyping everything is very time consuming.
> printenv seems to have the right settings. It's basically a full console
> screen of variables. It just doesn't seem to load them until I type in
> another command before it.
>
> boot_targets=mmc0 usb0 pxe dhcp
> Which seems right to me.
>
> I compiled the latest u-boot from github.
>
> If you need more info please let me know and I'll post it.
>
> Hope that anyone can point me in the right direction here. Would really
> appreciate it.

I'm seeing the same issues with 2018.03 rc3.

I'm not sure what the issue is and I've not had time to investigate it
further yet, but if you type "boot" and hit enter it should boot,
sometimes you actually have to type it twice. It will boot but I'm not
sure which bits here have causes this regression.

Peter

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Alexander Graf]

On 03/02/2018 08:55 PM, Peter Robinson wrote:
> On Fri, Mar 2, 2018 at 10:47 AM, Göran Lundberg <goran@lundberg.email> wrote:
>> Hi!
>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason it
>> isn't autobooting on the SD-card.
>>
>> Is it possible to get more debug output on the screen console? I don't have
>> a serial console at the moment.
>> The output on the screen is:
>>
>> Net:   No ehternet found.
>> starting USB...
>> USB:    Core Release 2.80a
>> scanning bus 0 for devices... 4 USB Devices found
>>         scanning usb for storage devices... 0 Storage Device(s) found
>> Hit any key to stop autoboot:   0
>> U-Boot>
>>
>> Shouldn't it mention mmc somewhere in the boot message?
>>
>> The first command I type on the prompt is always failing, it's not
>> outputting anything. Just a new prompt on the next line. The next commands i
>> type in are working. Which seems strange.
>> I got boot.scr set up right, except graphic settings which are wrong. It is
>> booting the kernel when I type 'run bootcmd'. But only after I type in
>> another command before it.
>> It seems like it's not detecting the SD-card (mmc0) until I have typed
>> anything into the prompt.
>>
>> Do I have to set any other env variable for it to autoboot? I would have
>> printed the output of printenv here, but since I don't have a serial
>> console, retyping everything is very time consuming.
>> printenv seems to have the right settings. It's basically a full console
>> screen of variables. It just doesn't seem to load them until I type in
>> another command before it.
>>
>> boot_targets=mmc0 usb0 pxe dhcp
>> Which seems right to me.
>>
>> I compiled the latest u-boot from github.
>>
>> If you need more info please let me know and I'll post it.
>>
>> Hope that anyone can point me in the right direction here. Would really
>> appreciate it.
> I'm seeing the same issues with 2018.03 rc3.
>
> I'm not sure what the issue is and I've not had time to investigate it
> further yet, but if you type "boot" and hit enter it should boot,
> sometimes you actually have to type it twice. It will boot but I'm not
> sure which bits here have causes this regression.

I do not see this at all on my RPi3. Maybe it's firmware version 
dependent? Do you happen to have an image that always fails for you?


Alex


U-Boot 2018.03-rc3-00109-g77bba970e2-dirty (Mar 05 2018 - 11:06:36 +0100)

DRAM:  992 MiB
RPI 3 Model B (0xa02082)
MMC:   mmc at 7e202000: 0, sdhci at 7e300000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default 
environment

Failed (-5)
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
USB0:   Core Release: 2.80a
scanning bus 0 for devices... 4 USB Device(s) found
        scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found EFI removable media binary efi/boot/bootaa64.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc at 7e202000.blk...
Card did not respond to voltage select!
Scanning disk sdhci at 7e300000.blk...
Disk sdhci at 7e300000.blk not ready
Found 4 disks
840192 bytes read in 38 ms (21.1 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
## Starting EFI application at 01000000 ...
Welcome to GRUB!

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Peter Robinson]

>>> Hi!
>>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason
>>> it
>>> isn't autobooting on the SD-card.
>>>
>>> Is it possible to get more debug output on the screen console? I don't
>>> have
>>> a serial console at the moment.
>>> The output on the screen is:
>>>
>>> Net:   No ehternet found.
>>> starting USB...
>>> USB:    Core Release 2.80a
>>> scanning bus 0 for devices... 4 USB Devices found
>>>         scanning usb for storage devices... 0 Storage Device(s) found
>>> Hit any key to stop autoboot:   0
>>> U-Boot>
>>>
>>> Shouldn't it mention mmc somewhere in the boot message?
>>>
>>> The first command I type on the prompt is always failing, it's not
>>> outputting anything. Just a new prompt on the next line. The next
>>> commands i
>>> type in are working. Which seems strange.
>>> I got boot.scr set up right, except graphic settings which are wrong. It
>>> is
>>> booting the kernel when I type 'run bootcmd'. But only after I type in
>>> another command before it.
>>> It seems like it's not detecting the SD-card (mmc0) until I have typed
>>> anything into the prompt.
>>>
>>> Do I have to set any other env variable for it to autoboot? I would have
>>> printed the output of printenv here, but since I don't have a serial
>>> console, retyping everything is very time consuming.
>>> printenv seems to have the right settings. It's basically a full console
>>> screen of variables. It just doesn't seem to load them until I type in
>>> another command before it.
>>>
>>> boot_targets=mmc0 usb0 pxe dhcp
>>> Which seems right to me.
>>>
>>> I compiled the latest u-boot from github.
>>>
>>> If you need more info please let me know and I'll post it.
>>>
>>> Hope that anyone can point me in the right direction here. Would really
>>> appreciate it.
>>
>> I'm seeing the same issues with 2018.03 rc3.
>>
>> I'm not sure what the issue is and I've not had time to investigate it
>> further yet, but if you type "boot" and hit enter it should boot,
>> sometimes you actually have to type it twice. It will boot but I'm not
>> sure which bits here have causes this regression.
>
>
> I do not see this at all on my RPi3. Maybe it's firmware version dependent?
> Do you happen to have an image that always fails for you?

2018.03 rc3 with "2018-02-09" firmware (so fairly recent) fails for me.

> Alex
>
>
> U-Boot 2018.03-rc3-00109-g77bba970e2-dirty (Mar 05 2018 - 11:06:36 +0100)
>
> DRAM:  992 MiB
> RPI 3 Model B (0xa02082)
> MMC:   mmc at 7e202000: 0, sdhci at 7e300000: 1
> Loading Environment from FAT... *** Warning - bad CRC, using default
> environment
>
> Failed (-5)
> In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   No ethernet found.
> starting USB...
> USB0:   Core Release: 2.80a
> scanning bus 0 for devices... 4 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> Found EFI removable media binary efi/boot/bootaa64.efi
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> Scanning disk mmc at 7e202000.blk...
> Card did not respond to voltage select!
> Scanning disk sdhci at 7e300000.blk...
> Disk sdhci at 7e300000.blk not ready
> Found 4 disks
> 840192 bytes read in 38 ms (21.1 MiB/s)
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> ## Starting EFI application at 01000000 ...
> Welcome to GRUB!
>

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Jonathan Gray]

On Mon, Mar 05, 2018 at 06:18:59PM +0000, Peter Robinson wrote:
> >>> Hi!
> >>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason
> >>> it
> >>> isn't autobooting on the SD-card.
> >>>
> >>> Is it possible to get more debug output on the screen console? I don't
> >>> have
> >>> a serial console at the moment.
> >>> The output on the screen is:
> >>>
> >>> Net:   No ehternet found.
> >>> starting USB...
> >>> USB:    Core Release 2.80a
> >>> scanning bus 0 for devices... 4 USB Devices found
> >>>         scanning usb for storage devices... 0 Storage Device(s) found
> >>> Hit any key to stop autoboot:   0
> >>> U-Boot>
> >>>
> >>> Shouldn't it mention mmc somewhere in the boot message?
> >>>
> >>> The first command I type on the prompt is always failing, it's not
> >>> outputting anything. Just a new prompt on the next line. The next
> >>> commands i
> >>> type in are working. Which seems strange.
> >>> I got boot.scr set up right, except graphic settings which are wrong. It
> >>> is
> >>> booting the kernel when I type 'run bootcmd'. But only after I type in
> >>> another command before it.
> >>> It seems like it's not detecting the SD-card (mmc0) until I have typed
> >>> anything into the prompt.
> >>>
> >>> Do I have to set any other env variable for it to autoboot? I would have
> >>> printed the output of printenv here, but since I don't have a serial
> >>> console, retyping everything is very time consuming.
> >>> printenv seems to have the right settings. It's basically a full console
> >>> screen of variables. It just doesn't seem to load them until I type in
> >>> another command before it.
> >>>
> >>> boot_targets=mmc0 usb0 pxe dhcp
> >>> Which seems right to me.
> >>>
> >>> I compiled the latest u-boot from github.
> >>>
> >>> If you need more info please let me know and I'll post it.
> >>>
> >>> Hope that anyone can point me in the right direction here. Would really
> >>> appreciate it.
> >>
> >> I'm seeing the same issues with 2018.03 rc3.
> >>
> >> I'm not sure what the issue is and I've not had time to investigate it
> >> further yet, but if you type "boot" and hit enter it should boot,
> >> sometimes you actually have to type it twice. It will boot but I'm not
> >> sure which bits here have causes this regression.
> >
> >
> > I do not see this at all on my RPi3. Maybe it's firmware version dependent?
> > Do you happen to have an image that always fails for you?
> 
> 2018.03 rc3 with "2018-02-09" firmware (so fairly recent) fails for me.

2018.03 rc4 works fine on rpi_3 here with

raspberrypi-firmware
20180221 / 9ab68bf218ffc84423a2591658260676d373259a

MD5 (bcm2710-rpi-3-b.dtb) = e5ee32f0c14cd23c327f1615df5d6bb4
MD5 (bootcode.bin) = 17efaf1c1ef89289168d71cdc8194982
MD5 (fixup.dat) = fe33157cedaf8130fa4587341553b26b
MD5 (start.elf) = 9c98e338a47e242f1726c508e60c4cc7

with 'boot_targets=usb0 mmc0 pxe dhcp' as root is on usb.

U-Boot 2018.03-rc4-00001-gc06b786faf (Mar 06 2018 - 23:30:47 +1100)

DRAM:  948 MiB
RPI 3 Model B (0xa02082)
MMC:   mmc at 7e202000: 0, sdhci at 7e300000: 1
Loading Environment from FAT... OK
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
USB0:   Core Release: 2.80a
scanning bus 0 for devices... 4 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot:  0 

Device 0: Vendor: SanDisk Rev: 1.00 Prod: Ultra
            Type: Removable Hard Disk
            Capacity: 29327.3 MB = 28.6 GB (60062500 x 512)
... is now current device
Scanning usb 0:1...
Found EFI removable media binary efi/boot/bootaa64.efi
82812 bytes read in 90 ms (898.4 KiB/s)
## Starting EFI application at 01000000 ...
Scanning disk mmc at 7e202000.blk...
Card did not respond to voltage select!
Scanning disk sdhci at 7e300000.blk...
Disk sdhci at 7e300000.blk not ready
Scanning disk usb_mass_storage.lun0...
Found 6 disks
>> OpenBSD/arm64 BOOTAA64 0.11
boot> 
booting sd0a:/bsd: 3990100+592528+580128+806208 [282379+96+463896+246895]=0x845298

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Alexander Graf]

On 03/06/2018 01:55 PM, Jonathan Gray wrote:
> On Mon, Mar 05, 2018 at 06:18:59PM +0000, Peter Robinson wrote:
>>>>> Hi!
>>>>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason
>>>>> it
>>>>> isn't autobooting on the SD-card.
>>>>>
>>>>> Is it possible to get more debug output on the screen console? I don't
>>>>> have
>>>>> a serial console at the moment.
>>>>> The output on the screen is:
>>>>>
>>>>> Net:   No ehternet found.
>>>>> starting USB...
>>>>> USB:    Core Release 2.80a
>>>>> scanning bus 0 for devices... 4 USB Devices found
>>>>>          scanning usb for storage devices... 0 Storage Device(s) found
>>>>> Hit any key to stop autoboot:   0
>>>>> U-Boot>
>>>>>
>>>>> Shouldn't it mention mmc somewhere in the boot message?
>>>>>
>>>>> The first command I type on the prompt is always failing, it's not
>>>>> outputting anything. Just a new prompt on the next line. The next
>>>>> commands i
>>>>> type in are working. Which seems strange.
>>>>> I got boot.scr set up right, except graphic settings which are wrong. It
>>>>> is
>>>>> booting the kernel when I type 'run bootcmd'. But only after I type in
>>>>> another command before it.
>>>>> It seems like it's not detecting the SD-card (mmc0) until I have typed
>>>>> anything into the prompt.
>>>>>
>>>>> Do I have to set any other env variable for it to autoboot? I would have
>>>>> printed the output of printenv here, but since I don't have a serial
>>>>> console, retyping everything is very time consuming.
>>>>> printenv seems to have the right settings. It's basically a full console
>>>>> screen of variables. It just doesn't seem to load them until I type in
>>>>> another command before it.
>>>>>
>>>>> boot_targets=mmc0 usb0 pxe dhcp
>>>>> Which seems right to me.
>>>>>
>>>>> I compiled the latest u-boot from github.
>>>>>
>>>>> If you need more info please let me know and I'll post it.
>>>>>
>>>>> Hope that anyone can point me in the right direction here. Would really
>>>>> appreciate it.
>>>> I'm seeing the same issues with 2018.03 rc3.
>>>>
>>>> I'm not sure what the issue is and I've not had time to investigate it
>>>> further yet, but if you type "boot" and hit enter it should boot,
>>>> sometimes you actually have to type it twice. It will boot but I'm not
>>>> sure which bits here have causes this regression.
>>>
>>> I do not see this at all on my RPi3. Maybe it's firmware version dependent?
>>> Do you happen to have an image that always fails for you?
>> 2018.03 rc3 with "2018-02-09" firmware (so fairly recent) fails for me.
> 2018.03 rc4 works fine on rpi_3 here with

Do you have enable_uart=1 in your config.txt? If you do, it works. If 
you don't, it fails :)


Alex

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Jonathan Gray]

On Tue, Mar 06, 2018 at 02:12:23PM +0100, Alexander Graf wrote:
> On 03/06/2018 01:55 PM, Jonathan Gray wrote:
> > On Mon, Mar 05, 2018 at 06:18:59PM +0000, Peter Robinson wrote:
> > > > > > Hi!
> > > > > > I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason
> > > > > > it
> > > > > > isn't autobooting on the SD-card.
> > > > > > 
> > > > > > Is it possible to get more debug output on the screen console? I don't
> > > > > > have
> > > > > > a serial console at the moment.
> > > > > > The output on the screen is:
> > > > > > 
> > > > > > Net:   No ehternet found.
> > > > > > starting USB...
> > > > > > USB:    Core Release 2.80a
> > > > > > scanning bus 0 for devices... 4 USB Devices found
> > > > > >          scanning usb for storage devices... 0 Storage Device(s) found
> > > > > > Hit any key to stop autoboot:   0
> > > > > > U-Boot>
> > > > > > 
> > > > > > Shouldn't it mention mmc somewhere in the boot message?
> > > > > > 
> > > > > > The first command I type on the prompt is always failing, it's not
> > > > > > outputting anything. Just a new prompt on the next line. The next
> > > > > > commands i
> > > > > > type in are working. Which seems strange.
> > > > > > I got boot.scr set up right, except graphic settings which are wrong. It
> > > > > > is
> > > > > > booting the kernel when I type 'run bootcmd'. But only after I type in
> > > > > > another command before it.
> > > > > > It seems like it's not detecting the SD-card (mmc0) until I have typed
> > > > > > anything into the prompt.
> > > > > > 
> > > > > > Do I have to set any other env variable for it to autoboot? I would have
> > > > > > printed the output of printenv here, but since I don't have a serial
> > > > > > console, retyping everything is very time consuming.
> > > > > > printenv seems to have the right settings. It's basically a full console
> > > > > > screen of variables. It just doesn't seem to load them until I type in
> > > > > > another command before it.
> > > > > > 
> > > > > > boot_targets=mmc0 usb0 pxe dhcp
> > > > > > Which seems right to me.
> > > > > > 
> > > > > > I compiled the latest u-boot from github.
> > > > > > 
> > > > > > If you need more info please let me know and I'll post it.
> > > > > > 
> > > > > > Hope that anyone can point me in the right direction here. Would really
> > > > > > appreciate it.
> > > > > I'm seeing the same issues with 2018.03 rc3.
> > > > > 
> > > > > I'm not sure what the issue is and I've not had time to investigate it
> > > > > further yet, but if you type "boot" and hit enter it should boot,
> > > > > sometimes you actually have to type it twice. It will boot but I'm not
> > > > > sure which bits here have causes this regression.
> > > > 
> > > > I do not see this at all on my RPi3. Maybe it's firmware version dependent?
> > > > Do you happen to have an image that always fails for you?
> > > 2018.03 rc3 with "2018-02-09" firmware (so fairly recent) fails for me.
> > 2018.03 rc4 works fine on rpi_3 here with
> 
> Do you have enable_uart=1 in your config.txt? If you do, it works. If you
> don't, it fails :)

yes, config.txt:

arm_control=0x200
enable_uart=1
device_tree_address=0x100
kernel=u-boot.bin

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Göran Lundberg]

I got it autobooting by adding enable_uart=1 to /boot/config.txt

But it seems like a bug that could be fixed, since it was booting, but
only manually.
Anyone got an idea what might cause this?

But the graphics mode is all wrong. The four raspberrys are purple and
the resolution is extremely low.
In u-boot, the graphics is ok in high resolution, but when booting the
kernel it all changes.
I'm guessing it's got something to do with the device tree not loading
properly.

I finally got a serial console working. Here's the output:

U-Boot 2018.03-rc3-00090-g3990c9d627 (Mar 01 2018 - 15:51:26 +0100)

DRAM:  998 MiB
RPI 3 Model B (0xa02082)
MMC:   mmc at 7e202000: 0, sdhci at 7e300000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

Failed (-5)
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
USB0:   Core Release: 2.80a
scanning bus 0 for devices... 4 USB Device(s) found
        scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
915 bytes read in 4 ms (222.7 KiB/s)
## Executing script at 02000000
switch to partitions #0, OK
mmc0 is current device
4579632 bytes read in 198 ms (22.1 MiB/s)
17794 bytes read in 3 ms (5.7 MiB/s)
Kernel image @ 0x1000000 [ 0x000000 - 0x45e130 ]
## Flattened Device Tree blob at 2effb600
    Booting using the fdt blob at 0x2effb600
    reserving fdt memory region: addr=0 size=1000
    Using Device Tree in place at 2effb600, end 2f002b81

Starting kernel ...

Any idea what is wrong here:

   Loading Environment from FAT... *** Warning - bad CRC, using default environment

I don't have an env file on the SD-card. So how can it give a CRC error?
I tried to use saveenv at the u-boot prompt but i got an infinite
repeating error.
   fsm 1, hsts 00000001

And this line:

   reserving fdt memory region: addr=0 size=1000

Why is addr=0? And size=1000 seems low?
But on the next line the size seems right.

Here's my boot.scr:

setenv fdtfile bcm2710-rpi-3-b.dtb
mmc dev 0
fatload mmc 0:1 ${kernel_addr_r} kernel7.img
fatload mmc 0:1 ${fdt_addr} ${fdtfile}
setenv bootargs earlyprintk console=tty0 root=/dev/mmcblk0p2
rootfstype=ext4 noinitrd rootwait dwc_otg.lpm_enable=0 elevator=deadline
bootz ${kernel_addr_r} - ${fdt_addr}

Any help appreciated!

On 2018-03-02 20:55, Peter Robinson wrote:
> On Fri, Mar 2, 2018 at 10:47 AM, Göran Lundberg <goran@lundberg.email> wrote:
>> Hi!
>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason it
>> isn't autobooting on the SD-card.
>>
>> Is it possible to get more debug output on the screen console? I don't have
>> a serial console at the moment.
>> The output on the screen is:
>>
>> Net:   No ehternet found.
>> starting USB...
>> USB:    Core Release 2.80a
>> scanning bus 0 for devices... 4 USB Devices found
>>         scanning usb for storage devices... 0 Storage Device(s) found
>> Hit any key to stop autoboot:   0
>> U-Boot>
>>
>> Shouldn't it mention mmc somewhere in the boot message?
>>
>> The first command I type on the prompt is always failing, it's not
>> outputting anything. Just a new prompt on the next line. The next commands i
>> type in are working. Which seems strange.
>> I got boot.scr set up right, except graphic settings which are wrong. It is
>> booting the kernel when I type 'run bootcmd'. But only after I type in
>> another command before it.
>> It seems like it's not detecting the SD-card (mmc0) until I have typed
>> anything into the prompt.
>>
>> Do I have to set any other env variable for it to autoboot? I would have
>> printed the output of printenv here, but since I don't have a serial
>> console, retyping everything is very time consuming.
>> printenv seems to have the right settings. It's basically a full console
>> screen of variables. It just doesn't seem to load them until I type in
>> another command before it.
>>
>> boot_targets=mmc0 usb0 pxe dhcp
>> Which seems right to me.
>>
>> I compiled the latest u-boot from github.
>>
>> If you need more info please let me know and I'll post it.
>>
>> Hope that anyone can point me in the right direction here. Would really
>> appreciate it.
> I'm seeing the same issues with 2018.03 rc3.
>
> I'm not sure what the issue is and I've not had time to investigate it
> further yet, but if you type "boot" and hit enter it should boot,
> sometimes you actually have to type it twice. It will boot but I'm not
> sure which bits here have causes this regression.
>
> Peter
>


On 2018-03-02 20:55, Peter Robinson wrote:
> On Fri, Mar 2, 2018 at 10:47 AM, Göran Lundberg <goran@lundberg.email> wrote:
>> Hi!
>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason it
>> isn't autobooting on the SD-card.
>>
>> Is it possible to get more debug output on the screen console? I don't have
>> a serial console at the moment.
>> The output on the screen is:
>>
>> Net:   No ehternet found.
>> starting USB...
>> USB:    Core Release 2.80a
>> scanning bus 0 for devices... 4 USB Devices found
>>         scanning usb for storage devices... 0 Storage Device(s) found
>> Hit any key to stop autoboot:   0
>> U-Boot>
>>
>> Shouldn't it mention mmc somewhere in the boot message?
>>
>> The first command I type on the prompt is always failing, it's not
>> outputting anything. Just a new prompt on the next line. The next commands i
>> type in are working. Which seems strange.
>> I got boot.scr set up right, except graphic settings which are wrong. It is
>> booting the kernel when I type 'run bootcmd'. But only after I type in
>> another command before it.
>> It seems like it's not detecting the SD-card (mmc0) until I have typed
>> anything into the prompt.
>>
>> Do I have to set any other env variable for it to autoboot? I would have
>> printed the output of printenv here, but since I don't have a serial
>> console, retyping everything is very time consuming.
>> printenv seems to have the right settings. It's basically a full console
>> screen of variables. It just doesn't seem to load them until I type in
>> another command before it.
>>
>> boot_targets=mmc0 usb0 pxe dhcp
>> Which seems right to me.
>>
>> I compiled the latest u-boot from github.
>>
>> If you need more info please let me know and I'll post it.
>>
>> Hope that anyone can point me in the right direction here. Would really
>> appreciate it.
> I'm seeing the same issues with 2018.03 rc3.
>
> I'm not sure what the issue is and I've not had time to investigate it
> further yet, but if you type "boot" and hit enter it should boot,
> sometimes you actually have to type it twice. It will boot but I'm not
> sure which bits here have causes this regression.
>
> Peter
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Göran Lundberg]

Yes i did that as I explained in my last message. And now it autoboots.

But why doesn't it autoboot without it?  Why is UART required to autoboot?

If I don't have that line in confg.txt I can manually boot with 'boot' 
'run boot_cmd' without a problem.
So it's not really problem with the boot itself. Just the automatic 
boot. And why doesn't the u-boot command prompt interpret the first 
command that is issued when enable_uart is disabled?

This seems like an issue that could be fixed.

/Göran Lundberg


On 2018-03-06 14:12, Alexander Graf wrote:
> On 03/06/2018 01:55 PM, Jonathan Gray wrote:
>> On Mon, Mar 05, 2018 at 06:18:59PM +0000, Peter Robinson wrote:
>>>>>> Hi!
>>>>>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some 
>>>>>> reason
>>>>>> it
>>>>>> isn't autobooting on the SD-card.
>>>>>>
>>>>>> Is it possible to get more debug output on the screen console? I 
>>>>>> don't
>>>>>> have
>>>>>> a serial console at the moment.
>>>>>> The output on the screen is:
>>>>>>
>>>>>> Net:   No ehternet found.
>>>>>> starting USB...
>>>>>> USB:    Core Release 2.80a
>>>>>> scanning bus 0 for devices... 4 USB Devices found
>>>>>>          scanning usb for storage devices... 0 Storage Device(s) 
>>>>>> found
>>>>>> Hit any key to stop autoboot:   0
>>>>>> U-Boot>
>>>>>>
>>>>>> Shouldn't it mention mmc somewhere in the boot message?
>>>>>>
>>>>>> The first command I type on the prompt is always failing, it's not
>>>>>> outputting anything. Just a new prompt on the next line. The next
>>>>>> commands i
>>>>>> type in are working. Which seems strange.
>>>>>> I got boot.scr set up right, except graphic settings which are 
>>>>>> wrong. It
>>>>>> is
>>>>>> booting the kernel when I type 'run bootcmd'. But only after I 
>>>>>> type in
>>>>>> another command before it.
>>>>>> It seems like it's not detecting the SD-card (mmc0) until I have 
>>>>>> typed
>>>>>> anything into the prompt.
>>>>>>
>>>>>> Do I have to set any other env variable for it to autoboot? I 
>>>>>> would have
>>>>>> printed the output of printenv here, but since I don't have a serial
>>>>>> console, retyping everything is very time consuming.
>>>>>> printenv seems to have the right settings. It's basically a full 
>>>>>> console
>>>>>> screen of variables. It just doesn't seem to load them until I 
>>>>>> type in
>>>>>> another command before it.
>>>>>>
>>>>>> boot_targets=mmc0 usb0 pxe dhcp
>>>>>> Which seems right to me.
>>>>>>
>>>>>> I compiled the latest u-boot from github.
>>>>>>
>>>>>> If you need more info please let me know and I'll post it.
>>>>>>
>>>>>> Hope that anyone can point me in the right direction here. Would 
>>>>>> really
>>>>>> appreciate it.
>>>>> I'm seeing the same issues with 2018.03 rc3.
>>>>>
>>>>> I'm not sure what the issue is and I've not had time to 
>>>>> investigate it
>>>>> further yet, but if you type "boot" and hit enter it should boot,
>>>>> sometimes you actually have to type it twice. It will boot but I'm 
>>>>> not
>>>>> sure which bits here have causes this regression.
>>>>
>>>> I do not see this at all on my RPi3. Maybe it's firmware version 
>>>> dependent?
>>>> Do you happen to have an image that always fails for you?
>>> 2018.03 rc3 with "2018-02-09" firmware (so fairly recent) fails for me.
>> 2018.03 rc4 works fine on rpi_3 here with
>
> Do you have enable_uart=1 in your config.txt? If you do, it works. If 
> you don't, it fails :)
>
>
> Alex
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[U-Boot] RPi3 Not autobooting from SD-card. {Scanned}

[Göran Lundberg]

Can anyone share their working u-boot configuration for RPi3? With a 
working graphics mode and device tree overlay. config.txt boot.scr and 
any other config files you might have.
I'm running a normal Raspbian Stretch lite image with stock 32bit kernel.
I compiled u-boot with |rpi_3_32b_defconfig|

/Göran Lundberg

On 2018-03-06 14:42, Göran Lundberg wrote:
>
> I got it autobooting by adding enable_uart=1 to /boot/config.txt
>
> But it seems like a bug that could be fixed, since it was booting, but
> only manually.
> Anyone got an idea what might cause this?
>
> But the graphics mode is all wrong. The four raspberrys are purple and
> the resolution is extremely low.
> In u-boot, the graphics is ok in high resolution, but when booting the
> kernel it all changes.
> I'm guessing it's got something to do with the device tree not loading
> properly.
>
> I finally got a serial console working. Here's the output:
>
> U-Boot 2018.03-rc3-00090-g3990c9d627 (Mar 01 2018 - 15:51:26 +0100)
>
> DRAM:  998 MiB
> RPI 3 Model B (0xa02082)
> MMC:   mmc at 7e202000: 0, sdhci at 7e300000: 1
> Loading Environment from FAT... *** Warning - bad CRC, using default 
> environment
>
> Failed (-5)
> In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   No ethernet found.
> starting USB...
> USB0:   Core Release: 2.80a
> scanning bus 0 for devices... 4 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> Found U-Boot script /boot.scr
> 915 bytes read in 4 ms (222.7 KiB/s)
> ## Executing script at 02000000
> switch to partitions #0, OK
> mmc0 is current device
> 4579632 bytes read in 198 ms (22.1 MiB/s)
> 17794 bytes read in 3 ms (5.7 MiB/s)
> Kernel image @ 0x1000000 [ 0x000000 - 0x45e130 ]
> ## Flattened Device Tree blob at 2effb600
>    Booting using the fdt blob at 0x2effb600
>    reserving fdt memory region: addr=0 size=1000
>    Using Device Tree in place at 2effb600, end 2f002b81
>
> Starting kernel ...
>
> Any idea what is wrong here:
>
>   Loading Environment from FAT... *** Warning - bad CRC, using default 
> environment
>
> I don't have an env file on the SD-card. So how can it give a CRC error?
> I tried to use saveenv at the u-boot prompt but i got an infinite
> repeating error.
>   fsm 1, hsts 00000001
>
> And this line:
>
>   reserving fdt memory region: addr=0 size=1000
>
> Why is addr=0? And size=1000 seems low?
> But on the next line the size seems right.
>
> Here's my boot.scr:
>
> setenv fdtfile bcm2710-rpi-3-b.dtb
> mmc dev 0
> fatload mmc 0:1 ${kernel_addr_r} kernel7.img
> fatload mmc 0:1 ${fdt_addr} ${fdtfile}
> setenv bootargs earlyprintk console=tty0 root=/dev/mmcblk0p2
> rootfstype=ext4 noinitrd rootwait dwc_otg.lpm_enable=0 elevator=deadline
> bootz ${kernel_addr_r} - ${fdt_addr}
>
> Any help appreciated!
>
> On 2018-03-02 20:55, Peter Robinson wrote:
>> On Fri, Mar 2, 2018 at 10:47 AM, Göran Lundberg 
>> <goran@lundberg.email> wrote:
>>> Hi!
>>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some 
>>> reason it
>>> isn't autobooting on the SD-card.
>>>
>>> Is it possible to get more debug output on the screen console? I 
>>> don't have
>>> a serial console at the moment.
>>> The output on the screen is:
>>>
>>> Net:   No ehternet found.
>>> starting USB...
>>> USB:    Core Release 2.80a
>>> scanning bus 0 for devices... 4 USB Devices found
>>>         scanning usb for storage devices... 0 Storage Device(s) found
>>> Hit any key to stop autoboot:   0
>>> U-Boot>
>>>
>>> Shouldn't it mention mmc somewhere in the boot message?
>>>
>>> The first command I type on the prompt is always failing, it's not
>>> outputting anything. Just a new prompt on the next line. The next 
>>> commands i
>>> type in are working. Which seems strange.
>>> I got boot.scr set up right, except graphic settings which are 
>>> wrong. It is
>>> booting the kernel when I type 'run bootcmd'. But only after I type in
>>> another command before it.
>>> It seems like it's not detecting the SD-card (mmc0) until I have typed
>>> anything into the prompt.
>>>
>>> Do I have to set any other env variable for it to autoboot? I would 
>>> have
>>> printed the output of printenv here, but since I don't have a serial
>>> console, retyping everything is very time consuming.
>>> printenv seems to have the right settings. It's basically a full 
>>> console
>>> screen of variables. It just doesn't seem to load them until I type in
>>> another command before it.
>>>
>>> boot_targets=mmc0 usb0 pxe dhcp
>>> Which seems right to me.
>>>
>>> I compiled the latest u-boot from github.
>>>
>>> If you need more info please let me know and I'll post it.
>>>
>>> Hope that anyone can point me in the right direction here. Would really
>>> appreciate it.
>> I'm seeing the same issues with 2018.03 rc3.
>>
>> I'm not sure what the issue is and I've not had time to investigate it
>> further yet, but if you type "boot" and hit enter it should boot,
>> sometimes you actually have to type it twice. It will boot but I'm not
>> sure which bits here have causes this regression.
>>
>> Peter
>>
>
>
> On 2018-03-02 20:55, Peter Robinson wrote:
>> On Fri, Mar 2, 2018 at 10:47 AM, Göran Lundberg 
>> <goran@lundberg.email> wrote:
>>> Hi!
>>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some 
>>> reason it
>>> isn't autobooting on the SD-card.
>>>
>>> Is it possible to get more debug output on the screen console? I 
>>> don't have
>>> a serial console at the moment.
>>> The output on the screen is:
>>>
>>> Net:   No ehternet found.
>>> starting USB...
>>> USB:    Core Release 2.80a
>>> scanning bus 0 for devices... 4 USB Devices found
>>>         scanning usb for storage devices... 0 Storage Device(s) found
>>> Hit any key to stop autoboot:   0
>>> U-Boot>
>>>
>>> Shouldn't it mention mmc somewhere in the boot message?
>>>
>>> The first command I type on the prompt is always failing, it's not
>>> outputting anything. Just a new prompt on the next line. The next 
>>> commands i
>>> type in are working. Which seems strange.
>>> I got boot.scr set up right, except graphic settings which are 
>>> wrong. It is
>>> booting the kernel when I type 'run bootcmd'. But only after I type in
>>> another command before it.
>>> It seems like it's not detecting the SD-card (mmc0) until I have typed
>>> anything into the prompt.
>>>
>>> Do I have to set any other env variable for it to autoboot? I would 
>>> have
>>> printed the output of printenv here, but since I don't have a serial
>>> console, retyping everything is very time consuming.
>>> printenv seems to have the right settings. It's basically a full 
>>> console
>>> screen of variables. It just doesn't seem to load them until I type in
>>> another command before it.
>>>
>>> boot_targets=mmc0 usb0 pxe dhcp
>>> Which seems right to me.
>>>
>>> I compiled the latest u-boot from github.
>>>
>>> If you need more info please let me know and I'll post it.
>>>
>>> Hope that anyone can point me in the right direction here. Would really
>>> appreciate it.
>> I'm seeing the same issues with 2018.03 rc3.
>>
>> I'm not sure what the issue is and I've not had time to investigate it
>> further yet, but if you type "boot" and hit enter it should boot,
>> sometimes you actually have to type it twice. It will boot but I'm not
>> sure which bits here have causes this regression.
>>
>> Peter
>>
>
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.