Jump to content

qume

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by qume

  1. @tparys this is very good advice. It seems the problem was the armbianEnv.txt was becoming corrupt, and losing the UUID (and everything else - the file seems to be clobbered with random content) This corruption problem of armbianEnv.txt used to happen all the time, then after an update it stopped happening on all the devices. This device hasn't been updated or modified in any way in a long time, and it happened again. So I guess the frequency of it happening was reduced greatly but the problem persists.
  2. This happened to me too. We have the RockPi 4 embedded in a product so when this randomly happens it bricks it. If anyone has any thoughts as to why it would happen out of the blue that mmcblk0 switches to mmcblk1 out of the blue it would be good to get to the bottom of it Thanks
  3. For the last few years I have been working on some hardware projects based on ARM SBCs. Every board I work with seems to have different kernel/overlay/GPIO/etc issues. So my question is - Which SBC, or chipset, has most complete and stable Armbian support? In other words if you had to pick a board to go into battle to run Armbian, without knowing any specific requirements, which SBC would it be?
  4. Trying to get the serial port working on pins 24 and 26 of the espressobin. I've tried all of the armbian builds, plus building the kernel from the Marvell github repo - various branches. On the 4.4.52 kernels, the serial port on the header pins shows up with port of 0000 and IRQ of 8, but will not work. On the 4.14 kernels, I get port 0000 and IRQ 0, and also doesn't work Has anyone managed to get the serial port working on the header pins 24,26 of the espressobin? I have posted more detail here on the github page but no progress so thought I'd ask here if anyone has had any success with this? Thanks https://github.com/MarvellEmbeddedProcessors/mainline-public/issues/81
  5. For anyone who lands here from a web search trying to get kernel PPS working with the Tinkerboard on armbian. I failed going the overlay route, and also failed to add a new patch to the /userpatches/kernel/rockchip-next/ directory. In both cases I don't have enough experience here to figure out why. But, I did manage to get the device tree item into rt3288.dtsi file by copying one of the files which modify it from /patches/kernel/rockchip-next into the /userpatches/kernel/rockchip-next directory and modifying it. When copying it over, the build system uses any file with the same name from /userpatches instead of /patches. When I say modifying it, I literally added these lines: pps: pps { compatible = "pps-gpio"; pinctrl-names = "default"; pinctrl-0 = <&pps_pins>; gpios = <&gpio5 19 0>; status = "okay"; }; in to one of the patches directly. So you'll need to add +'s to the start of each line then change the number of lines added in the patch chunk header. This is an abomination of course but it worked (along with building the kernel with PPS and PPS GPIO turned on). Perhaps someone with more experience here might chime in on the proper way of doing this. Every time I created a patch it failed without any reason I could track down.
  6. Hi All, first thanks for the great work getting Armbian up and running on the Tinkerboard. It's been rock solid for me. In the TinkerOS repo, they have created an overlay for PPS (1 pulse per second from GPS devices for keeping time): https://github.com/TinkerBoard/debian_kernel/blob/develop/arch/arm/boot/dts/overlays/pps-gpio-overlay.dts I spent the day building Armbian using the vagrant build system, which is working well, but I haven't managed to figure out how to get this overlay integrated. I also created a patch with the core change to rk3288.dtsi in the userpatches/kernel directory but it always fails to apply with not enough explanation for me to figure out why, so no luck there. Apologies if this isn't the right place to be asking this as although I'm trying to do this for the Tinkerboard it probably is a general armbian question.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines