Jump to content

constantius

Members
  • Posts

    221
  • Joined

  • Last visited

Posts posted by constantius

  1. thanks for all

    1. uboot upgraded

    2. Armbian 4.9 stops work

    3. Rest of images with newer kernel - if tou upgrade kernal - system stop working - you must disable kernel upgrade via armbian-config

    4. What a suprise - no audio..... hm

  2. On 5/2/2021 at 7:02 PM, TonyMac32 said:

    So far my Jetson Nano won't get to desktop using the images on the download site.  I have the original one, is this a device tree issue?

    Hello. I have the same problem... No one from armbian images works. Works image from that site .: https://forums.developer.nvidia.com/t/xubuntu-20-04-focal-fossa-l4t-r32-3-1-custom-image-for-the-jetson-nano/121768. And of course oryginal linux4tegra from Nvidia...But i would like switch to kernel 5.10 or 5.15, becuse snap does not work properly on 4.9... 

  3. hello. Thanks for reply. 

    Never mind the problem

    Starting kernel ...

    [   29.347708] EXT4-fs error (device mmcblk1p1): htree_dirblock_to_tree:1004: inode #35260: comm find: Directory block failed checksum
    [   29.379325] EXT4-fs (mmcblk1p1): Remounting filesystem read-only
    [   29.380061] EXT4-fs error (device mmcblk1p1): ext4_journal_check_start:83: Detected aborted journal
    [   30.096180] EXT4-fs error (device mmcblk1p1): htree_dirblock_to_tree:1004: inode #35318: comm find: Directory block failed checksum
    [   30.212107] EXT4-fs error (device mmcblk1p1): htree_dirblock_to_tree:1004: inode #35347: comm find: Directory block failed checksum
    [   30.352610] EXT4-fs error (device mmcblk1p1): htree_dirblock_to_tree:1004: inode #35301: comm find: Directory block failed checksum
     

    The board is probably mechanically damaged. Not even android and systems supplied by the manufacturer orangepi works. I have already filed a complaint with orangepi. That was strange behauvoir from the beggining...

    Thanks

     

  4. My picocom output

     

    "

    adek@PentiumG3440:~$ picocom -b 1500000 -r -l /dev/ttyUSB0
    picocom v3.1

    port is        : /dev/ttyUSB0
    flowcontrol    : none
    baudrate is    : 1500000
    parity is      : none
    databits are   : 8
    stopbits are   : 1
    escape is      : C-a
    local echo is  : no
    noinit is      : no
    noreset is     : yes
    hangup is      : no
    nolock is      : yes
    send_cmd is    : sz -vv
    receive_cmd is : rz -vv -E
    imap is        :
    omap is        :
    emap is        : crcrlf,delbs,
    logfile is     : none
    initstring     : none
    exit_after is  : not set
    exit is        : no

    Type [C-a] [C-h] to see available commands
    Terminal ready
    DDR Version 1.24 20191016
    In
    channel 0
    CS = 0
    MR0=0x18
    MR4=0x1
    MR5=0x1
    MR8=0x8
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    CS = 1
    MR0=0x18
    MR4=0x1
    MR5=0x1
    MR8=0x8
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    channel 1
    CS = 0
    MR0=0x18
    MR4=0x1
    MR5=0x1
    MR8=0x8
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    CS = 1
    MR0=0x18
    MR4=0x1
    MR5=0x1
    MR8=0x8
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    channel 0 training pass!
    channel 1 training pass!
    change freq to 416MHz 0,1
    Channel 0: LPDDR4,416MHz
    Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
    Channel 1: LPDDR4,416MHz
    Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
    256B stride
    channel 0
    CS = 0
    MR0=0x18
    MR4=0x1
    MR5=0x1
    MR8=0x8
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    CS = 1
    MR0=0x18
    MR4=0x1
    MR5=0x1
    MR8=0x8
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    channel 1
    CS = 0
    MR0=0x18
    MR4=0x1
    MR5=0x1
    MR8=0x8
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    CS = 1
    MR0=0x18
    MR4=0x1
    MR5=0x1
    MR8=0x8
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    channel 0 training pass!
    channel 1 training pass!
    channel 0, cs 0, advanced training done
    channel 0, cs 1, advanced training done
    channel 1, cs 0, advanced training done
    channel 1, cs 1, advanced training done
    channel 0, cs 1, dq 0 RISK!!! read vref 27% and 13% no find pass-eye
    channel 0, cs 1, dq 0 RISK!!! TdiVW_total violate spec
     channel 0, cs 1, dq 7 RISK!!! read vref 27% and 13% no find pass-eye
    channel 0, cs 1, dq 7 RISK!!! TdiVW_total violate spec
     change freq to 856MHz 1,0
    ch 0 ddrconfig = 0x101, ddrsize = 0x2020
    ch 1 ddrconfig = 0x101, ddrsize = 0x2020
    pmugrf_os_reg[2] = 0x3AA1FAA1, stride = 0xD
    ddr_set_rate to 328MHZ
    ddr_set_rate to 666MHZ
    ddr_set_rate to 928MHZ
    channel 0, cs 0, advanced training done
    channel 0, cs 1, advanced training done
    channel 1, cs 0, advanced training done
    channel 1, cs 1, advanced training done
    channel 0, cs 1, dq 0 RISK!!! read vref 27% and 13% no find pass-eye
    channel 0, cs 1, dq 0 RISK!!! TdiVW_total violate spec
     channel 0, cs 1, dq 7 RISK!!! read vref 27% and 13% no find pass-eye
    channel 0, cs 1, dq 7 RISK!!! TdiVW_total violate spec
     ddr_set_rate to 416MHZ, ctl_index 0
    ddr_set_rate to 856MHZ, ctl_index 1
    support 416 856 328 666 928 MHz, current 856MHz
    OUT
    Boot1: 2019-03-14, version: 1.19
    CPUId = 0x0
    ChipType = 0x10, 250
    mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
    mmc: ERROR: Card did not respond to voltage select!
    emmc reinit
    mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
    mmc: ERROR: Card did not respond to voltage select!
    emmc reinit
    mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
    mmc: ERROR: Card did not respond to voltage select!
    SdmmcInit=2 1
    mmc0:cmd5,20
    SdmmcInit=0 0
    BootCapSize=0
    UserCapSize=15193MB
    FwPartOffset=2000 , 0
    StorageInit ok = 54609
    SecureMode = 0
    SecureInit read PBA: 0x4
    SecureInit read PBA: 0x404
    SecureInit read PBA: 0x804
    SecureInit read PBA: 0xc04
    SecureInit read PBA: 0x1004
    SecureInit read PBA: 0x1404
    SecureInit read PBA: 0x1804
    SecureInit read PBA: 0x1c04
    SecureInit ret = 0, SecureMode = 0
    atags_set_bootdev: ret:(0)
    GPT 0x3380ec0 signature is wrong
    recovery gpt...
    GPT 0x3380ec0 signature is wrong
    recovery gpt fail!
    LoadTrust Addr:0x4000
    No find bl30.bin
    No find bl32.bin
    Load uboot, ReadLba = 2000
    hdr 0000000003380880 + 0x0:0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,

    Load OK, addr=0x200000, size=0xd3e04
    RunBL31 0x40000
    NOTICE:  BL31: v1.3(debug):42583b6
    NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
    NOTICE:  BL31: Rockchip release version: v1.1
    INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
    INFO:    Using opteed sec cpu_context!
    INFO:    boot cpu mask: 0
    INFO:    plat_rockchip_pmu_init(1190): pd status 3e
    INFO:    BL31: Initializing runtime services
    WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
    ERROR:   Error initializing runtime service opteed_fast
    INFO:    BL31: Preparing for EL3 exit to normal world
    INFO:    Entry point address = 0x200000
    INFO:    SPSR = 0x3c9


    U-Boot 2020.07-armbian (Sep 02 2020 - 10:03:21 +0200)

    Model: OrangePi 4 AI board
    DRAM:  3.9 GiB
    PMIC:  RK808
    MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
    Loading Environment from MMC... Card did not respond to voltage select!
    *** Warning - No block device, using default environment

    In:    serial
    Out:   serial
    Err:   serial
    Model: OrangePi 4 AI board
    Net:   eth0: ethernet@fe300000
    Hit any key to stop autoboot:  0
    =>  mmc list
    mmc@fe320000: 1
    sdhci@fe330000: 0
    => setenv devnum 0
    => run mmc_boot
    Card did not respond to voltage select!
    =>"

  5. On 2/29/2020 at 3:48 PM, martinayotte said:

    You need a USB-TTL Serial dongle plugged on the 3 pins Debug header of the OPi4 board. On your computer where you attached the dongle, you run terminal software such as "picocom" with baudrate set at 1500000 baud.

    You will then see the log when powering the board. If this Android U-Boot allows to stop booting using <spacebar> pressed several times during early boot and comes to a command prompt, you can then do "mmc list" to see the list of bootable devices, you can then select the SDCard device by doing "setenv devnum N", where N is the device number for SD, followed by "run mmc_boot". If this Android U-Boot doesn't support those commands, then you have to either try the TP50265 test point method shorted to GND before applying power to the board, or to find/try another SD image provided by Xunlong that allows to boot from it over eMMC, and then, from a "root" user shell, erase the eMMC by doing "dd if=/dev/zero of=/dev/mmcblk2 bs=1024 count=1024", that will destroy/erase Android U-Boot sectors definitively, so that any future boot attempts will be done exclusively from SDCard ...

     good evening - I did what you recommnad - I have Orange Pi4 without EMMC.  Output from putty MMC@fe320000 :1 and sdhci@fe330000: 0  DDR version 1.24 20191016.  Device is tried boot from emmc but there is no emmc. SDHCI error card did not respond to voltage select.  I have changed setnev devnum 0 - device not boot at all. What is wrong?

  6. I have a question. Because there is a big mess in the naming of the first Orangepi series. I have a board with orangepi mini 2 image working. Archived Armbian 5.05 kernel 3.4.119. Orangepi pi 2 images do not launch. In appearance and specifications, the Orangepi PC 2 and mini 2 are almost identical. https://linux-sunxi.org/Xunlong_Orange_Pi_Mini_2. However, the specification for the mini 2 exists, although the manufacturer himself does not provide it on its main website. Could you add an introduction to the orange pi mini 2 board, with the old 3.4 kernel, so that you can build a system? Or maybe someone has some archival image to share?

  7. Hello

    I think there is strange behawior in N2 board.

    http://ix.io/2xET
    In default cpu frequency script settings.: setenv max_freq_a73 "1800" htop and xfce4-cpu-monitor show 1900MHZ for A73

    When i changed it to setenv max_freq_a73 "1908" there is 1800MHZ in htop and xfce-cpu-monitor.

     

    I have also N2+ board and there is everything ok

  8. The N2 plus set to 2.4GHZ + 2.0GHZ works like a storm on the manufacturer's ubuntu firmware. I did not even try Armbian because there was no image that would support such frequencies. But it would be nice to support N2 +. I ordered fan. It works when you rich 65 degrees C

  9. Hi

    The problem with NXP I.Mx 8M cpu is lack of XORG 3D GPU support. Driver does not work.

    only 2D driver works.

    You can run XFCE and MATE destop without play video. ( video very often hangs system ) .

    Wayland 3D driver works with weston pulpit. But weston is on early stage of build.

    In fact, there is no multitasking. Works similar to AndroidTV or something like that.

  10. Hi

    Embest provides support for maaxboard. 

    You can downlaod image from their dropbox public site

    https://www.dropbox.com/sh/ft2o8olt88vm9mi/AACM2vz0SfZWuK4urXh2CpSla/02Linux/02LinuxShipmentImage?dl=0&subfolder_nav_tracking=1

    Weston wayland with 3d gpu driver and Xorg only 2D support ( MATE XFCE4 ).  

    I think the worse problem is lack of 3D driver to Xorg for NXP i.MX 8M Vivante GPU. 

    Best regards

  11. I would like to inform.

    There is debian 10 Weston 5.0 image avalaible to download on embest dropbox public site. Xorg can be installed and Xwayland but 3d driver is disabled. Wayland works with Weston and gdm3 display manager. If you prefer Xorg you can install xfce4 or mate desktop and lightdm display.

    If lightdm does not work properly please run startx service from terminal.  Best regards

  12. Hi

    I see that you have added Orange pi 4 SBC. 

    You can also add this device as suitable for testing .: https://pl.gearbest.com/tv-box/pp_728990.html 

    https://www.cnx-software.com/2017/08/18/videostrong-vs-rd-rk3399-development-board-review-part-1-unboxing-kit-assembly-sdk-and-documentation/

     https://pl.aliexpress.com/item/32875114274.html

    I have successfuly flashed on eMMC this SBC img from orange pi RK3399 first realese.

    Linux orangepi 4.4.174-rk3399 #31 SMP Sun Feb 10 00:37:23 CET 2019 aarch64 aarch64 aarch64 GNU/Linux

    Works perfactly ( as suitable for testing ) as on the Orange PI RK3399.

    I think Orange pi RK3399 may be is produced by Mecool.... Mecool has production line ( ODM OEM and as Mecool ) xuloung not. 

  13. thanks

     

    I gave it only for information. Embest company has announced that they will do a Debian port. I built the minimal-core yocto image myself. It lasts on a dual-core cpu haswell. Building an image from Gui is necessary to compile 2000 packages in yocto. I just gave the embest that there is something like armbian. They didn't know that such a thing existed. That's all. I didn't mean to do something for them for free. They should apply themselves if they want to. Support is expensive, i know.

  14. Hello. Information to Igor. I sent information about armbian to Embest (maaxboard manufacturer).
    They told me it was very interesting. I don't know if they will apply, it may be so. I have sent similar information to iWave (india) and Phytec (germany) which has also released sbc on NXP. SBC producers based on NXP cpu are based only on Yocto. And this is not easy and time consuming. I just inform you that if someone came to know where it came from. I did not suggest but you could do them for a fee, not free.

  15. Is there anyone from the armbian team interested in making img (I'd prefer ubuntu 18.04) to the maaxboard.
    I have such a board and I can borrow it for the time of testing the system. If so, please provide an address.

    Maaxboard 2GB RAM boot from sd-card, NXP i.MX 8M - Cortex-A53 Quad-Core  1.300MHZ ( it can run 1.5Ghz) 

    I have added solid fan.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines