tparys

  • Content Count

    104
  • Joined

  • Last visited

About tparys

  • Rank
    Elite member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The package management tools "dpkg" and "apt" are part of the Debian (and Ubuntu) Linux distributions. If CoreElec does not have apt, it is not a good idea to attempt to install it after the fact. You can run into situations where different package managers do not track each others installed dependencies correctly, potentially overwrite each other's files, and possibly leave your system in a non-working state. If you want a minimal system with the armbian tools, download the armbian images, as they are already minimal Debian/Ubuntu systems with some small quality of life changes.
  2. It looks like the Armbian TV images look like they might be using 5.10.27. The hard part of updating the kernel and u-boot may be done. The remaining work is likely identifying any DTB differences between the 3.x legacy kernel and the more modern 5.10. You can always drop in the old DTB and hope for the best, but I know there have been some format changes over the years to make things more standard and consistent.
  3. https://www.go4b.com/usa/technical-support/product-manuals/t500-hotbus/rs485-wiring-guide.pdf 485 uses differential pair as a both a send and a receive. Both pins are both input and output. There's not really an RX pin unless you convert back to 232. If you take a look at example link. You can have multiple listeners using 485 to 232 converters attached to that differential pair, and may do what you want.
  4. @cracker, I don't think those images that @balbes150 linked to were ready to go for the Radxa Rock, but were probably intended for RK3188 TV boxes. If you tried them and they booted, that's a promising start. However, there's almost certainly substantial board differences (like your LAN), which will need to be reflected in the DTB.
  5. Bunch of examples for sunxi chips: https://github.com/armbian/sunxi-DT-overlays Documentation on how to use them: https://docs.armbian.com/User-Guide_Allwinner_overlays/ And a decent example that does multiple DTS edits (fragments): https://github.com/armbian/sunxi-DT-overlays/blob/master/examples/gpio-button.dts Note that the first fragment selects the target edit point by phandle, where the second selects the target by DTS path.
  6. Not that I have experience with these sensors, but looks like the general flow is this: hit the sensor with a pulse (low/high) count cycles until a response (pulseIn) As it's a microcontroller, pulseIn will probably not return until there is a response. The second call to pulseIn() probably starts counting after you're done printing the value from the first. Considering your output pulses happen within 2-10 ms of each other, I bet this happens: digitalWrite(center_Trig, LOW); digitalWrite(right_Trig, LOW); a=pulseIn(left_Echo, HIGH) / 58.00; Serial.println(a); /
  7. In case there's some sort of rare RK3399 memory issue ... https://forum.armbian.com/topic/16889-nanopi-m4v2-only-2gb-ram-reported/
  8. Sounds like the install to disk probably didn't work smoothly? It may be as simple as copying missing /boot files from your SD card to your disk. Providing armbianmonitor -u on your working HC1 may provide more useful information.
  9. Reason I do that is that I've used this technique to backup (or obliterate) full OS images. If I rsync from an image that doesn't have that new directory, it'll wipe out the mount. If I have the mount in a tmpfs at a known location, that shouldn't happen.
  10. Make your changes to the image before you call rsync? /dev/shm/original is mounted rw unless you tell it otherwise. You monster
  11. Not sure serial transceivers (UARTs) can be configured to pass every bit rate, parity, start/stop bit combination. Maybe better to use a circuit to do this? For RS232 format data, you can always tie the data sender's TX pin to multiple data receiver's RX pins. Just don't tie TX pins together. For RS485 format data, you could have a large number of listeners on the same pins.
  12. Would a USB to quad serial adapter work? Those tend to be consistent boot-to-boot. https://www.amazon.com/dp/B08P24ZQ1B/
  13. As a possible out-of-the-box solution. Have you tried directly mounting the original image, and just rsync'ing that to your partitions? # mkdir /dev/shm/{original,current} # kpartx -av Armbian_21.02.1_Nanopim4v2_focal_current_5.10.12_desktop.img add map loop9p1 (253:0): 0 7258112 linear 7:9 32768 # mount /dev/mapper/loop9p1 /dev/shm/original # mount /dev/mmcblk0p1 /dev/shm/current # rsync -av --delete /dev/shm/{original,current}/ # umount /dev/shm/original # umount /dev/shm/current # sync I didn't try it (for obvious reasons), but that should reset pretty much all log
  14. May be worth reading this thread for some background. May be more work than you might think ... https://forum.armbian.com/topic/17492-newbie-cpu-marvell-armada-370/ My understanding is that the Rockchip CPUs have device unique boot blobs as part of the boot sequence. I believe this would be the only RK3188, so would be a one-off, and may require substantial u-boot or kernel DTB work with the payoff being a somewhat older and under powered board (compared to more recent RK3399). You can certainly leverage the Armbian build system to generate a build for your board, but y