qualle337

  • Posts

    6
  • Joined

  • Last visited

qualle337's Achievements

  1. Hi, I can confirm having the same problems with CPU freezes. Initially I fixed the problem by setting min CPU frequency = max CPU frequency = 1.4Ghz. This configuration ran very solid. A few days ago I reinstalled my system (due to a different problem) and left the CPU settings on default. I'm now running Kernel 5.10.63-rockchip64. Yesterday I noticed that the system was unresponsive again. Actually the red fault LED was blinking, which I cannot remember that it did before. Unlike documented it was set to trigger on (kernel) panic. Now I set the max CPU frequency to 1.4Ghz, leaving the min CPU frequency at 400Mhz (performance mode). Lets see how this goes... Meanwhile, I'm wondering if anyone heard of an actual fix. Could it actually be a problem with my hardware or is it purely software? And if it is - why are there so little complaints? I mean this system is designed to run 24/7, isn't it? I don't want to complain about Helios64, I'm just trying to understand if there is anything I'm missing out to get around this problem. Many Thanks, Julius
  2. Ohh that's cool - I was actually checking about the PoE capabilities of the W5100 Ethernet Shield but I thought it does not support PoE. How did you manage to power your Arduino? Did you use the same shield?
  3. This is actually a really good idea - especially as I'm using Kubernetes where you prefer your workloads being able to run independent from the host configuration. Thanks for the hint
  4. Yes - looks like you're right! Thanks for pointing me in this direction. I'll update the thread when I found a solution (other than plugging in the Arduino after the boot) in case someone else has similar issues. Cheers, Julius
  5. The Arduino is connected to one of the USB 3.0 Ports
  6. Hello, I've got my Helios64 since a few week now and enjoying it a lot. I've installed k3s on it with various applications. The next step is to install home assistant to control my home. Previously, I've already had a setup with a RaspberryPi with a Arduino Mega connected, that is running the rflink firmware. That way I, can control cheap 433Mhz power switches. The problem is, when I connect the Arduino (acting as a serial input device) to my Helios64, the system does not startup anymore. The following error message is printed on the serial console: WARN halted endpoint, queueing URB anyway. Unexpected XHCI event TRB, skipping... (f5f5deb0 00000000 13000000 04008400) "Synchronous Abort" handler, esr 0x96000010 elr: 000000000025ee28 lr : 000000000025ee28 (reloc) elr: 00000000f7f6fe28 lr : 00000000f7f6fe28 x0 : 0000000000000000 x1 : 00000000000003e8 x2 : 0000000000000040 x3 : 000000000000003f x4 : 00000000f5f5e500 x5 : 0000000000001800 x6 : 0000000000000030 x7 : 000000000000000f x8 : 00000000f5ef09c8 x9 : 0000000000000008 x10: 00000000ffffffe8 x11: 0000000000000010 x12: 00000000000000fc x13: 0000000000000002 x14: 00000000f5ef11e0 x15: 0000000000000021 x16: 00000000f7f6db08 x17: 0000000000000001 x18: 00000000f5f08dc0 x19: 00000000f5f5b2c0 x20: 00000000f5ef10c0 x21: 0000000000000000 x22: 00000000f5f6a1d0 x23: 00000000000000ff x24: 0000000080000580 x25: 00000000f5ef0d40 x26: 0000000000000004 x27: 0000000000000001 x28: 00000000f5f6a1d0 x29: 00000000f5ef0a40 Code: 97ffff40 52800401 aa1303e0 97ffffa2 (b9400c00) After this message is printed, the CPU is reset and the system tries to startup again. Does anyone has an idea, what the problem could be? Does the system try to boot from the serial device? I recently upgraded to Kernel 5.10.43, which did not solve the problem. Many thanks for your help in advance Julius