sgjava

Running latest Jammy image and trying to attach USB to SATA 3 SSD. I tried two different USB 3 to SATA adapters and they both show up in lsusb: Bus 005 Device 002: ID 2109:0711 VIA Labs, Inc. VL711 SATA 6Gb/s bridge sudo fdisk -l doesn't show drive, but I can plug into my desktop and it mounts disk. Could be related to https://github.com/MichaIng/DietPi/issues/5378

Looks like it's the USB to SATA adapter. https://www.amazon.com/gp/product/B06WVDK9QD doesn't work, but https://www.amazon.com/gp/product/B07S9CKV7X does work. I even tried the Rosewill adapter in a powered hub and it didn't work.

Nothing weird from what I can tell. I ordered another USB3 to SATA adapter. An older XU4 I have has a similar log and it works, but it was installed months ago. Mon Jun 27 07:13:25 PM EDT 2022: Start nand-sata-install. Old UUID: UUID=bc61c55d-8e89-422e-bd96-6bf0901b94ea SD UUID: UUID=bc61c55d-8e89-422e-bd96-6bf0901b94ea SATA UUID: UUID=5e24c2e8-ebaf-4897-bc37-d10cfafb3d47 eMMC UUID: Boot: $1 Root: $2 /dev/sda1 ext4 Usage: 1063 Dest: 227055 /etc/fstab: UUID=bc61c55d-8e89-422e-bd96-6bf0901b94ea / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 /etc/mtab: /dev/mmcblk1p1 / ext4 rw,noatime,errors=remount-ro,commit=600 0 0 /dev/mmcblk1p1 /var/log.hdd ext4 rw,noatime,errors=remount-ro,commit=600 0 0 /dev/sda1 /mnt/nand-sata-install.wwpusQ/rootfs ext4 rw,relatime,stripe=8191 0 0 /dev/zram1 /var/log ext4 rw,relatime,discard 0 0 Files currently open for writing: nfsdcld 701 root 6u REG 179,1 32768 43678 /var/lib/nfs/nfsdcld/main.sqlite vnstatd 1566 vnstat 3u REG 179,1 69632 43683 /var/lib/vnstat/vnstat.db Trying to stop running services to minimize open files: Stopping nfs-mountd.service Stopping nfs-idmapd.service Stopping nfs-blkmap.service Stopping cron.service Checking again for open files: nfsdcld 701 root 6u REG 179,1 32768 43678 /var/lib/nfs/nfsdcld/main.sqlite vnstatd 1566 vnstat 3u REG 179,1 69632 43683 /var/lib/vnstat/vnstat.db Copying 44257 files to /dev/sda1. Finishing transfer to disk, boot from SD/eMMC Checking again for open files: nfsdcld 701 root 6u REG 179,1 32768 43678 /var/lib/nfs/nfsdcld/main.sqlite vnstatd 1566 vnstat 3u REG 179,1 69632 43683 /var/lib/vnstat/vnstat.db Mon Jun 27 07:16:08 PM EDT 2022: Finished

I've tried nand-sata-install on Armbian_22.05.3_Odroidxu4_jammy_current_5.4.199.img and Armbian_22.05.3_Odroidxu4_focal_current_5.4.199.img. Right at the end of running nand-sata-install there's an error. If I try to install anything after nand-sata-install it will hang or the SSD will go into read only mode. To be safe I tested various SD cards and USB to SATA controllers. sed: can't read /boot/boot.cmd: No such file or directory sed: can't read /boot/boot.cmd: No such file or directory Error while creating U-Boot loader image with mkimage umount: /mnt/nand-sata-install.wwpusQ/bootfs: not mounted.

@Keeratiglad to hear that. What properties file did you use with MMIO?

@KeeratiI replied to your post on github. The input file is for MMIO GPIO mappings and not used by LedBlink. Use --help argument on any demo or tool for list of arguments such as gpio chip, pin, etc.

@DorisSmithI'm using https://www.amazon.com/gp/product/B07V8H5QQ1 since they are about the cheapest 4K camera you can get. I have 6 of them in use. Make sure you check the coupon and save $40. Works out to about $70 US. That's the easy part. Setting up a homemade NVR is more difficult, so you may want to look at some of the existing NVR packages out there.

This is a follow up based on running my cameras for a few months. While setting up a new XU4 and copying a file I noticed the same lockup issue. The heartbeat still going but internal and USB NIC dead. I set usbstoragequirks for the SSD drive to u and now I'm able to copy multi-gig files without this issue. Of course SSD performance is less, but I still have plenty of bandwidth. I will monitor long term.

armbianEnv.txt is missing from latest XU4 focal image Armbian_21.08.5_Odroidxu4_focal_current_5.4.159_minimal.img. Should I just create on or use boot.ini?

@lanefuI love the device tree (the one with the boards welded on). I ended up using a storage box with little drawers I got off Amazon and made the cut outs with a rotary tool. This was right after I had it complete. Those Android sticks were quad cores running Linux. That's how I started before most SBCs were sold. Note the active cooling

Java UIO provides high performance Java interfaces for Linux Userspace IO. Java UIO was built from the ground up to use modern kernel APIs, libraries and code generation techniques to provide a best of breed cross platform approach. It does not make sense to recreate the wheel like so many other IO libraries. JDK 17 LTS is supported out of the box. I've been committing code to U8g2 that utilizes the same userspace code at the C level and dramatically improved the performance of HW/SW SPI and I2C in the arm-linux port. I also made the arm-linux port thread safe and multi display capable (you can use this in C as well obviously). It made sense to add modularization to the Java Periphery IO library since I can take advantage of the same code generation techniques. I will continue to wrap optimized C libraries moving forward in the same modular fashion. So now you can develop against IO and small displays with one code base in Java.

OK, so I tried console=none, the getty disable ttyS0 trick, etc. Most of the posts indicate you need to make a change and recompile the kernel. I don't have time for that, but for multi function pins this should work like it did in the previous releases.

@WernerOK, I finally figured this out and it's not my wiring job What's happening is the Duo uses DRX pin (debug receive) for PWM, so if I wire up a LED it will not boot. If I remove that wire it will boot up. After it boots I can connect wire and it will work as expected, so something changed in Armbian_21.08.1_Nanopiduo_focal_current_5.10.60.img. I suspect that no one noticed this unless they were doing hardware PWM, I guess I need to disable serial console?

OK, found root cause. I had a board wired up with all kinds of test devices, loopbacks, etc. My bad, sorry about that. I can fire up debug console now as a result. Still not sure why other version would boot though.

Damn thing booted Armbian_21.08.1_Nanopiduo_focal_current_5.10.60.img. Let me try this on the board I had an issue with and the same SD card. At least I know how to grab boot log now

OK, have FriendlyElec Matrix USB to TTL logging with working image. Let me try broken one and capture.

OK, let me try the easy way with USB UART, but I also found I have a https://www.friendlyarm.com/index.php?route=product/product&product_id=178 kicking around. Give's me a use for it if easy method doesn't work. And good thing I have 4 Duos because 3 are already on breadboards in use.

So on a normal boot I can putty into Duo using USB serial. Are you saying I need adapter that uses debug pins? i.e. https://www.cnx-software.com/2017/10/30/nanopi-duo-quick-start-guide-ubuntu-breadboard-mini-shield-msata-ssd

Armbian_21.05.1_Nanopiduo_focal_current_5.10.34.img boots (updating via apt upgrade also causes it not to boot any more) Armbian_21.08.1_Nanopiduo_focal_current_5.10.60.img does not When I examine the SD card it hasn't expended from image (makes sense since the heartbeat never starts).

PA18\0PA19 and E12\0PE13 do not seem to map to pins.

Found it in DTB i2c0-pins { pins = "PA11\0PA12"; function = "i2c0"; phandle = <0x1c>; }; i2c1-pins { pins = "PA18\0PA19"; function = "i2c1"; phandle = <0x1d>; }; i2c2-pins { pins = "PE12\0PE13"; function = "i2c2"; phandle = <0x1e>; };

So in armbian-config I can enable /dev/i2c-0 /dev/i2c-1 /dev/i2c-2 but there is only one hardware I2C onboard. Are the other two software driven? If so what pins do you use for SCL and SDA?

How is i2c1 and i2c2 mapped on Nanopi Duo? I can configure in armbian-config, but all the Duo pin diagrams only show i2c0.

How is i2c1 and i2c2 mapped on Nanopi Duo? I can configure in armbian-config, but all the Duo pin diagrams only show i2c0.

Java U8g2 is a high performance library based on U8g2: Library for monochrome displays, version 2. Rather than try to code the JNI by hand I used HawtJNI to generate the JNI wrappers. I also used some custom code to generate the setup methods and font constants. final var u8g2 = U8g2.initU8g2(); // Change this to your actual display U8g2.setupSsd1306I2c128x64NonameF(u8g2, U8G2_R0, u8x8_byte_arm_linux_hw_i2c, u8x8_arm_linux_gpio_and_delay); U8g2.initDisplay(u8g2); logger.debug(String.format("Size %d x %d, draw color %d", U8g2.getDisplayWidth(u8g2), U8g2.getDisplayHeight(u8g2), U8g2. getDrawColor(u8g2))); U8g2.setPowerSave(u8g2, 0); U8g2.clearBuffer(u8g2); U8g2.setFont(u8g2, u8g2_font_t0_15b_mf); U8g2.drawStr(u8g2, 1, 18, "Java U8g2"); U8g2.sendBuffer(u8g2); try { TimeUnit.SECONDS.sleep(5); } catch (InterruptedException ie) { Thread.currentThread().interrupt(); } U8g2.setPowerSave(u8g2, 1); U8g2.done(u8g2);