• Content Count

  • Joined

  • Last visited

About boobypi

  • Rank
    Advanced Member

Recent Profile Visitors

1648 profile views
  1. If data need to be recorded network boot with nfs will be needed but if it's just to run an small emmbedded project, it's possible to load rootfs in ramdisk and remove the sdcard in case you don't use a spi flash to boot. It's work fine for sure with openwrt but armbian is too big to fit in ram
  2. Uboot Software is a bit deceiving for now, as example : they release an gmac driver but without phy driver and no clocks tree for gmac driver available. No documentation about clock tree configuration, internal PHY is really bad, no chip ref seriously, not well configured for aneg but using init configuration from an old amlogic phy driver (*1) is working a lot better (when you plug a cable you have a link, basicaly )...arm make new with old but they didn't tell it, just fuck. *1 Fixin
  3. Maybe it's just an issue with miniloader at 0x40 or the shity trust.img - this thing make a 4gb file to write 4MB and i don't understand how it's a feature (i can modify uboot without changing trust.img... :/ ) . On my RK3328 4GB device i wasn't able to boot with the ayufans uboot build script but i'm able to boot using ayufans uboot with rockchip build script. Maybe wrong timing for RAM?
  4. In case of brick, there is 2 pad bottom emmc that can be shorted with a 10Ohm resistor or whatever near from you to put the box in maskrom mode (tested without problem). In maskrom mode you will need to load usb loader to do anything. Basicaly i done these steps mkdir rockchip/ cd rockchip/ git clone git clone git clone sudo apt install gcc-aarch64-linux-gnu git-core gitk git-gui gcc-arm-linux-gnueabihf u-boot-tools //make uboot image ./ rk3
  5. Hello, Just some word to know MX10 RK3328 can have an uboot legacy 4.4 working in emmc with the defaut rk3328-evb board config. I follow the guide [RK3328_Linux-Debian_V1.1_Development_Guide-20170711.pdf]. I suggest before trying anything to be sure you have an working usb loader for your BOX (usb loader from rkbin github don't work for example). You can find it in android update firmware image, unpack it with And try on box in recovery mode : To remenber information about your emmc (in case it show 0MB capacity) Be carefull with the
  6. Or put an unused gpio pin for kernel start and drive PL12 manualy as gpio after startup to turn on usb device. Interresting for power saving
  7. Here After read some comments at, mali400 have different implementation (nexell mali 400 != allwinner mali 400)
  8. Maybe i tell bullshit but i saw a kernel4.4 driver for mali400 released with NanoPi Fire2A & Fire3 Boards.
  9. Do you know your link with comment reference isn't working in firefox? I have to check the share button to see proposed url and find the tutorial Maybe it's more simple to make an pdf or a quote like this :
  10. Well u are right, i misreading first page, sorrye Plz share a link to the tutorial, i don't find it
  11. Hello Just to understand a little bit can we use the binary libmali with lastest kernel with patch (Myy) or it 's necessary to start from 4.4 kernel and port mainline patches to 4.4 kernel? I buy an rk3328 device only because it's seem there is an kernel - not prehistoric - with gpu available but after some read i find documentation poor and community less active (in number) than sunxi linux team. I hope to be able to compile QT5 webkit with gpu mesa dependancy but maybe it's very early to dream about it A link to Myy tutorial (RK3288) if already exist need to be under light ^^
  12. The only good reason in my opinion is for usb protocol reverse engineering with a low cost usb packet analyser (usb 12mbit).
  13. Hi mdel, I ask if the weird "sdmmc0m1-pwren" instead SDMMC0_DET isn't the power enable pin for wlan-bluetooth module
  14. Maybe you can check a big file copy from sdcard to android emmc to see speed throughtput and maybe confirming sdcard socket is spi wired (lower speed than real sdmmc controller)
  15. example of command (tested on OP PC) to boot openwrt in ram from a tftp server (sharing dtb, uimage and rootfs) : setenv ipaddr 192.168.x.x setenv serverip 192.168.x.x setenv netmask setenv kernel_addr_r 0x42000000 setenv fdt_addr_r 0x43000000 setenv ramdisk_addr_r 0x43300000 setenv rootfsaddr 0x43300000 setenv tftpLoadUBoot tftpboot 0x42000000 openwrt-sunxi-uImage setenv tftpLoadDTB tftpboot 0x43000000 dtb setenv tftpLoadROOTFSRAM tftpboot 0x43300000 openwrt-sunxi-root.ext4 setenv tftpLoadCMD run tftpLoadUBoot tftpLoadDTB tftpLoadROOTFSRAM setenv bootargs console=ttyS0,1152