Jump to content

overlays=w1-gpio spi-spidev are not working anymore since upgrade to 4.19.13-sunxi


heimworker

Recommended Posts

Hi, my overlays=w1-gpio spi-spidev are not working anymore since I upgraded from 4.14.84-sunxi to 4.19.13-sunxi (Banana Pi with armbian 5.70).

Regarding the 1-wire protocol cat /sys/bus/w1/devices/*/w1_slave responds "No such file or directory" since the upgrade.

Also regarding the spi overlay  # ls /dev/spi* should result in  /dev/spidev0.0 whereas kernel 4.19 says "cannot access /dev/spi*: No such file or directory".

All was working fine with the 4.14 kernel.

thanks in advance

 

Link to comment
Share on other sites

Sorry that it took so long, but serial boot debugging there is misleading info out there, like at http://linux-sunxi.org/LeMaker_Banana_Pi.

In opposite of what is drawn there, I found UART0 wired to J11 (1x2 header). Also the baud rate is 115200 and not 9600 as other sites suggest.

So I also tried to get w1-wire and spi working with kernel 4.19.13 using a new installation (Armbian_5.69_Bananapi_Debian_stretch_next_4.19.13.img) - showing the same results.

 

Here is my boot-output:

U-Boot SPL 2018.05-armbian (Jan 09 2019 - 16:25:26 +0100)                                                   
DRAM: 1024 MiB                                                                                              
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2                                                                        
Trying to boot from MMC1                                                                                    
U-Boot 2018.05-armbian (Jan 09 2019 - 16:25:26 +0100) Allwinner Technology                                  
CPU:   Allwinner A20 (SUN7I)                                                                                
Model: LeMaker Banana Pi                                                                                    
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
Failed (-5)
Setting up a 720x576i composite-pal console (overscan 32x20)
Error: no valid bmp image at 66000000
In:    serial
Out:   vga
Err:   vga
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c50000
230454 bytes read in 28 ms (7.8 MiB/s)
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3798 bytes read in 24 ms (154.3 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
272 bytes read in 19 ms (13.7 KiB/s)
4948290 bytes read in 308 ms (15.3 MiB/s)
6906880 bytes read in 417 ms (15.8 MiB/s)
Found mainline kernel configuration
40331 bytes read in 76 ms (517.6 KiB/s)
777 bytes read in 131 ms (4.9 KiB/s)
Applying kernel provided DT overlay sun7i-a20-w1-gpio.dtbo
1057 bytes read in 127 ms (7.8 KiB/s)
Applying kernel provided DT overlay sun7i-a20-spi-spidev.dtbo
5925 bytes read in 119 ms (47.9 KiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 44000000
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
tmp_bank=H
tmp_pin=20
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Sorry, I could not convert " 7 20 0>"
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4948226 Bytes = 4.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Ramdisk to 49b47000, end 49fff102 ... OK
   reserving fdt memory region: addr=43000000 size=70000
   Loading Device Tree to 49ad4000, end 49b46fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
?H?Debian GNU/Linux 9 bananapi ttyS0

 

Here is my armbianEnv.txt:

verbosity=1
logo=disabled
console=both
disp_mode=1920x1080p60
overlay_prefix=sun7i-a20
rootdev=UUID=85fff9ba-cebc-4404-98b3-05ec04f392be
rootfstype=ext4
overlays=w1-gpio spi-spidev
param_spidev_spi_bus=0
param_w1_pin=PH20
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

-thanks-

Link to comment
Share on other sites

1 hour ago, heimworker said:

libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
tmp_bank=H
tmp_pin=20
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Sorry, I could not convert " 7 20 0>"

Those errors have been fixed 11 days ago with this commit : https://github.com/armbian/build/commit/592c8bd76b006c64564d88145c867f231e5e3791

Please, take a newer build or do your own build using Armbian scripts : https://docs.armbian.com/Developer-Guide_Build-Preparation/

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines