Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

3905 profile views
  1. OpenWrt has a good Wiki-page about this topic, you may try start reading there: https://openwrt.org/docs/guide-user/network/wan/wwan/start
  2. could be 1500000 as well, see here: https://forum.pine64.org/showthread.php?tid=5029
  3. Unfortunately, HDMI output in u-boot doesn't seem to work at this time. But I have a spare serial connection cable for these kind of devices ...
  4. Both modules have worked in the past (BSP), the red module was made for the C2 while the other came with the N2 developer sample. At this time I'm quite happy that at least one eMMC module is working now. Thank you. Just for the records, you need to write the firmware on emmc starting with sector 1 (instead of sector 0 for µSD): sudo dd if=u-boot-meson.bin of=/dev/XXX conv=fsync bs=512 seek=1
  5. I've tested the 2022.10 GA u-boot. This working for the red coloured eMMC, but the orange coloured eMMC (the faster one) still has the same issue (unable to select a mode : -5).
  6. You'd better go with a fresh Armbian install. The Cubox-I image works for the Utilite Pro as well. Just write the Cubox-i image onto USB or µSD card and modify the u-boot environment in a way mentioned above. If you are afraid to render the Utilite Pro unusable, you can omit the saveenv command and try out the modified environment before you make the change permanent. Before issuing the nand-sata-install command you should modify this shell-script in a way that u-boot can access the filesystem contents during boot. Cheers Uli
  7. You may also ask the people from the odroid forum as well, since this topic doesn't seem to be bound to a specific Linux distribution.
  8. IMHO, µSD should have highest boot priority. You may try this first and check if there are any messages indicating some trouble with emmc storage (u-boot, kernel).
  9. Hi, in addition to this topic I would like to mention that the current Odroid N2 Firmware (Armbian 22.05.0-trunk.0004 Jammy with Linux 5.10.103-meson64 / U-Boot 2022.01-armbian (Mar 03 2022 - 19:25:51 +0000) odroid-n2/n2-plus) as well has difficulties with both the orange and the red coloured eMMC modules at this time. The orange coloured eMMC module is recognised but couldn't be activated ("unable to select a mode : -5"): The red coloured eMMC module cannot be used due to a partition type mismatch (ext4 vs. dos): I don't know if there is already a corresponding Jira issue and/or development activities going on. Cheers Uli PS: odroidn2:~:% sudo armbianmonitor -u System diagnosis information will now be uploaded to curl: (52) Empty reply from server Please post the URL in the forum where you've been asked for.
  10. The u-boot feature set is defined during build-time. IIRC there has been a reason for disabling this feature in the past for certain platforms.
  11. The Utilite Pro has 2GB of RAM only, the Cubox-i has a variant (4x4) with 4 GB. Both share the same imx6 SoC, which is way slower than the Exynos 5422 from the XU4. The Utilite Pro uses an internal msata ssd (which can be replaced), the Cubox-i has an esata connector (both with 3.0 Gbps).
  12. Cool, congrats! Yes, the filesystem uses features u-boot doesn't know about (u-boot is simply too old). You can circumvent this issue by modifying nand-sata-install: upro:build:% diff ./packages/bsp/common/usr/sbin/nand-sata-install /usr/sbin/nand-sata-install 56c56 < if [[ $LINUXFAMILY == mvebu ]]; then --- > if [[ $LINUXFAMILY == mvebu || $LINUXFAMILY == imx6 ]]; then There is already a hook in this script which disables this feature during file-system creation. # for ARMv7 remove 64bit feature from default mke2fs format features if [[ $LINUXFAMILY == mvebu ]]; then mkopts[ext2]='-O ^64bit -qF' mkopts[ext3]='-O ^64bit -qF' mkopts[ext4]='-O ^64bit -qF' else mkopts[ext2]='-qF' mkopts[ext3]='-qF' mkopts[ext4]='-qF' fi Looks like you were trying to implement the distroboot feature within you script. I believe the SATA part should also use the /boot/ prefix ...
  • Create New...