Jump to content

denni_isl

Members
  • Posts

    125
  • Joined

  • Last visited

Everything posted by denni_isl

  1. Now it boots Armbian 21.02.1 Focal with Linux 5.10.12-rockchip64 successfully every time from emmc. To those of consern about /dev/mmcblk2boot0 and /dev/mmcblk2boot1 and RPMB partitiones. This is http://trac.gateworks.com/wiki/MMC some info about hardware partitions on some emmc. "man mmc-utils" and "sudo dpkg -L mtd-utils" and man mmc UART
  2. This is strange - "and totally easy going ". After starting the board with bullseye 4.4.213 SD card and then right away starting with fresh 5.4.43-rockchip64 SD card then it all of a sudden did boot up. Then armbian-config - sytem - boot and flash to emmc - but 5.4.43 does not boot now from emmc- same UART messages as from the SD card. Edit: Did boot from 4.4.213 sd card, shut down, remove sd card, reset button, stop u-boot - run bootcmd_mmc1, and 5.4.43 did boot up from emmc. apt update; apt upgrde and reboot now and reboots so it is working. ------------------------------------------- There are always 3 small boot partitions on the mmc and some u-boot there - Boot1: 2019-03-14, version: 1.19 Is it possible to wipe those partitions clean without bricking the firefly-rk3399 board?
  3. The image is Armbian_20.05.1_Firefly-rk3399_focal_curent_5.4.43 - the with rk3399-firefly.dtb - and I did work - but not now ? Armbian bullseye 4.4.213 and rk3399-firefly.dtb does always work - and is just fine image for this board. Just experimenting with newer kernel. This is where it halts - votages and RTL UART
  4. Can confirm that those two images work for firefly-rk3399 - Armbian_20.02.7_Firefly-rk3399_bullseye_legacy_4.4.213 and Armbian_20.05.1_Firefly-rk3399_focal_current_5.4.43.img.xz - from https://archive.armbian.com/firefly-rk3399/archive/ Could not get the newest ones to work from https://www.armbian.com/firefly-rk3399/
  5. The max is still 1800000 - it has something to do with compiling the .dtb - have not looked much into that yet - https://docs.armbian.com/Developer-Guide_User-Configurations/
  6. How can one clock roc-rk3399-pc to 2016000 Armbian 21.02.1 kern 5.10.12 Bullseye - already done armbian-config, Hardware, rk3399-opp-2ghz, boot with sd and cd and sudo mkdir /mnt/mmcblk2 - sudo mount /dev/mmcblk2 /mnt/mmcblk2/boot - ls -alh - in my case after update another one of the image at link was linked wrongly Image or uInitrd - had to remove and ln -s target link again. If it is the same issue.
  7. Just to be informative this is excellent sound output to speakers through ordinary usb on every SBC board https://www.aliexpress.com/item/32809504593.html?spm=a2g0s.9042311.0.0.688a4c4d4jtZa4 It have CM6631A ship and gives the possibility to Coaxial/Optical fiber SPDIF I2S Converter DAC Board 24bit 192khz. Gives a superb sound quality.
  8. The Samsung EVO 250 G did not show up on station -p1 5-10-12-rockchip64 until I did unplug the mezzanine -remove the envm drive and clean the connectors and then plug it all together again and then then /dev/nvme0n1 did show up as expected. Probably some dirt at the connectors on the nvme.
  9. Did do apt update; apt upgrade on rockpro64 today and it did hangs on booting kernel.... Did use UART serial to connect and =>ums 0 mmc 0 - and USB 3 male and USB C male to connect to the USB-C on rockpro64, the emmc came up as a /dev/sda1 on the host computer. Did sudo mount /dev/sda1 /mnt/sda1, cd /mnt/sda1/boot, ls -alh and uInitrd was linked to uInitrd-5-10-12-rockchip65 but Image was wrongly linked to vlinux-4.4.213-rockchip6, then, sudo rm Image, ln -s vmlinuz-5.10.12-rockship64 and reboot and it did boot successfully after the upgrade.
  10. Yes, short the clock to ground, similar to shorting pins 23 and 25 on rockpro64 board. There are also dedicated 4 spi pins on roc-rk3399-pc-plus, they are marked 3V3, WP, CLK, GND. So one might as well sort CLK and GND as pin 6 and 4 on the chip it self.
  11. The board is nanopi-m4v2 and the image is Armbian 21.02.0-trunk Focal with Linux 5.10.13-rockchip64. The problem is that hdmi - resolution 1920x1080@60Hz does only work if I physically connect the hdmi to nanopi-m4v2 AFTER I see "Starting kernel ..." in the UART serial console terminal. What I have understood is that hdmi of the new u-boot does conflict with the hdmi of the kernel. This is probably a bug in u-boot so the workaround would be to compile u-boot without hdmi support. How can one compile u-boot and apply the newly compiled u-boot to armbian on the emmc with those modification? Something like this maybe https://www.olimex.com/wiki/ArmbianHowTo Perhaps this to adapt the compiled image to emmc - sudo dd if=u-boot-with-spl.bin of=/dev/sdX seek=16 conv=sync
  12. Did "brick" rokpro64 and there is a workaround there to disable spi, jumper on pin 23 and 25 release the jumper to boot from sd or mmc. Just want to put it here for those who are flashing the gd25q128 spi with programmers, to unplug all extra electrical connections from the board UART serial adapter, lan and the power cord. Did get error messages from the programmer software for the EZP201+ "programmer - flash check error address 0h" and no writing to the spi few times. Did then eventually flash the same u-boot-rokchip.bin (8.8 MiB image) that I dis use for flashing roc-rk3399-pc to flash the rockpro64. It seems to be enough to get one up and going if he bricks rk3399 spi.
  13. Is it right understood that ATF (Arm Trusted Firmware) is necessary for u-boot to function by it self as a mini kernel to recognize all the necessary hardware by it self on various embedded devices? What is the purpose of having multiple bl* - bl31,bl32 bl2u * ? - ma - you define the platform (PLAT) and then other hardware support you chose through bl31? I can see that plat directory is under trusted-firmware-a/plat/rockchip/rk3399/
  14. This was the missing link. Now the spi boot work like a charm (have not tried yet to boot from nvme). => run bootcmd_mmc1 (sd) - with balbes150 bullseye image from https://users.armbian.com/balbes150/arm-64/ boots without a problem and supposedly also from NVME and USB. Some research; https://duckduckgo.com/?q=bl31+uboot&t=newext&atb=v255-3__&ia=web http://u-boot.10912.n7.nabble.com/SPL-load-ARM-Trusted-Firmware-BL31-td269471.html Are you familiar with this warning? - *** Warning - bad CRC, using default envirt This is the boot log.
  15. Ok lets tell my story of successfully flashing SPI with a Chinese programmer. This is for educational purpose for others in similar situation. Had done armbian-config, system, install to/update bootloader, install/Update the bootloader on SPI Flash roc-rk3399-pc-plus board and that did completely brick the board. Prior to that I had ordered EZP2019 flasher kit from https://www.aliexpress.com/item/33042726404.html?spm=a2g0s.9042311.0.0.491a4c4dxKfJuf for 20$. Witch turned out to be fortunate. Compiled u-boot-2021-01 according to Panzerknacker advice as a had done before and flashed the u-boot-rokchip.bin (8.8 MiB image) to the SPI chip throug my old Windows laptop with the EZP2019+ USB high speed programmer software that was included in the package. Had to chose, Chip - Type = SPI_FLASH, Manufacturer = WINBOUND, Name = W25Q128, Test, AUTO - few attempts because of the fragile connection through the clip. The output from UART serial
  16. Pin 19, 21, 23, 24 are laid out directly to the pins of SPI device on board. spi bus 1 (Function1), although I have never tried this.
  17. It went through paypal at last.
  18. I did try to donate today few time without success. First there was insufficient amount on the card and the I did remove site private protection in firefox, and also enhanced tracking protection (the chield on the left side of the url: bar, still no success. Must be something else, will try again to morrow.
  19. EUREKA! Thank you balbes150 and Panzerknaker - did make my third donatian to armbian through paypal. It did boot successfully from the sd card after - => sf erase 0 0x200000 What is the best way for one to get himself familiar with memory address management. To know offsett and size of memory addresses. It is a bit a Hebrew to me and probably most others. This is a good source of information about practical use of u-boot commands, with examples and explanations. https://www.linuxsecrets.com/xilinx/U-Boot.html
  20. How can one erase the spi with the u-boot command "sf"? Some other useful hardware spesific u-boot info here https://wiki.dh-electronics.com/index.php/COM_iMX6_Bootloader_U-Boot https://www.digi.com/resources/documentation/digidocs/PDFs/90000852.pdf https://www.linuxsecrets.com/xilinx/U-Boot.html Did, => sf erase 0 0x200000 SF: 2097152 bytes @ 0x0 Erased: OK =>
  21. I did use your image Armbian_20.11_Arm-64_bullseye_current_5.10.0-rc4.img.xz and it did work perfectly (hdmi through kvm switch and everything else) as a desktop before the compiling and flashing the spi.
  22. Did only change verbosity=7 in armbianEnv.txt on the SD card and the connections are all normal except the hdmi is connected to the Benq 24" through kvm switch I was just interesting in learning about SPI booting process and u-boot in general. The device is just used for the purpose of expanding the knowledge of the technology that is shaping the modern world. So there is no special stress factor involved.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines