Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

2186 profile views
  1. You'll find in general lots of SBC's have poor power management. What should be happening is the CPU needs to send the RK808 PMIC the right power off commands before it enters it's halt state. That's probably series of i2c commands and gpio1_a5. If it keeps the power on, it may just be sitting there with the SoC fully powered up, wasting your power. The board vendors don't seem to care much about the problem. If it powers up when you apply power, they think their job is done. In theory there's nothing stopping these systems from entering sleep mode, like your phone or tablet does. They'll last weeks if you set them on airplane mode to disable the wireless and leave them alone. The Raspberry Pi for example, uses almost as much power while "off" as it does then it's idle. The VideoCore CPU in it is fully awake waiting for you to turn it back on with a gpio.
  2. I currently run an Odroid XU4, Odroid HC1 and Rock64 all 24x7. I never have any problems with them. They all run from decent power supplies though, connected to a UPS. The only board I've have stability issues with is an Espressobin. I've also got a Tinkerboard, a couple of Pine64's, Raspberry Pi 2 and 3 and an old Cubietruck. They've all been stable too. Sounds like you need to sort out your power supply problems first.
  3. It should be possible to use a SPI CAN module, as long as you can get the SPI interface enabled and the kernel driver loaded. I imagine you'll need to do something with the device tree to enable it. I don't know if the default kernel has the mcp2515 driver built in though. You may need to compile your own kernel module or kernel. Edit: I see Igor has already posted how to enable SPI
  4. I had kernel panic issues with my Espressobin, when it was functional. It worked best with the 1200/750 firmware. It's probably something to do with memory timing/board layout.
  5. Most SBC's don't have proper power management. As an example of the Raspberry Pi, when you do a software shutdown, the main VideoCore processor is still running, waiting for you to wake it back up with the GPIO pin. When you first apply power, it's not in that state. There is no non-volatile memory to remember the previous state. Power consumption in the soft-off state isn't much lower than idle. In PC's this is stored in the BIOS's battery backed SRAM. The motherboards controller chip (usually some kind of microcontroller, Apple call theirs the "SMC") is what manages the power for the whole system. monitoring the power button, enabling and disabling power rails and resetting the CPU. SBC's don't tend to have that. They just have a PMIC chip and the SoC.
  6. No, but I would start by comparing the DVFS config between the two images. Also the cpufreq governor being used.
  7. I've used it with the original tinkerboard. I just plugged it in to the DSI connector and it worked straight away.
  8. @Jbobspants I think the switch ports are dependent on the eth0 port being up first, maybe it has something to do with timing/ordering?
  9. Why are you trying to bond two ports? There is only a 1Gb link between the switch and the SoC, you're not going to get any more bandwidth
  10. You have to make a choice with the shared SERDES lanes. Espressobin has already made that for you with it's PCB layout - one lane goes to SATA, one to USB3 and one to PCIe. There is only one lane on the PCIe slot, which is also apparently limited to 2.5Gb in early boards due issues running at PCI 2 speeds. The switch is connected via a 1Gb link to the 3270. Your physical limitations will be 2.5* or 5Gb on the PCIe slot and 3Gb on the SATA 2 connection. The 3Gb link uses 8b/10b encoding, so it's limited to 300MB/s. * OpenWRT has reduce PCIe speed to 1.0 https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=772258044b48036699302840abf96cd34c4e5078
  11. The system is fine, cpuinfo shows 4 cores of 0xc0f and 4 of 0xc07 0xc07 is a Cortex-A7 and 0xc0f is a Cortex-A15 What version of htop is it?
  12. Isn't a pi-hole just a DNS server? You don't need multiple interfaces for that, nor do you need gigabit speeds to serve a local network. All you'd need to do would be update the DHCP settings in your router to set the DNS server to that of the pi-hole.
  13. If you have a proper crimping tool for the pin, crimping alone is better than soldering or crimping and soldering. The solder wicks up the stranded wire and creates a point where all the flexing will happen, resulting in easily broken connections.
  14. Have you tried looking at /proc/interrupts to see which cores are actually handling the interrupts?
  • Create New...