Re: [rockchip] broken SPI on RockPro64 and other RK3399 targets

2020-11-10 Thread Simon South
Alper Nebi Yasak writes: > Something else you can test: > - Remove the aliases block from rk3399-rockpro64-u-boot.dtsi > - Add "spi[0-5] = [0-5];" aliases to rk3399-u-boot.dtsi > - Add CONFIG_SF_DEFAULT_BUS=1 to configs/rockpro64-rk3399_defconfig This fixed for me the same issue on my Pinebook

Re: [rockchip] broken SPI on RockPro64 and other RK3399 targets

2020-11-05 Thread Marcin Juszkiewicz
W dniu 05.11.2020 o 17:49, Alper Nebi Yasak pisze: I suspect this change in that commit (rk3399-u-boot.dtsi): / { aliases { mmc0 = mmc1 = pci0 = + spi1 = }; Can you test adding spi0 = above that in the

[rockchip] broken SPI on RockPro64 and other RK3399 targets

2020-11-05 Thread Marcin Juszkiewicz
I wanted to update U-Boot on my RockPro64 board from some random build of 2020.07-rc with out of tree patches to official one. Built, flashed and then got this: Loading Environment from SPI Flash... Invalid bus 0 (err=-19) *** Warning - spi_flash_probe_bus_cs() failed, using default

Re: [rockchip] broken SPI on RockPro64 and other RK3399 targets

2020-11-05 Thread Alper Nebi Yasak
On 05/11/2020 20:04, Marcin Juszkiewicz wrote: > W dniu 05.11.2020 o 17:49, Alper Nebi Yasak pisze: > >> I suspect this change in that commit (rk3399-u-boot.dtsi): >> >>> / { >>> aliases { >>> mmc0 = >>> mmc1 = >>> pci0 = >>> +

Re: [rockchip] broken SPI on RockPro64 and other RK3399 targets

2020-11-05 Thread Alper Nebi Yasak
On 05/11/2020 18:55, Marcin Juszkiewicz wrote: > I wanted to update U-Boot on my RockPro64 board from some random build > of 2020.07-rc with out of tree patches to official one. Built, flashed > and then got this: > > Loading Environment from SPI Flash... Invalid bus 0 (err=-19) > *** Warning -