• Content Count

  • Joined

  • Last visited

About gounthar

  • Rank
    Elite member

Profile Information

  • Gender
  • Location
    Seclin, France

Recent Profile Visitors

498 profile views
  1. With the right image, I managed to do the HDMI-IN thingie on this board.
  2. <rant-on> Why in the hell do we have to use that stupid shortening trick to get a Linux image written on the eMMC? Android images can be written under Windows by just using the recovery button (LOADER mode), why can't we do the same for Linux images (MASKROM)? As I wrote quite a few images on this board, the pads worn out, we soldered a pin to make it easier and more durable, which worked for a while... It failed after some time, the testing pad just quit and I am now stuck with a useless board... until a colleague makes another better solder. I know, this was bound to happen, a recipe for catastrophy, but, come on, two small testing pads! I could have gone Armbian the whole way, and avoid that, but I did not know what I would loose with switching u-boot, as I need HDMI-IN, sound in, CSI camera and network. I asked OrangePi if they could make another version with a switch or a jumper, and they answered they could modify if I order 2.000 boards, which I won't (and can't). </rant-on>
  3. Well, the soldering attempt did not go that well, more to follow... I received the SATA cable, and the disk is now seen. I'm currently creating a NTFS partition.
  4. Yes, you're right, thanks for clarifying. Today, we'll try to solder something to the pads so that it gets easier for me to go into maskrom mode.
  5. As I will be using an SSD, I found this connector that will only give 5V. And I still have to try that, I really have to figure out this Msata/pcie/m2 thingie...
  6. I see, thanks. I already have a parent-size Molex Sata power connector, I "just" have to get two tiny weeny Molex connectors, and a little bit of solder I guess. I received today my test heatsink, let's hope it doesn't short anything...
  7. My bad, that's very good news indeed! I had not read that part of the schematics, just read the documentation where it is noted I guessed (wrong) it was another way to power up the board... @Igor: would you happen to have a link to buy the power connector you used (amazon, aliexpress, ...)? Thanks!
  8. Thanks a lot for this info! You are right, with my test, I was using OrangePi's U-boot, not Armbian's! The pads for the shorting are getting worn out, and I would like to get it to boot to the SDCARD with a softer method... Are you using the +5V+12V connectors to power up your SATA disk? I don't get it... Aren't they supposed to be in, not out? I'm still trying to figure out how to power my SSD... For the time being, I'm stuck with the OrangePi Os (even if I rebuild it myself), as I need to have an HDMI-IN solution for the 3rd of July. While I'm there, if I can bring anything from the OrangePi OS for Armbian, please let me know. My goal would be to have one of these days this board with Armbian handling sound-in, sound-out, hdmi-in, IR, Ethernet, OV18350 and WIFI.
  9. So... I somehow managed to compile a kernel for this board, then a whole image, and burned it on a SDCard with Etcher. The problem I have is that I can't make this card boot the SDCard unless I do the shorting trick. I tried what is indicated on the dedicated Armbian download page, but it failed: In: serial Out: serial Err: serial Model: OrangePi RK3399 Board Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 => mmc list dwmmc@fe320000: 1 sdhci@fe330000: 0 (eMMC) => setenv devnum 1 => run mmc_boot mmc_init: -5, time 4 => mmc_init: -5, time 4 ** Bad device mmc 1 ** mmc_init: -5, time 4 ** Bad device mmc 1 ** => => I'm sure I missed something, but what? I have the very same behaviour with the standard Armbian image on the SDCard.
  10. Thanks. I'll try to find something that could be connected to the GPIO.
  11. The OrangePi RK3399 doesn't have that kind of Molex connector, but I will keep searching. Thanks for your help.
  12. How can we power an SSD when using Sata on this board? Is there some kind of power splitter somewhere? I'm using the barrel connector to power the board. Thanks.
  13. After reading this excellent blog post by Dieter Reuter, I said to myself that compiling the kernel on this very same board could be a good idea. I cloned the kernel: git clone https://github.com/orangepi-xunlong/OrangePiRK3399_kernel.git Unfortunately, zcat /proc/config.gz > .config does not work. 1. /proc/config.gz 2. /boot/config 3. /boot/config-$(uname -r) do not work either, I suspect the config extension have not been built for this kernel. sudo modprobe configs modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.103/modules.dep.bin' modprobe: FATAL: Module configs not found in directory /lib/modules/4.4.103 Then, I thought I could get the configuration from the kernel image file. It was nowhere to be found... So, I unzipped the img I flashed on the device on a X86 Linux machine, mounted the boot img sudo mount -t msdos -o loop boot.img /mnt/firmware/ gounthar@maurice:~/Desktop/rk-linux/out$ ll /mnt/firmware/ total 19212 drwxr-xr-x 3 root root 16384 janv. 1 1970 ./ drwxr-xr-x 3 root root 4096 mai 2 16:22 ../ drwxr-xr-x 2 root root 2048 oct. 16 2018 extlinux/ -rwxr-xr-x 1 root root 19568648 oct. 16 2018 image* -rwxr-xr-x 1 root root 78885 oct. 16 2018 rk3399~1.dtb* and it does not work /usr/src/linux-headers-4.18.0-17/scripts/extract-ikconfig /mnt/firmware/image >config extract-ikconfig: Cannot find kernel config. The file command says image is just data. Could it be linked that I'm doing that on a X86 machine? I then transfered the image file to the RK3399 to see if I have a different result: root@linaro-alip:/home/linaro/OrangePiRK3399_kernel# file /tmp/image /tmp/image: data root@linaro-alip:/home/linaro/OrangePiRK3399_kernel# ./scripts/extract-ikconfig /tmp/image extract-ikconfig: Cannot find kernel config.
  14. I finally managed to install the OrangePi HDMI-IN image to the eMMC, but still have to figure out how to handle the camera. Anyway... While I'm working with the OrangePi Debian Stretch, is there anything I can grab that could help the Armbian build? I finally have the logs thanks to the UART, so that I should be able to setup setenv devnum 1 followed by run mmc_boot . This way, I could start Armbian from SDCard anytime. Unfortunately, I can't build a kernel on my Lubuntu laptop for the time being. I will try to setup an Armbian build environment on it.
  15. That's what I thought, thanks. This board is not for the faint of heart I believe...