piter75

  • Content Count

    287
  • Joined

  • Last visited

Reputation Activity

  1. Like
    piter75 got a reaction from NicoD in NanoPi M4 V2 - M4 Image not working   
    I rebased my branch onto latest master changes.
    Took me some time to make the sound working in kernel 5.4.
     
    Branch is now named nanopi-m4v2-bring-up and supports "legacy", "current" and "dev" targets.
    Did not test "legacy" much yet but "current" 5.4 works quite well.
    In dev wi-fi is broken, but anyway "current" is much more compelling as it is 5.4 vs. 5.4-rc1 in dev.
     
    Command line for "current":
    ./compile.sh BOARD=nanopim4v2 BRANCH=current RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no  
  2. Like
    piter75 got a reaction from Fred St-Pierre in ROC-RK3399-PC (Renegade Elite)   
    The kudos belong to Levin Du of T-Firefly team who did the heavy lifting.
    I merely paved the path with my u-boot PR and helped make the reboot work in mainline ATF for rk3399.
     
    Oh and BTW... this is the first rk3399 board in Armbian which boots with full and fresh OSS combo: mainline u-boot's TPL/SPL + mainline ATF.
  3. Like
    piter75 got a reaction from Fred St-Pierre in ROC-RK3399-PC (Renegade Elite)   
    What we have right now is, probably, exactly what you wanted to achieve:
    Option 2 for building Option 3 for packaging This boils down to having all bootloader components built from source code as opposed to having to load binary blob from vendor in the process.
     
    I am not an expert on ATF but I understand it as a firmware running in a secure zone of the processor with a set of interfaces (eg. PSCI for power control) that let it interact with the rest of the software.
    Not using ATF would mean that one had to code those interfaces themselves.
  4. Like
    piter75 got a reaction from gounthar in ROC-RK3399-PC (Renegade Elite)   
    The kudos belong to Levin Du of T-Firefly team who did the heavy lifting.
    I merely paved the path with my u-boot PR and helped make the reboot work in mainline ATF for rk3399.
     
    Oh and BTW... this is the first rk3399 board in Armbian which boots with full and fresh OSS combo: mainline u-boot's TPL/SPL + mainline ATF.
  5. Like
    piter75 got a reaction from aaditya in ROC-RK3399-PC (Renegade Elite)   
    The kudos belong to Levin Du of T-Firefly team who did the heavy lifting.
    I merely paved the path with my u-boot PR and helped make the reboot work in mainline ATF for rk3399.
     
    Oh and BTW... this is the first rk3399 board in Armbian which boots with full and fresh OSS combo: mainline u-boot's TPL/SPL + mainline ATF.
  6. Like
    piter75 got a reaction from Igor in ROC-RK3399-PC (Renegade Elite)   
    The kudos belong to Levin Du of T-Firefly team who did the heavy lifting.
    I merely paved the path with my u-boot PR and helped make the reboot work in mainline ATF for rk3399.
     
    Oh and BTW... this is the first rk3399 board in Armbian which boots with full and fresh OSS combo: mainline u-boot's TPL/SPL + mainline ATF.
  7. Like
    piter75 got a reaction from aaditya in Rock PI 4   
    IMHO It could never work with mainline kernel.
    At first it was named "RockPi-4B" in Armbian's custom device tree and then it was renamed to "Radxa ROCK Pi 4" following Rock Pi 4's device tree upstreaming somewhere around July.
     
    At this point you could:
    use "default" image which should work fine with "libmraa" make yourself and overlay with a model change to survive kernel updates try adjusting "libmraa" to make it work with mainline kernel (and upstreaming the change) - probably by the means of verifying that "compatible" contains "radxa,rockpi4" 3rd option would be best in the long run IMO.
  8. Like
    piter75 got a reaction from pask in NanoPi M4 V2 - M4 Image not working   
    There is one thing that comes to my mind... I have some features disabled in my config-minimal.conf.
    I have AUFS disabled for sure, which is irrelevant. Will let you know about the rest later.
     
    Dev kernel should have a sound card working by now 😉
  9. Like
    piter75 got a reaction from NicoD in NanoPi M4 V2 - M4 Image not working   
    Ok, the causes of the crashes could be different for us as I use it solely in the terminal
     
    Anyway, I did something which I cannot imagine could help but... it seems that it helped.
    I remember reading somewhere lately about instability of PX30 at 408MHz that was avoided by changing min frequency to 600MHz.
    Our images for RK3399 have default min of 600MHz so I did the opposite and changed the min to 408MHz.
     
    I will definitely observe it for a longer time but last 40-50 reboots were clean of errors while before it happened every 3-5 reboot.
  10. Like
    piter75 got a reaction from chwe in armbian can not boot in Rock Pi4 v1.4   
    I have been happily booting Rock Pi 4B v1.4 since August with both eMMC and SD.
    As others already pointed it would be good if you had some console logs.
     
    At this point I am running custom Armbian build based on latest u-boot and open source ATF but will burn SD with latest "official" image, check if it boots and will get back with the results.