U-boot v2018.05 and RK3288 not working?

[jock]

U-boot is always a great source of amusement, did anyone try that combination?

Just yesterday got v2018.05 in, and it just does not work.

I don't get any serial from u-boot SPL, do I don't know what is happening.

I compiled it with #define DEBUG, and still no serial output at all.

 

At last I downloaded latest mainline u-boot (v2018.07-rc2) from github, applied manually the patches, complied and it worked.

It seems something very specific for v2018.05 and rockchip/rk3288

[TonyMac32]

I tried it last night without any UART connection, it took it about 5 minutes to boot.  So I'm not certain what's going on, I have some other stuff to work on first in any case.

[jock]

Got it. I was concerned I made some mistake due to my particular device. It's confortable to know I'm not the only one experiencing some kind of issues.

Thanks, I hope I will have the chance to look into soon

[TonyMac32]

U-Boot 2018.05-armbian (Jul 02 2018 - 00:54:54 -0400)

Model: Tinker-RK3288
DRAM:  2 GiB
PC event = 0x20
usb connected to SDP, force enter ums mode
rk3288_maskrom_ctrl: enable_emmc = 1
usb_current_limit_ctrl: unlock_current = 1
MMC:   dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0
Loading Environment from EXT4...
** Unable to use mmc 0:auto for loading the env **
Failed (-5)
In:    serial
Out:   serial
Err:   serial
Model: Tinker-RK3288
Net:   failed to enable clock 0
No ethernet found.
UMS: LUN 0, dev 0, hwpart 0, sector 0x0, count 0x1d5a000
\wait for usb get descriptor cmd timeout
rk3288_maskrom_ctrl: enable_emmc = 0
usb_current_limit_ctrl: unlock_current = 0
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
1498 bytes read in 17 ms (85.9 KiB/s)
## Executing script at 00000000
U-boot loaded from eMMC
178 bytes read in 14 ms (11.7 KiB/s)
41042 bytes read in 35 ms (1.1 MiB/s)
4908082 bytes read in 238 ms (19.7 MiB/s)
9272512 bytes read in 433 ms (20.4 MiB/s)
## Loading init Ramdisk from Legacy Image at 21000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4908018 Bytes = 4.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to 0fb51000, end 0ffff3f2 ... OK
   Loading Device Tree to 0fb43000, end 0fb50051 ... OK

gets right to starting kernel.  The delay is the dev kernel I was building.

[jock]

Mmmh, so I guess it's my problem exclusively

Thanks a lot for sharing, gotta go find what the hell happened

[TonyMac32]

9 hours ago, jock said:

Mmmh, so I guess it's my problem exclusively

I'm not so sure of that, are you getting nothing from the serial port at all?

[jock]

8 hours ago, TonyMac32 said:

I'm not so sure of that, are you getting nothing from the serial port at all?

 

I'm using the SPL binary from rockchip which initializes the SDRAM, and it correctly provides the initialization strings. When u-boot kicks in the serial became totally mute. Something happens because u-boot is responsible for the power led and it is actually turned on, but then just hangs at some point without providing any info.

 

 I also tried u-boot v2018.03 and v2018.07-rc3 and both of them work fine with the same compiler and the same config file.

 

[jock]

On 7/3/2018 at 5:20 AM, TonyMac32 said:

gets right to starting kernel.  The delay is the dev kernel I was building.

@TonyMac32 I experienced the absymal performance too with dev kernel (4.18), maybe it is related to this? (I don't see the 0007-... patch applied to dev kernels, I'm currently building the kernel but can't test it till evening. edit: tried the 4.18.0-rc4 kernel with the patch and it seems to work!)

 

In the meantime I give up v2018.05 and go back to working v2018.03, don't want to lose time on an issue which has already been fixed in later u-boot revisions...