Rock64 enable 1-wire to read DS18B20 or Dallas temperature sensor


 Share

0

Recommended Posts

How is the 1-wire bus enabled on a Rock64 with Armbian 20.08.17 Bionic? I have enabled the w1-gpio through armbian-config. The /sys/bus/w1/devices/ folder is empty after sudo modprobe w1-gpio and sudo modprobe w1-therm. 

 

Below is what is in the armbianEnv.txt file in the /boot directory.

verbosity=1

bootlogo=false

overlay_prefix=rockchip

rootdev=UUID=cbeeff94-c38d-4a79-b10a-3854a2470be4

rootfstype=ext4

usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

overlays=i2c7 spi-spidev w1-gpio

 

In the /boot/dtb/rockchip/overlay/ directory there is a file rockchip-w1-gpio.dtbo.

 

I have connected the VCC pin of the DS18B20 to 3v3 physical pin 1, ground of the DS18B20 to physical pin 9, data of the DS18B20 to physical 7.

The DS18B20 address and w1_bus_master1 do not appear in the /sys/bus/w1/devices/ folder.

 

What more is required to see the DS18B20 and take readings?

 

I have already connected an 18x2 LCD to i2c and am writing information to the LCD using python.

 

Thank you for the help.

Perry

Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

Good evening. I added the following to /boot/armbianEnv.txt

param_w1_pin=GPIO1_D4

 

This is the armbianEnv.txt contents

verbosity=1

bootlogo=false

overlay_prefix=rockchip

rootdev=UUID=cbeeff94-c38d-4a79-b10a-3854a2470be4

rootfstype=ext4

usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

param_w1_pin=GPIO1_D4

overlays=i2c7 spi-spidev w1-gpio

 

I restarted the Rock64. The w1 directory is not created in the /sys/bus/ directory. I have to run modprobe w1-gpio and/or modprobe w1-therm to see the w1 directory. The /sys/bus/w1/devices/ directory is empty. There is not an address or the w1_bus_master listed.

 

Thank you for your help

Perry

Link to post
Share on other sites

17 hours ago, Perry said:

Thank you for your help

 

Ok ! I've never try this over on Rock64, but I did for some other Rockchip boards.

So, I've just tried and figured out that U-Boot version was not supporting "setexpr" function, so fixup script failed :

 

## Executing script at 0900Unknown command 'setexpr' - try 'help'
Unknown command 'setexpr' - try 'help'
Unknown command 'setexpr' - try 'help'
Unknown '
Unknown command 'setexpr' - tlibfdt fdt_getprop(): FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_BADPATH

 

I will check to see if doing new builds will provided newer U-Boot for this board ...

 

Alternatively, it is possible maybe to workaround by editing main DT instead of using overlay.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

0