Gunjan Gupta

Could you please reproduce the issue and then run `armbianmonitor -u` and share the link for the uploaded logs? I don't have a camera myself and I can't help until I see atleast the full oops message. Edit: Sorry it seems its still too early for me. Didn't saw your attached files. Going through the logs now will update in a bit.

Not a c++ person, but generally speaking you need to call sync after you do the write call to make sure its written to disk. Otherwise it will be help in memory.

@kriptonus Could you please try building an image from https://github.com/viraniac/armbian_build/tree/opi3 and see if that works?

Fix has been merged and will be included in next release.

Created jira for the issue and raised pull request for the same

@Teetoow Looks like uwe5622 is disabled in the current and edge kernel config $ grep CONFIG_SPARD_WLAN_SUPPORT config/kernel/linux-sunxi64-* config/kernel/linux-sunxi64-current.config:# CONFIG_SPARD_WLAN_SUPPORT is not set config/kernel/linux-sunxi64-edge.config:# CONFIG_SPARD_WLAN_SUPPORT is not set config/kernel/linux-sunxi64-legacy.config:CONFIG_SPARD_WLAN_SUPPORT=y you can run the following to try enable the same and then compile the kernel ./compile.sh BOARD=orangepi3-lts BRANCH=edge RELEASE=bookworm kernel-config

@pierre-pretCould you please create and test an image from my branch https://github.com/viraniac/armbian_build/tree/opi3

@schunckt I have taken over the Duo2 maintenance and as part of that have made it a officially supported board. Now it does have official forum as pointed out by Werner above

Hi, Thanks for reporting this. I added a patch to include the missing entries for ethernet to the dts and have created an image with the same. I have not changed the status for ethernet though as using it require hardware that users might not have. So you still have to modify status to okay. Could you please test this image and confirm that its working fine now from ethernet's perspective. Once you confirm that it works, I will raise a pull request to merge the changes to armbian repository. There are also some extra fixes included in the image. The button on nanopiduo2 will be able to resume the device back from suspend state. Also if the device is powered off, it will be possible to restart it by pressing the same button. The power consumption in suspend and poweroff state will also be lower as now we have crust enabled for this board which reduces power consumption

yes, now the pull request is finalised. Unless someone reports any issue, I am not going to make more changes They were not bringing any bad things. But I was trying to reduce changes to minimum and noticed that crust was working fine even without kernel changes. So I just removed them as we don't have to worry about maintaining those changes in the future

Bought a usb multimeter. Powered my board with the power cable connected to usb multimeter and usb multimeter connected to power adapter. Following are my observations Current Armbian image with 6.1.30 kernel. This image doesn't have crust Idle current usage - 0.15 Amps current usage during sleep - 0.09 Amps current usage after poweroff - 0.13 Amps Armbian image with 6.1.33 kernel and Crust. Idle current usage - 0.15 Amps current usage during sleep - 0.00 Amps current usage after poweroff - 0.00 Amps Sleep state was triggered with rtcwake -m mem -s 30 Now I can confirm this is working and reducing the power draw as expected. Thanks everyone for helping on the same.

Moved the code as requested. I went through various config options, not sure I was able to locate a config that enables that kind of output. Does this require code changes in crust or is it already a builtin feature that needs to be enabled?

Alright. some progress on testing. Tried rtcwake command, that gave me a write error I will see what caused this later. My board doesn't have hdmi, so hdmi-cec is out of picture. That leaves me with IR, but the board doesn't have inbuilt IR receiver, but has some gpio pin to interface one. I didn't had an IR receiver so have ordered it and it will likely arrive by Monday. Meanwhile, I enabled DEBUG_MONITOR in the crust config and used that for testing. This gave me access to debug terminal for crust when linux is suspended or powered off. I ran systemctl suspend that stopped linux and dropped me to crust debug console. I pressed w on the crust debug console and it brought back linux from suspended state. I powered off Linux and that too dropped me off to crust debug console. I pressed w and it rebooted the board. So I guess its working the way it was expected. I will also test if the system resumes on IR once that arrives and will try to debug why rtcwake command is not working.

@going Thanks for the review. I will move the changes you have mentioned to sunxi_common and sunxi64_common. The PR is still wip and I would be making more changes as the testing proceeds.

I am using nanopi duo2. I only have this single allwinner board at the moment.

@jernejThanks for replying back. Tried with systemctl suspend and power button connected to ap_reset, the board just reboots both with and without crust. I will try compiling and flashing LibreELEC and will see how that behaves.

@ALIGMSTEN No problem. Thanks for the replying anyways

@c0rnelius How can I check that the board actually powers down and resets properly?

@jernej @ALIGMSTEN Could you please help me with this?

Hi, I am working on enabling crust support in Armbian. A draft version of pull request is here. I have made the changes for the same. With my changes, crust compiles as part of building the image and gets bundled in u-boot. I can also see the following message from U-boot U-Boot 2022.10-armbian (Jun 14 2023 - 13:49:59 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 512 MiB Core: 61 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Starting SCP... Net: SCP/INF: Crust v0.5.10000 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 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 and the following message is present in dmesg output [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: MIGRATE_INFO_TYPE not supported. [ 0.000000] psci: SMC Calling Convention v1.0 So I know that crust is getting loaded. I am not sure how I can test if its working as its supposed to be. I can use some guidance for the same. Thanks in advanced

I was able to narrow down the problem further. This seems to have caused because of net-phy-Support-yt8531c.patch. I am not sure why this patch is causing the issue but removing the stmmac part or changing config for stmmac from y to m solves it.

The upstream 6.1.30 kernel with sunxi_defconfig seems to boot fine. So I think either one of the armbian patches is not working with the upstream change that I mentioned before or there might be some config missing. Trying to find out whats causing the conflict

I have also noticed this issue on nanopi duo2. I tried to find out the cause of it and I think its caused by this upstream commit. I added a revert patch in userpatches/kernel/archive/sunxi-6.1 and compiled an image. Image was able to boot successfully. I am going to investigate a bit more about why its impacting 32bit allwinner boards, and will raise a merge request with the fix once I have it ready