Sysdeploy
/
openwrt
2
0
Fork 2
Code Issues Pull Requests 2 Packages Projects Releases Wiki Activity

Support for Waveshare NAS double deck #33

New Issue
Closed
opened 2023-04-11 07:59:59 +00:00 by PeterSurda · 6 comments
PeterSurda commented 2023-04-11 07:59:59 +00:00
Owner
Copy Link

Manufacturer page: https://www.waveshare.com/wiki/CM4-NAS-Double-Deck

  • can be detected (for example for purposes of uci-default) by checking if the output of lspci -d ::106 isn't empty (this detects a PCI(e) SATA controller, which then you can use with opkg install kmod-ata-ahci)
  • needs an RTC driver, looks like it's the same as the official IO board / dualeth
  • needs an additional boot option to support the LCD, but probably no extra dtbo or driver
  • a demo app for controlling the LCD, fan and detect the button presses can be downloaded at https://www.waveshare.com/w/upload/7/73/CM4-NAS-Double-Deck_Demo.zip . It's in python. It needs two pip packages. Unfortunately one of them needs to be compiled with C so I can't install it directly. It would be nice if we has a package for these two (spidev, RPi.GPIO). Alternatively, the GPIO can also be accessed using the python's gpiozero package, but then the code in the demo needs to be refactored to use this library instead. I haven't investigated this in detail but the code doesn't seem to be complex.
  • I need to auto-install a couple of extra packages, but this can be done with uci-defaults and they don't need to be built into the rootfs.
    • smartmontools
    • hdparm
    • fdisk
    • parted
    • kmod-hwmon-drivetemp
    • btrfs-progs
    • kmod-fs-btrfs
    • cryptsetup
Manufacturer page: https://www.waveshare.com/wiki/CM4-NAS-Double-Deck - [ ] can be detected (for example for purposes of uci-default) by checking if the output of `lspci -d ::106` isn't empty (this detects a PCI(e) SATA controller, which then you can use with `opkg install kmod-ata-ahci`) - [x] needs an RTC driver, looks like it's the same as the official IO board / dualeth - [ ] needs an additional boot option to support the LCD, but probably no extra dtbo or driver - [ ] a demo app for controlling the LCD, fan and detect the button presses can be downloaded at https://www.waveshare.com/w/upload/7/73/CM4-NAS-Double-Deck_Demo.zip . It's in python. It needs two pip packages. Unfortunately one of them needs to be compiled with C so I can't install it directly. It would be nice if we has a package for these two (`spidev`, `RPi.GPIO`). Alternatively, the GPIO can also be accessed using the python's `gpiozero` package, but then the code in the demo needs to be refactored to use this library instead. I haven't investigated this in detail but the code doesn't seem to be complex. - [x] I need to auto-install a couple of extra packages, but this can be done with uci-defaults and they don't need to be built into the rootfs. - [x] smartmontools - [x] hdparm - [x] fdisk - [x] parted - [x] kmod-hwmon-drivetemp - [x] btrfs-progs - [x] kmod-fs-btrfs - [x] cryptsetup
lee.miller was assigned by PeterSurda 2023-04-13 07:33:34 +00:00
PeterSurda commented 2023-05-23 06:46:57 +00:00
Author
Owner
Copy Link

RTC driver is the same as "dualeth", just needs slightly different boot config as it's wired to I2C bus 1 instead of 10. The solution is described here as the board in that post appears to be wired the same way: https://forums.raspberrypi.com/viewtopic.php?t=293632#p1845336

Instead of

dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi

it should be

dtoverlay=i2c-rtc,pcf85063a

It doesn't look like there is a way to override it from within the OS once the system has booted.

Not sure how to integrate it the best, should this really be a separate image?

RTC driver is the same as "dualeth", just needs slightly different boot config as it's wired to I2C bus 1 instead of 10. The solution is described here as the board in that post appears to be wired the same way: https://forums.raspberrypi.com/viewtopic.php?t=293632#p1845336 Instead of `dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi` it should be `dtoverlay=i2c-rtc,pcf85063a` It doesn't look like there is a way to override it from within the OS once the system has booted. Not sure how to integrate it the best, should this really be a separate image?
lee.miller commented 2023-05-30 19:11:15 +00:00
Collaborator
Copy Link

RTC driver is the same as "dualeth", just needs slightly different boot config as it's wired to I2C bus 1 instead of 10. The solution is described here as the board in that post appears to be wired the same way: https://forums.raspberrypi.com/viewtopic.php?t=293632#p1845336

Instead of

dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi

it should be

dtoverlay=i2c-rtc,pcf85063a

It doesn't look like there is a way to override it from within the OS once the system has booted.

Not sure how to integrate it the best, should this really be a separate image?

Maybe edit on first boot? Your task description implies a lot of actions to do on the first boot.

> RTC driver is the same as "dualeth", just needs slightly different boot config as it's wired to I2C bus 1 instead of 10. The solution is described here as the board in that post appears to be wired the same way: https://forums.raspberrypi.com/viewtopic.php?t=293632#p1845336 > > Instead of > > `dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi` > > it should be > > `dtoverlay=i2c-rtc,pcf85063a` > > It doesn't look like there is a way to override it from within the OS once the system has booted. > > Not sure how to integrate it the best, should this really be a separate image? Maybe edit on first boot? Your task description implies a lot of actions to do on the first boot.
PeterSurda commented 2023-06-06 06:20:49 +00:00
Author
Owner
Copy Link

Maybe edit on first boot?

I think this is a good backup option. However I'm starting to think a separate image may make it easier to manage the devices, assuming the build time doesn't increase. too much.

Your task description implies a lot of actions to do on the first boot.

Yes, I'm starting to think a separate image may be a better choice.

> Maybe edit on first boot? I think this is a good backup option. However I'm starting to think a separate image may make it easier to manage the devices, assuming the build time doesn't increase. too much. > Your task description implies a lot of actions to do on the first boot. Yes, I'm starting to think a separate image may be a better choice.
PeterSurda commented 2023-06-09 04:52:37 +00:00
Author
Owner
Copy Link

I ticked all the checkboxes that work now. Only thing left to do is support for the LCD.

I ticked all the checkboxes that work now. Only thing left to do is support for the LCD.
PeterSurda commented 2023-10-18 04:48:47 +00:00
Author
Owner
Copy Link

LCD works on ubuntu 22.04. This needs installing:

apt install python3-rpi.gpio python3-spidev
pip3 install pillow
LCD works on ubuntu 22.04. This needs installing: ``` apt install python3-rpi.gpio python3-spidev pip3 install pillow ```
PeterSurda commented 2024-02-17 06:59:43 +00:00
Author
Owner
Copy Link

I'll use this with ubuntu, not needed anymore.

I'll use this with ubuntu, not needed anymore.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
23.05.3
kernel-test
collectd-build-debug
kmod-nvme
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
lee.miller
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Sysdeploy/openwrt#33
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?