Jump to content

Redferne

Members
  • Posts

    29
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Hi, Same problem here. I tried all flavours, vendor, current & edge. No Wifi or BT. Manually installed aic8800-firmware_3.0+git20240327.3561b08f-2_all.deb and aic8800-usb-dkms_3.0+git20240327.3561b08f-2_all.deb from here: https://github.com/radxa-pkg/aic8800/releases Got Wifi and BT working, but it is far from stable. BT works a few minutes and then craps out. Did not test Wifi since I have no use for it.
  2. Hi @maphstra Yes. I'm still trying to keep the fork alive. Please understand that it's is somewhat customized for my use case. I'm only using headless builds and I'm only focusing on having a testbed for 4G/5G modems in the mPCI/M.2 slot. For that reason, I'm building NetworkManager/ModemManager/iperf3 etc directly from github main/master branch and there are also some other tweaks and patches in there. I've never gotten HDMI to work on any SolidRun board, and have not really tried. On the Hummingbard2/Gate (cubox-i) there is a u-boot boot logo working, but once the kernel boots the console never shows up or any life on HDMI. The following two targets/config are the only ones that I'm building: ./compile.sh BOARD=cubox-i BRANCH=edge RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no USE_TORRENT=no EXPERT=yes NO_HOST_RELEASE_CHECK=yes SKIP_BOOTSPLASH=yes ./compile.sh BOARD=hummingboardpulse-imx8q BRANCH=dev RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no USE_TORRENT=no EXPERT=yes NO_HOST_RELEASE_CHECK=yes SKIP_BOOTSPLASH=yes But right now the fork is under maintenance, the builds are not error free just yet. I'll post an update once I've gotten all packages to build.
  3. I'm still keeping a fork alive for the imx8mq Hummingboard Pulse over here: https://github.com/Redferne/build It is geared towards 4G/5G modems in the mPCIe and M.2 slots. It is a CLI only image. The following target is what's being used here: $ compile.sh BOARD=hummingboardpulse-imx8q BRANCH=dev RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no EXPERT=yes _ _ ____ ____ _ _ __ ____ _____ | | | | __ ) | _ \ _ _| |___ ___ (_) \/ \ \/ ( _ ) | |_| | _ \ | |_) | | | | / __|/ _ \ | | |\/| |\ // _ \ | _ | |_) | | __/| |_| | \__ \ __/ | | | | |/ \ (_) | |_| |_|____/ |_| \__,_|_|___/\___| |_|_| |_/_/\_\___/ Welcome to Armbian 21.11.0-trunk Bullseye with Linux 5.14.9-imx8 No end-user support: built from trunk System load: 17% Up time: 0 min Memory usage: 4% of 2.92G IP: 192.168.42.1 192.168.0.200 CPU temp: 84°C Usage of /: 12% of 29G
  4. @nightseas My interest so far was only headless. You can try to build a Desktop target and see what works :-)
  5. Was in dire need of Armbian on my new toy, the HBP with a iMX8Q CPU ;-) The board features dual WWAN (PCIe + M.2) sockets for highspeed 3G/4G/5G modems with a SIM socket. The Debian build from SolidRun did not have any modem drivers enabled in the kernel so there was headache. Wipped up this WIP configuration and it builds and runs with: ``` $ ./compile.sh BOARD=hummingboardpulse-imx8q BRANCH=legacy RELEASE=buster BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no ``` NOTE: It uses the HDMI and LPDDR4 binary blobs from NXP. You will get a prompt during build to accept the license. The board is default configured to boot from SD using the Boot Select DIPs _ _ ____ ____ _ _ __ ____ _____ | | | | __ ) | _ \ _ _| |___ ___ (_) \/ \ \/ ( _ ) | |_| | _ \ | |_) | | | | / __|/ _ \ | | |\/| |\ // _ \ | _ | |_) | | __/| |_| | \__ \ __/ | | | | |/ \ (_) | |_| |_|____/ |_| \__,_|_|___/\___| |_|_| |_/_/\_\___/ Welcome to Armbian buster with Linux 4.19.72-imx8-sr-imx8 System load: 0.41 1.82 1.38 Up time: 29 min Memory usage: 4 % of 2997MB IP: 192.168.10.148 CPU temp: 47°C Usage of /: 18% of 7.1G [ General system configuration (beta): armbian-config ] http://ix.io/27FC
  6. @balbes150 Just build Armbian from your repo, used the aw-h6-tv config and flashed SD. Booted Eachlink H6 Mini and it seems to be working pretty good. Wired network works and I used the console uart mod from here. Made it crash by installing some apt packages. Ooops here:
  7. If you're building 5.4.y, try tag:v5.4.6 instead. I couldn't get latest master to boot properly on this board.
  8. Not sure this a bug, but the following patch made my EMMC revert back to MMC High Speed (26MHz) after failing @ MMC High Speed (52MHz). diff --git a/drivers/mmc/mmc.c b/drivers/mmc/mmc.c index f683b52e..2e01c75f 100644 --- a/drivers/mmc/mmc.c +++ b/drivers/mmc/mmc.c @@ -2139,11 +2143,14 @@ static int mmc_select_mode_and_width(struct mmc *mmc, uint card_caps) if (!err) return 0; error: + pr_debug("error: %d\n", err); mmc_set_signal_voltage(mmc, old_voltage); /* if an error occured, revert to a safer bus mode */ mmc_switch(mmc, EXT_CSD_CMD_SET_NORMAL, EXT_CSD_BUS_WIDTH, EXT_CSD_BUS_WIDTH_1); mmc_select_mode(mmc, MMC_LEGACY); + mmc_set_clock(mmc, mmc->tran_speed, + MMC_CLK_ENABLE); mmc_set_bus_width(mmc, 1); } }
  9. @Panzerknacker What make/model EMMC you got? I have the 128GB which was delivered with the board. It's wierd the EMMC works in Linux but U-Boot SPL has issues. Wondering if there's patch somewhere... Edit: Many hours later... Dug deep into the MMC code in UBoot and it seems there is a bug.. My EMMC will not negotiate success the advertised supported speed/mode (mmc: widths [8, 4, 1] modes [MMC legacy, MMC High Speed (26MHz), SD High Speed (50MHz), MMC High Speed (52MHz), MMC DDR52 (52MHz)] ). UBoot should revert back to the "safer" speed here: mmc.c#L2146, but it seems to be missing a call to mmc_set_clock(). I added the missing call and it successfully reverts back to "MMC High Speed (26MHz)" and EMMC can be read. Board finally boots on EMMC trying mode MMC High Speed (26MHz) width 8 (at 26 MHz) CMD_SEND:6 ARG 0x03b70200 MMC_RSP_R1b 0x00800800 CMD_SEND:13 ARG 0x00010000 MMC_RSP_R1,5,6,7 0x00000900 CURR STATE:4 CMD_SEND:6 ARG 0x03b90100 MMC_RSP_R1b 0x00000800 CMD_SEND:13 ARG 0x00010000 MMC_RSP_R1,5,6,7 0x00000900 CURR STATE:4 CMD_SEND:8 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000900 selecting mode MMC High Speed (26MHz) (freq : 26 MHz) clock is enabled (26000000Hz) CMD_SEND:8 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000900 switch to partitions #0, OK mmc0(part 0) is current device Now booted kernel and the EMMC works perfectly in HS400 ES mode?!?! Welcome to Armbian buster with Linux 5.4.6-rockchip64 System load: 0.00 0.00 0.00 Up time: 1 min Memory usage: 3 % of 3868MB IP: 192.168.0.33 CPU temp: 36°C Usage of /: 2% of 113G root@roc:~# cat /sys/kernel/debug/mmc1/ios clock: 200000000 Hz actual clock: 200000000 Hz vdd: 7 (1.65 - 1.95 V) bus mode: 2 (push-pull) chip select: 0 (don't care) power mode: 2 (on) bus width: 3 (8 bits) timing spec: 10 (mmc HS400 enhanced strobe) signal voltage: 1 (1.80 V) driver type: 0 (driver type B) Oh, and 5.4.7 is no good...
  10. Gave the latest UBoot tag a spin, but it looks much the same: U-Boot TPL 2020.01-rc5-armbian (Jan 03 2020 - 03:07:34) Channel 0: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Channel 1: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB 256B stride 256B stride lpddr4_set_rate: change freq to 400000000 mhz 0, 1 lpddr4_set_rate: change freq to 800000000 mhz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2020.01-rc5-armbian (Jan 03 2020 - 03:07:34 +0100) Trying to boot from MMC2 unable to select a mode mmc_load_image_raw_sector: mmc block read error Trying to boot from MMC2 mmc_load_image_raw_sector: mmc block read error Trying to boot from MMC1 mmc_load_image_raw_sector: mmc block read error SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### Then I tried to build latest master, but I omitted the board-roc-rk3399-pc-fix-disable-hs400.patch and I'm greeted with this (booted from SD). Maybe I'll just call it goodnight
  11. Just freshly minted a Armbian build for this board. It boots just fine from SD card, but when I nand-sata-install to EMMC and power cycle. I'm greeted with this: U-Boot TPL 2019.10-armbian (Dec 28 2019 - 02:48:10) Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2019.10-armbian (Dec 28 2019 - 02:48:10 +0100) Trying to boot from MMC2 unable to select a mode mmc_load_image_raw_sector: mmc block read error Trying to boot from MMC2 mmc_load_image_raw_sector: mmc block read error Trying to boot from MMC1 mmc_load_image_raw_sector: mmc block read error SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### Is this a known issue?
  12. Yes. This exactly what I wanted to achieve, no blobs. But I got the impression while glancing over the U-Boot commits, that ATF was not needed for the TPL+SPL combo. I was wrong 🤣 Thanks for clearing this up 👍
  13. Huge thanks for this! I have one of these boxes just collecting dust. Will it boot an Armbian minted SD or do you need Pheonixcard tricks?
  14. I was trying to get "Option 3: Package the image with TPL" pure U-Boot working without ATF. But it would not boot properly. BTW, why do we need ATF? I'm probably missing something important ☺️
  15. A huge kudos to @piter75 who commited a csc for this board 👍😍 Did not have the time or energy get my efforts to bear fruit. Was probably to focused on getting the U-Boot TPL+SPL combo working. Maybe this board finally gets the love it so desperately needs. Once again. Thank you for Armbian and all the work everyone puts in!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines