Andrew Pafitis Posted April 24, 2021 Share Posted April 24, 2021 I just got in the new 6.8" super wide BeadaPanel the other day and it's great when it's connected, but sometimes (not always) when coming back from sleep it goes to the screensaver and Aida64 shows "Error: LCD init failed" in the LCD preferences. Disabling and re-enabling BeadaPanel support does nothing, but if I terminate Aida64 and relaunch it reconnects just fine. Attaching some dump files if it helps. Let me know if there's anything else I can provide to help chase down this bug. devdump.txt usbdump.txt Quote Link to comment Share on other sites More sharing options...
Andrew Pafitis Posted April 28, 2021 Author Share Posted April 28, 2021 @Fiery just want to make sure this gets seen, should i open a ticket instead? Quote Link to comment Share on other sites More sharing options...
Andrew Pafitis Posted April 30, 2021 Author Share Posted April 30, 2021 Please help, it seems that this does occur after every time I wake from sleep. The only solution is restarting Aida64. For a $120 panel, I would really like this working as intended. Quote Link to comment Share on other sites More sharing options...
Andrew Pafitis Posted April 30, 2021 Author Share Posted April 30, 2021 whatever, i set up a script to kill and relaunch aida64 and use Hibernate Trigger to launch it on resume from sleep. aida relaunches before the beadapanel fully boots up but it connects straight away when it does. seems to work well. Quote Link to comment Share on other sites More sharing options...
Andrew Pafitis Posted January 26, 2023 Author Share Posted January 26, 2023 i reinstalled windows and tried to reimplement the kill script to force a restart of aida64, but for some reason the kill script doesn't work this time. anyways, @Fiery i found this other post mentioning "lcd init failed" where you asked for a usbdump file so i started poking around. i took a usbdump file when it failed, after restarting aida when it was successfully connected, and after restarting a second time to be sure. i compared values from the 3 files and think believe i understand the problem here. Under the section [ DevClass / USB Devices ] I found that the usb beadapanel device instance ID was logged as 20, however restarting aida64 the usbdump shows an instance id of 19 and is properly connected and displaying stats on my panel. Restarting aida64 the second time, panel connected again, and usbdump also still showing device instance id of 19. I have a whole bunch of usb devices connected through several usb hubs, so I'm not sure of the exact root cause for the IDs to change, but it seems possibly related to usb selective suspend and when the pc wakes from sleep where the usb devices are reconnecting, where it seems the pc reindexes the usb devices (panel now at 19) but aida64 is looking for the index that was saved prior to going to sleep (20), and thus failing. Is there any way to force aida64 to reindex the usb devices after waking from sleep, at some interval, or anything else without having to force a restart of the entire application? usbdump-init failed.txt usbdump-ok.txt usbdump-ok2.txt Quote Link to comment Share on other sites More sharing options...
Fiery Posted February 2, 2023 Share Posted February 2, 2023 On 1/27/2023 at 12:45 AM, Andrew Pafitis said: i reinstalled windows and tried to reimplement the kill script to force a restart of aida64, but for some reason the kill script doesn't work this time. anyways, @Fiery i found this other post mentioning "lcd init failed" where you asked for a usbdump file so i started poking around. i took a usbdump file when it failed, after restarting aida when it was successfully connected, and after restarting a second time to be sure. i compared values from the 3 files and think believe i understand the problem here. Under the section [ DevClass / USB Devices ] I found that the usb beadapanel device instance ID was logged as 20, however restarting aida64 the usbdump shows an instance id of 19 and is properly connected and displaying stats on my panel. Restarting aida64 the second time, panel connected again, and usbdump also still showing device instance id of 19. I have a whole bunch of usb devices connected through several usb hubs, so I'm not sure of the exact root cause for the IDs to change, but it seems possibly related to usb selective suspend and when the pc wakes from sleep where the usb devices are reconnecting, where it seems the pc reindexes the usb devices (panel now at 19) but aida64 is looking for the index that was saved prior to going to sleep (20), and thus failing. Is there any way to force aida64 to reindex the usb devices after waking from sleep, at some interval, or anything else without having to force a restart of the entire application? Thank you for your test runs and the dumps. And the issue is not related to USB device indexing, but rather the way the WinUsb API takes control of the arrival of USB devices after waking the computer up from sleep. Apparently the WinUsb initialization fails if it is called to early after wakeup. We'll implement a cycle to repeat the init procedure 10 times with delays between the trials in a hope that it will provide WinUsb more time to perform the init properly and give control over the BeadaPanel screen to AIDA64 more reliably than now. I will post a message once the new beta build becomes available for download. Quote Link to comment Share on other sites More sharing options...
Fiery Posted February 13, 2023 Share Posted February 13, 2023 @Andrew Pafitis Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Quote Link to comment Share on other sites More sharing options...
beada Posted May 21 Share Posted May 21 I met a similar issue related with Windows sleep/wakeup and BeadaPanel. I am not sure if it is the same cause with the OP but would like @Fiery to have a look into. Every time Windows enter sleep mode, BeadaPanel will go into 'photo album' mode and start to play internal photo/videos. That is all I was expecting, ok. But when Windows wake up from sleep, BeadaPanel is still playing photo/videos though AIDA64 show it was working with BeadaPanel well. I did try to click 'disable' and 're-enable' buttons on AIDA64 GUI but no luck. I have to exit AIDA64 app and then re-launch it to make BeadaPanel to work. Any ideas for how to investigate this issue? Environment: AIDA64 EXTREME: 7.20.6802 BeadaPanel: 6P v7.17 Windows 11 Home 23H2 Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 23 Share Posted May 23 On 5/21/2024 at 8:09 AM, beada said: I met a similar issue related with Windows sleep/wakeup and BeadaPanel. I am not sure if it is the same cause with the OP but would like @Fiery to have a look into. Every time Windows enter sleep mode, BeadaPanel will go into 'photo album' mode and start to play internal photo/videos. That is all I was expecting, ok. But when Windows wake up from sleep, BeadaPanel is still playing photo/videos though AIDA64 show it was working with BeadaPanel well. I did try to click 'disable' and 're-enable' buttons on AIDA64 GUI but no luck. I have to exit AIDA64 app and then re-launch it to make BeadaPanel to work. Any ideas for how to investigate this issue? Environment: AIDA64 EXTREME: 7.20.6802 BeadaPanel: 6P v7.17 Windows 11 Home 23H2 We've checked, and it works fine with our BeadaPanel 5 [NHBC05A] with v5.02 firmware. I suppose the issue could be something you introduced in a newer firmware. Is it possible to update our device to v7.17 firmware? If not, then we'll need to acquire a newer device to have the v7.17 firmware and diagnose the issue. Quote Link to comment Share on other sites More sharing options...
beada Posted May 24 Share Posted May 24 18 hours ago, Fiery said: We've checked, and it works fine with our BeadaPanel 5 [NHBC05A] with v5.02 firmware. I suppose the issue could be something you introduced in a newer firmware. Is it possible to update our device to v7.17 firmware? If not, then we'll need to acquire a newer device to have the v7.17 firmware and diagnose the issue. Thanks for the reply. Had you been able to do the test on a Win11 laptop? My previous test was done on a win11 laptop. To isolate the issues, today I did the same tests on Win7&Win10 desktop machines and results are all ok. This might be clues for further investigation. I'll update here when I dig deeper in it. For the firmware update. Yes there is a tutorial -->v7.10 Upgrade Guidance And here is onedrive link for Firmware Binaries Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 16 Share Posted August 16 On 5/24/2024 at 7:09 AM, beada said: Thanks for the reply. Had you been able to do the test on a Win11 laptop? My previous test was done on a win11 laptop. To isolate the issues, today I did the same tests on Win7&Win10 desktop machines and results are all ok. This might be clues for further investigation. I'll update here when I dig deeper in it. For the firmware update. Yes there is a tutorial -->v7.10 Upgrade Guidance And here is onedrive link for Firmware Binaries I've performed the explained steps to upgrade to the v7.10 firmware, but the device no longer works after the upgrade. I've tried to do it again, from scratch, but still, it doesn't boot up anymore. The blue LED lights up, but nothing shows on the screen and the device doesn't appear as a USB device under Windows. Maybe our device (NHBC05A) isn't compatible with v7.10 firmware? Microcontroller label reads MCIMX6G2CVM05AB, so it seems to be a "6G" device that should be compatible with v7.10. Anyway, we've just ordered a BeadaPanel 6 device to help us diagnose this issue with the latest firmware ready & working. We'd prefer to revert the BeadaPanel 5 device to firmware v5.02. Can you please send us that firmware with files+instructions? Quote Link to comment Share on other sites More sharing options...
beada Posted August 16 Share Posted August 16 47 minutes ago, Fiery said: I've performed the explained steps to upgrade to the v7.10 firmware, but the device no longer works after the upgrade. I've tried to do it again, from scratch, but still, it doesn't boot up anymore. The blue LED lights up, but nothing shows on the screen and the device doesn't appear as a USB device under Windows. Maybe our device (NHBC05A) isn't compatible with v7.10 firmware? Microcontroller label reads MCIMX6G2CVM05AB, so it seems to be a "6G" device that should be compatible with v7.10. Anyway, we've just ordered a BeadaPanel 6 device to help us diagnose this issue with the latest firmware ready & working. We'd prefer to revert the BeadaPanel 5 device to firmware v5.02. Can you please send us that firmware with files+instructions? I am sorry to hear that bad news. Actually the process of revert to v5.02 is almost identical with the process to upgrade to v7.10. I will check if I can prepare a whole disk image for your model 5 and this will save up your time to walk through those provision steps. Will let you know in one or two days. Quote Link to comment Share on other sites More sharing options...
beada Posted August 18 Share Posted August 18 On 8/16/2024 at 11:39 PM, Fiery said: I've performed the explained steps to upgrade to the v7.10 firmware, but the device no longer works after the upgrade. I've tried to do it again, from scratch, but still, it doesn't boot up anymore. The blue LED lights up, but nothing shows on the screen and the device doesn't appear as a USB device under Windows. Maybe our device (NHBC05A) isn't compatible with v7.10 firmware? Microcontroller label reads MCIMX6G2CVM05AB, so it seems to be a "6G" device that should be compatible with v7.10. Anyway, we've just ordered a BeadaPanel 6 device to help us diagnose this issue with the latest firmware ready & working. We'd prefer to revert the BeadaPanel 5 device to firmware v5.02. Can you please send us that firmware with files+instructions? I made a disk image backup for model 5 with a '6G' SOC. It is a pure raw disk image and you can download, uncompress and then write it to BeadaPanel internal eMMC by a Win32 Disk Imager tool. https://drive.google.com/drive/folders/1RtiYVAkGcELBKiPuBfvxqO-zs8FqYQS7?usp=sharing Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 18 Share Posted August 18 4 hours ago, beada said: I made a disk image backup for model 5 with a '6G' SOC. It is a pure raw disk image and you can download, uncompress and then write it to BeadaPanel internal eMMC by a Win32 Disk Imager tool. https://drive.google.com/drive/folders/1RtiYVAkGcELBKiPuBfvxqO-zs8FqYQS7?usp=sharing WinRAR says the file is corrupt Quote Link to comment Share on other sites More sharing options...
beada Posted August 18 Share Posted August 18 4 hours ago, Fiery said: WinRAR says the file is corrupt The first image file was corrupted before upload, 2nd try finished. Please check it again. v717_6G_5_2nd.rar Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 18 Share Posted August 18 43 minutes ago, beada said: The first image file was corrupted before upload, 2nd try finished. Please check it again. v717_6G_5_2nd.rar Thank you! Can you please explain how can I write the .img file to the eMMC using DiskGenius? It doesn't seem to be able to handle the .img file format. Let me know what other Win32 software should I use. With DiskGenius I've tried to open the .img file using Open Virtual Disk File, and then Clone Disk, but the .img file is slightly larger (15360000 sectors) than the eMMC of BeadaPanel 5 (15269888 sectors) and so it cannot clone .img to the eMMC Quote Link to comment Share on other sites More sharing options...
beada Posted August 18 Share Posted August 18 37 minutes ago, Fiery said: Thank you! Can you please explain how can I write the .img file to the eMMC using DiskGenius? It doesn't seem to be able to handle the .img file format. Let me know what other Win32 software should I use. With DiskGenius I've tried to open the .img file using Open Virtual Disk File, and then Clone Disk, but the .img file is slightly larger (15360000 sectors) than the eMMC of BeadaPanel 5 (15269888 sectors) and so it cannot clone .img to the eMMC You can use this tools for image writing. https://sourceforge.net/projects/win32diskimager/ If the image file larger than destination disk size, you can just cut the sectors/clusters at the tail of image file. It is safe. Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 18 Share Posted August 18 39 minutes ago, beada said: You can use this tools for image writing. https://sourceforge.net/projects/win32diskimager/ If the image file larger than destination disk size, you can just cut the sectors/clusters at the tail of image file. It is safe. Thank you, that worked out well. We've tested the device with v7.17 firmware, by putting the computer to sleep and recover from it, 10 cycles, under both Windows 10 and Windows 11, and sadly we couldn't reproduce the issue about recovering from sleep. It worked out well all 20 times. Quote Link to comment Share on other sites More sharing options...
beada Posted August 18 Share Posted August 18 32 minutes ago, Fiery said: Thank you, that worked out well. We've tested the device with v7.17 firmware, by putting the computer to sleep and recover from it, 10 cycles, under both Windows 10 and Windows 11, and sadly we couldn't reproduce the issue about recovering from sleep. It worked out well all 20 times. @Fiery As I mentioned in my previous post, this issue can only be reproduced on my Win11 Laptop machine. It can not be reproduced on desktop machines. I suggest you have a try if you have a laptop on hand. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.