akatsuki (NanoPC T4)
Summary
TODO
Notes
TODO
Hardware
| Make | FriendlyElec |
| Year | 2018 |
| Model | NanoPC-T4 |
| Chassis | T4 Metal Case |
| Power Supply | 12V Adapter |
| Processor | Rockchip RK3399 |
| Memory | 4GB DDR4 |
| Ports | USB C 3.0 w/ DP Alt. |
| USB A 3.0 | |
| 2x USB A 2.0 | |
| RJ-45 LAN | |
| HDMI 2.0 | |
| 3.5mm headphone jack | |
| Micro SD | |
| Graphics | - |
| Storage | 16GB eMMC |
| 256GB Inland Premium NVMe SSD | |
| Display | 7" 800x1280 HD702E eDP touch panel |
| Int. Peripherals | UART (1500000 baud) |
| GPIO | |
| 2x MIPI-CSI (4-lane) | |
| MIPI-DSI (4-lane) | |
| eDP | |
| RTL8211E Gigabit Ethernet | |
| AP6389SV 2x2 802.11ac + Bluetooth 4.1 | |
| Ext. Peripherals | 7-in HD702E eDP Touch LCD. 800x1280 |
| Dimensions | |
| Length/Depth | |
| Width | |
| Height/Thickness | |
| Weight | kg (lbs oz) |
Software
| Operating System | |
| Unique applications |
Links
Log
Getting a Debian install working
I followed similar procedure to build the Debian installer as with testament.
The bookworm u-boot package already has targets for nanopc-t4, but it still required adding them to the debian-installer files. The only other major issue I ran into was the installer is set for a newer version of the kernel than is available in bookworm and that made for some confusion when it tried to fetch packages.
With that sorted I built the image and wrote to SD card. The machine was able to boot from the SD card u-boot when I held the MASKROM button and powered it on. The installer kernel did not start the eDP display which is a bit worrying.
Initial attempts at booting were unsuccessful. I did use u-boot-update, and u-boot-install-rockchip to the nvme drive, but the MASKROM button nor RECOVERY made it load that. Android on the eMMC still boots so at least I haven't broken that.
It may require booting from the eMMC storage. The best guide I've found so far is https://github.com/tmountain/arch-nanopct4/ for arch linux, but I haven't searched much yet.
I tried to chroot in from the installer SD card. When I went to write the mmc I kept having write errors. Fdisk failed, mkfs failed, then fsck failed, even u-boot-install-rockchip failed. When I rebooted the machine did load the Debian u-boot, but produced several errors like "FDT_ERR_BADMAGIC", and "FDT_ERR_BADDOFFSET".
I think I'll try a reinstall with / and /boot directly on the eMMC, but I accidentally overwrote my SD card (mmcblk1) thinking it was the built-in eMMC so that is enough for now.
Attempted eMMC workaround
The eMMC issues seems related to an issue with the NanoPC T4 and HS400 mmc device driver. I found this information and a workaround in the device tree here: Armbian NanoPC T4 Kernel MMC issues and this issue: arch-nanopct4 - Errors writing to emmc
I rebuilt u-boot with the &sdhci commented out of rk3399-nanopc-t4.dts. (Using quilt to manage patching). This did not work. dmesg still indicates hs400 is being used. Not sure the installer build is using the dtb from my u-boot package.