• Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by boobypi

  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 Fixing save env on emmc instead sdcard working No realease log to know what is working and what is will working maybe in next 5 years :/ sometimes i remember some taking about allwinner poor software support, i can say rockchip is same Without USB3 and better hw encoder/decoder h264, best Soc remain H3, if they can make an H3 with USB3, i will never buy another crap soc with crap sw release! But well this device can boot fine from emmc, (no check for the moment about used pins by sdcard socket) and it's can network boot with an old usb ethernet r8152 adapter well supported by uboot. make thing easier to test linux kernel and let closed enclosure!
  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 ./ rk3328-evb //tool for flashing in maskrom mode git clone cd rkdeveloptool/ cat Readme.txt autoreconf -i ./configure make sudo ./rkdeveloptool rd 3 Reset Device OK. sudo ./rkdeveloptool db ../out/u-boot/RK3328MiniLoaderAll_MX10.bin Downloading bootloader succeeded. //editing parameter_gpt file then erasing emmc sudo ./rkdeveloptool ef //writing new partition table sudo ./rkdeveloptool gpt ../parameter_gpt.txt **********GPT Info********** NO LBA Name 00 00000040 loader1 01 00001F80 reserved1 02 00002000 reserved2 03 00004000 loader2 04 00006000 atf 05 00008000 boot 06 00040000 rootfs sudo ./rkdeveloptool wl 0x40 ../out/u-boot/idbloader.img sudo ./rkdeveloptool wl 0x4000 ../out/u-boot/uboot.img sudo ./rkdeveloptool wl 0x6000 ../out/u-boot/trust.img If i remember weel in this state the box don't want to start but wasn't in maskmode, I connect the 2 pads to short Emmc for 1 sec while connecting usb and i upgrade the loader with this cmd : sudo ./rkdeveloptool db ../out/u-boot/RK3328MiniLoaderAll_MX10.bin Downloading bootloader succeeded. sudo ./rkdeveloptool ul ../out/u-boot/RK3328MiniLoaderAll_MX10.bin Upgrading loader succeeded. Now it's booting with console at 1500000
  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 default parameter_gpt file, it's setup 512bytes page size and if you erase you emmc will show 0MB capacity so bad!) sudo ./rkdeveloptool rfi Flash Info: Manufacturer: SAMSUNG, value=00 Flash Size: 29820 MB Block Size: 512 KB Page Size: 2 KB ECC Bits: 0 Access Time: 40 Flash CS: Flash<0> sudo ./rkdeveloptool rd 3 //reboot device in maskrom mode sudo ./rkdeveloptool db RK3328MiniLoaderAll_MX10.bin (extracted from MX10 firmware) Downloading bootloader succeeded. Now you are sure to be able to debrick the box if thing go wrong :) parameter_gpt.txt used FIRMWARE_VER: 6.0.0 MACHINE_MODEL: RK3328 MACHINE_ID: 007 MANUFACTURER: RK3328 MAGIC: 0x5041524B ATAG: 0x00200800 MACHINE: 3328 CHECK_MASK: 0x80 PWR_HLD: 0,0,A,0,1 #KERNEL_IMG: 0x00280000 #FDT_NAME: rk-kernel.dtb #RECOVER_KEY: 1,1,0,20,0 #in section; per section 2048(0x800) bytes <<===== BE CAREFULL with PAGE SIZE BEFORE ERASE CMDLINE: mtdparts=rk29xxnand:0x00001f40@0x00000040(loader1),0x00000080@0x00001f80(reserved1),0x00002000@0x00002000(reserved2),0x00002000@0x00004000(loader2),0x00002000@0x00006000(atf),0x00038000@0x00008000(boot:bootable),-@0x0040000(rootfs) RK3328MiniLoaderAll.bin
  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 ^^ Tks for what is sharing here
  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,115200 mem=512M earlyprintk root=/dev/ram0 rw ramdisk_size=200000 initrd=0x43300000,100M saveenv run tftpLoadCMD bootm 0x42000000 - 0x43000000 - 0x43300000
  16. Thanks for replying, Do you know if i can just copy or dd my new uboot custumized? I have an mainline uboot-orange-pc-sunxi-ith-spl.bin (421.3ko) to write somewhere on sdcard...
  17. Hello, I would like to know if it's possible to put a mainline uboot with ethernet, usb support and lunch the old legacy kernel with it? I need it to be able to boot remotely (tftp) or from usb to make backup, restore without remove sdcard or lunch a recovery mode remotely by lora and a little uC speaking on uart of OPI. With mainline uboot it's easy to lunch openwrt on a ramdisk without mounting sdcard. If i can do the same (mainline uboot) with legacy kernel, i m happy. Thanks
  18. According to this - always some issues -
  19. Equation for board with SDIO wlan and bluetooth, no gmac: the SDIO module is wired with a full uart RTS CTS (UART0 | UART1) for Bluetooth and a sdmmc (SDMMC0 | SDMMC1 | SDMMC0_EXT). UART1 is multiplexed with SDMMC0_EXT. UART2 has a pin switch (UART2-0 | UART2-1). UART2-1 isn't multiplexed with SDMMC0. SDMMC0 available. UART2-0 is multiplexed with SDMMC0. SPI2 is multiplexed with SDMMC0_EXT. I see four possibilities : - The console is UART2-0 (multiplexed with SDMMC0). SDMMC0_EXT and SDMMC1 are dedicated to the SDIO module. Boot possible with an SDMMC0 sdcard but loss of the UART2 console. => (maybe an idea about bug boot with uart connected) - The console is UART2-1 (not multiplexed with SDMMC0). UART1 (disable SDMMC0_EXT) for serial bluetooth, SDMMC1 and SDMMC0 are dedicated to the SDIO module and SD socket. Boot possible with an SDMMC0 sdcard. - The console is UART2-1 (not multiplexed with SDMMC0). UART0 for serial bluetooth, SDMMC1, SDMMC0 and SDMMC0_EXT can be dedicated to the SDIO module and SD socket. Boot possible with an sdcard if SDMMC0 is available on sd socket. Boot possible with an spi nor flash if SDMMC0_EXT is available on sd socket. - The console is UART1 (multiplexed with SDMMC0_EXT). UART0 for Bluetooth, SDMMC1|SDMMC0 for sdio wlan. SDMMC1|SDMMC0 for sd socket. Boot possible with an SDMMC0. - The console is UART0. UART1 (multiplexed with SDMMC0_EXT) for Bluetooth, SDMMC1|SDMMC0 for sdio wlan and SD port. SDMMC1|SDMMC0 for sd socket. Boot possible with an SDMMC0. As information ROCK64 use UART2-1 for serial console. Sorry for brainstorming but it's needed to make the right uboot with output on right serial console
  20. Equation for Z28 PRO with SDIO wlan bluetooth (FN6222B), gmac : the SDIO module is wired with a full uart RTS CTS (UART0 | UART1) for Bluetooth and a sdmmc (SDMMC0 | SDMMC1 | SDMMC_EXT). UART0, SDMMC1 unavailable because multiplexed with GMAC UART1 is multiplexed with SDMMC_EXT. UART2 has a pin switch (UART2-0 | UART2-1). UART2-1 isn't multiplexed with SDMMC0. SDMMC0 available. UART2-0 is multiplexed with SDMMC0. SPI2 is multiplexed with SDMMC_EXT. I see only one possibilitie : UART2-1 is serial console, let available SDMMC0. UART1 is for bluetooth link => SDMMC0_EXT unavailable. As SDMMC1 is unavailable because multiplexed with GMAC, SDMMC0 is for sdio wlan. Next big question is how is wired sdsocket? is it spi wired?
  21. I don't understand this fact, look like hidden information in public datasheet no mention about external sdmmc or alternate pin select, even in rk3399 datasheet... I 'am asking if people try booting Z28 pro with a kill clk on emmc to stard sdcard boot. I supose yes but if yes it's crazy not understandable why z28 pro don't boot on mmc0
  22. For information esp8266 flash/read really fine 16MB flash, save you to make an breadboard with soic nor flash and programing dts and everybody have an soldering iron have an old esp8266 no so far
  23. Just a word to say, finaly i am sure SDIO host don't handle SPI mode - no way to connect CS/SS to sdio interface, so bad. SDcard can work in spi mode but not reverse. Really SDIO has a big potential (bandwidht, low power) but hard to use for hackers. Example there no ethernet chip based on sdio, but lot of wlan - really strange! The way to use sdio0 on rk3328 is soldering sdcard including a working u boot, soldering is easy and safe but not easy to adjust u boot. Soldering sdsocket is weak mecanicaly...maybe an bid sd to microsd is better.