Search the Community

Showing results for tags 'legacy'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 14 results

  1. EDIT: Just realized I posted this in the bug tracker forum. My apologies! See:
  2. Hello, I try to run this image: Armbian_20.02.0-rc0_Bananapir2_buster_legacy_4.19.97_minimal.img on Sinovoip Banana PI R2 (from SD card) and on 1-st boot i'm stuck: Tx DQM dly bit4 = 0x0 DRAMC_DQODLY1=79A98889h DRAMC_DQODLY2=8988B99Ah DRAMC_DQODLY3=2203123h DRAMC_DQODLY4=31103014h Tx DQ dly bit4 = 0x0 Tx DQS dly = 0x8949 Tx DQS dly bit4 = 0x0 TX Byte0: DQ - 16, DQS - 17. win_sum= 32 TX Byte1: DQ - 21, DQS - 13. win_sum= 33 TX Byte2: DQ - 8, DQS - 22. win_sum= 29 TX Byte3: DQ - 8, DQS - 22. win_sum= 29 DRAMC calibration takes 651397386 CPU cycles [EMI] DRAMC calibration passed [MEM] complex R/W mem test pass 0:dram_rank_size:80000000 [Dram_Buffer] dram size:-2147483648 [Dram_Buffer] structure size: 1725560 [Dram_Buffer] MAX_TEE_DRAM_SIZE: 0 Boot from SD Card!! [PLFM] Init Boot Device: OK(0) [PART] blksz: 512B [PART] [0x0000000000000000-0x000000000003FFFF] "PRELOADER" (512 blocks) [PART] [0x0000000000000000-0x000000000003FFFF] " B[TOOL] <UART> listen ended, receive size:3! [TOOL] <UART> wait sync time 150ms->5ms [TOOL] <UART> receieved data: () Device APC domain init setup: bootloader load uboot ,the address of uboot is 81E00000 [PART]partition name UBOOT [PART]partition start block 0x200 [PART]partition size 0x80000 [PART]partition blks 0x400 [PART]partition flags 0x0 [PART]partition name 0x8 [bean] part->startblk(0x200) bdev->blksz(0x200) part->part_id(8) hdr(0xFFB50000) [BlkDev.c 101 ]partition block size 0x200 ,blks:0xECE000 [BlkDev.c 101 ]partition block erase size 0x200 [PART] load "UBOOT" from 0x0000000000050000 (dev) to 0x81E00000 (mem) [SUCCESS] [PART] load speed: 5978KB/s, 300000 bytes, 49ms [BT_SD_PG] device info 0x8590 0x8A00 0xCB01 0x102 0:dram_rank_size:80000000 [PLFM] md_type[0] = 255 [PLFM] md_type[1] = 255 [PLFM] boot reason: 0 [PLFM] boot mode: 0 [PLFM] META COM0: 0 [PLFM] <0xFFB7CC10>: 0x0 [PLFM] boot time: 1906ms [PLFM] DDR reserve mode: enable = 0, success = 0 [BLDR] jump to 0x81E00000 [BLDR] <0x81E00000>=0xEA0000B8 [BLDR] <0x81E00004>=0xE59FF014 [USBD] USB PRB0 LineState: 0 [USBD] USB cable/ No Cable inserted! [PLFM] Keep stay in USB Mode Platform initialization is ok wait for frequency meter finish, CLK26CALI = 0x81 mt_pll_post_init: mt_get_cpu_freq = 1040000Khz wait for frequency meter finish, CLK26CALI = 0x90 mt_pll_post_init: mt_get_bus_freq = 273000Khz wait for frequency meter finish, CLK26CALI = 0x81 mt_pll_post_init: mt_get_mem_freq = 133250Khz [PWRAP] pwrap_init_preloader [PWRAP] pwrap_init [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=0,rdata=2D52 [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=1,rdata=2D52 [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=2,rdata=2D52 [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=3,rdata=800 [PWRAP] _pwrap_init_sistrobe [Read Test] pass,index=4 rdata=5AA5 [PWRAP] _pwrap_init_sistrobe [Read Test] pass,index=5 rdata=5AA5 [PWRAP] _pwrap_init_sistrobe [Read Test] pass,index=6 rdata=5AA5 [PWRAP] _pwrap_init_sistrobe [Read Test] pass,index=7 rdata=5AA5 [PWRAP] _pwrap_init_sistrobe [Read Test] pass,index=8 rdata=5AA5 [PWRAP] _pwrap_init_sistrobe [Read Test] pass,index=9 rdata=5AA5 [PWRAP] _pwrap_init_sistrobe [Read Test] pass,index=10 rdata=5AA5 [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=11,rdata=1001 [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=12,rdata=B54B [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=13,rdata=B54B [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=14,rdata=B54B [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=15,rdata=B54B [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=16,rdata=B54B [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=17,rdata=B54B [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=18,rdata=B54B [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=19,rdata=2003 [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=20,rdata=6A97 [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=21,rdata=6A97 [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=22,rdata=6A97 [PWRAP] _pwrap_init_sistrobe [Read Test] fail,index=23,rdata=6A97 [PWRAP] _pwrap_init_reg_clock [PMIC_WRAP]wrap_init pass,the return value=0. [pmic6323_init] Preloader Start.................. [pmic6323_init] PMIC CHIP Code = 0x2023 INT_MISC_CON: 1 TOP_RST_MISC: 1 pl pmic powerkey Release [pmic6323_init] powerKey = 0 [pmic6323_init] is USB in = 0xB004 [pmic6323_init] Reg[0x11A]=0x1B pmic setup LED [pmic6323_init] Done................... mt7623 disable long press reset ->>>>> mt7623 disable long press reset <<<<<- mt7623 VPA supplied by 1.0V to MT7530 -> mt7623 VPA supplied by 1.0V to MT7530 <- mt7623 enables RG_VGP1_EN for LCM -> mt7623 enables RG_VGP1_EN for LCM <- MT7623 E2 setting => MT7623 E2 setting <= [PLFM] Init I2C: OK(0) [PLFM] Init PWRAP: OK(0) [PLFM] Init PMIC: OK(0) [PLFM] chip[CA00] [BLDR] [Support SD/eMMC] Build Time: 20170114-170026 ==== Dump RGU Reg ======== RGU MODE: 4D RGU LENGTH: FFE0 RGU STA: 0 RGU INTERVAL: FFF RGU SWSYSRST: 0 ==== Dump RGU Reg End ==== RGU: g_rgu_satus:0 mtk_wdt_mode_config mode value=10, tmp:22000010 PL P ON WDT does not trigger reboot RGU mtk_wdt_init:MTK_WDT_DEBUG_CTL(590200F3) kpd read addr: 0x0040: data:0x4001 Enter mtk_kpd_gpio_set! kpd debug column : 0, 0, 0, 0, 0, 0, 0, 0 kpd debug row : 0, 0, 0, 0, 0, 0, 0, 0 after set KP enable: KP_SEL = 0x0 ! MTK_PMIC_RST_KEY is used for this project! [RTC] get_frequency_meter: input=0x0, ouput=5 [RTC] get_frequency_meter: input=0x0, ouput=3967 [RTC] get_frequency_meter: input=0x0, ouput=5 [RTC] get_frequency_meter: input=0x0, ouput=0 [RTC] get_frequency_meter: input=0x0, ouput=0 [RTC] bbpu = 0xD, con = 0x426 [RTC] powerkey1 = 0xA357, powerkey2 = 0x67D2 Writeif_unlock [RTC] RTC_SPAR0=0x40 rtc_2sec_reboot_check cali=1792 rtc_2sec_stat_clear [RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800 [RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1 [RTC] bbpu = 0xD, con = 0x426, cali = 0x700 pl pmic powerkey Release [PLFM] Power key boot! [RTC] rtc_bbpu_power_on done [EMI] mcp_dram_num:0,discrete_dram_num:1,enable_combo_dis:0 [EMI] PCDDR3 [Check]mt_get_mdl_number 0x0 [EMI] eMMC/NAND ID = 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 [EMI] MDL number = 0 [EMI] emi_set eMMC/NAND ID = 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 [EMI][Vcore]0x21E=0x48,0x220=0x48 [EMI][Vmem]0x554=0x0 wait for frequency meter finish, CLK26CALI = 0x81 [EMI] PCDDR3 DRAM Clock = 1600012 KHz, MEMPLL MODE = 2 [EMI] PCDDR3 RXTDN Calibration: Start REXTDN SW calibration... drvp=0xB,drvn=0x9 [EMI] pinmux = 4 =============================================================================== dramc_write_leveling_swcal =============================================================================== delay byte0 byte1 byte2 byte3 ----------------------------- 0 0 0 0 1 1 0 0 0 1 2 0 0 1 1 3 0 0 1 1 4 0 1 1 1 5 0 1 1 1 6 0 1 1 1 7 0 1 1 1 8 0 1 1 1 9 1 1 1 1 10 1 1 1 1 11 1 1 1 1 12 1 1 1 1 13 1 1 1 1 14 1 1 1 1 15 1 1 1 1 pass bytecount = 4 byte_i status best delay 0 2 9 1 2 4 2 2 2 3 2 0 ======================================== [write leveling]DQS: 0x249, DQM: 0x249 [write leveling after remap]DQ byte0 reg: 0x200 val: 0x99994444 [write leveling after remap]DQ byte1 reg: 0x204 val: 0x44449999 [write leveling after remap]DQ byte2 reg: 0x208 val: 0x22220000 [write leveling after remap]DQ byte3 reg: 0x20C val: 0x2222 ============================================= X-axis: DQS Gating Window Delay (Fine Scale) Y-axis: DQS Gating Window Delay (Coarse Scale) ============================================= 0 8 16 24 32 40 48 56 64 72 80 88 96 104 112 120 -------------------------------------------------------------------------------- 0000:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0001:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0002:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0003:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0004:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0005:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0006:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0007:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0008:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0009:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000A:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000B:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000C:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000D:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000E:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000F:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0010:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0011:| 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 0012:| 0 0 0 1 1 1 1 1 1 1 1 1 1 1 0 0 0013:| 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0014:| 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0015:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0016:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0017:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0018:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0019:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 001A:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 001B:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 001C:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 001D:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 001E:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 001F:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Rank 0 coarse tune value selection : 18, 18 18 64 rank 0 coarse = 18 rank 0 fine = 64 00:| 0 0 0 0 0 0 0 0 1 1 1 0 opt_dle value:13 ================================================================== RX DQS perbit delay software calibration ================================================================== 1.0-31 bit dq delay value ================================================================== bit| 0 1 2 3 4 5 6 7 8 9 -------------------------------------- 0 | 0 0 0 0 0 0 0 0 0 0 10 | 0 0 0 0 0 0 0 0 0 0 20 | 0 0 0 0 0 0 0 0 0 0 30 | 0 0 -------------------------------------- ================================================================== 2.dqs window x=pass dqs delay value (min~max)center y=0-7bit DQ of every group input delay:DQS0 =50 DQS1 = 40 DQS2 =53 DQS3 = 44 ================================================================== bit DQS0 bit DQS1 bit DQS2 bit DQS3 0 (19~69)44 8 (5~58)31 16 (23~69)46 24 (15~58)36 1 (19~70)44 9 (7~60)33 17 (22~70)46 25 (15~60)37 2 (21~70)45 10 (9~62)35 18 (25~70)47 26 (17~63)40 3 (18~68)43 11 (11~61)36 19 (21~68)44 27 (17~63)40 4 (21~77)49 12 (17~62)39 20 (27~79)53 28 (21~68)44 5 (21~68)44 13 (15~61)38 21 (25~71)48 29 (18~61)39 6 (21~69)45 14 (13~60)36 22 (25~72)48 30 (16~62)39 7 (25~76)50 15 (16~64)40 23 (31~74)52 31 (18~64)41 ================================================================== 3.dq delay value last ================================================================== bit| 0 1 2 3 4 5 6 7 8 9 -------------------------------------- 0 | 6 6 5 7 1 6 5 0 9 7 10 | 5 4 1 2 4 0 7 7 6 9 20 | 0 5 5 1 8 7 4 4 0 5 30 | 5 3 ================================================================== *DQIDLY1 = 0x7050606 *DQIDLY2 = 0x50601 *DQIDLY3 = 0x4050709 *DQIDLY4 = 0x40201 *DQIDLY5 = 0x9060707 *DQIDLY6 = 0x1050500 *DQIDLY7 = 0x4040708 *DQIDLY8 = 0x3050500 *DRAMC_R0DELDLY = 0x2C352832 [MEM]CONA:F3A2,conf1:F07486A3 DM4BitMux = 1 DQSO 0 in TX per-bit = 2 <= DQSO 0 in WL = 9 DQSO 1 in TX per-bit = 0 <= DQSO 1 in WL = 4 [Warning] DQSO 2 in TX per-bit = 9 > DQSO 2 in WL = 2 [Warning] DQSO 3 in TX per-bit = 8 > DQSO 3 in WL = 0 Tx DQM dly = 0x1189 Tx DQM dly bit4 = 0x0 DRAMC_DQODLY1=79A98989h DRAMC_DQODLY2=8988B99Bh DRAMC_DQODLY3=2103123h DRAMC_DQODLY4=31103014h Tx DQ dly bit4 = 0x0 Tx DQS dly = 0x8949 Tx DQS dly bit4 = 0x0 TX Byte0: DQ - 16, DQS - 17. win_sum= 32 TX Byte1: DQ - 21, DQS - 13. win_sum= 33 TX Byte2: DQ - 8, DQS - 22. win_sum= 29 TX Byte3: DQ - 8, DQS - 22. win_sum= 29 DRAMC calibration takes 651397844 CPU cycles [EMI] DRAMC calibration passed [MEM] complex R/W mem test pass 0:dram_rank_size:80000000 [Dram_Buffer] dram size:-2147483648 [Dram_Buffer] structure size: 1725560 [Dram_Buffer] MAX_TEE_DRAM_SIZE: 0 Boot from SD Card!! [PLFM] Init Boot Device: OK(0) [PART] blksz: 512B [PART] [0x0000000000000000-0x000000000003FFFF] "PRELOADER" (512 blocks) [PART] [0x0000000000000000-0x000000000003FFFF] "MBR" (512 blocks) [PART] [0x0000000000040000-0x00000000000BFFFF] "UBOOT" (1024 blocks) [PART] [0x00000000000C0000-0x00000000000FFFFF] "CONFIG" (512 blocks) [PART] [0x0000000000100000-0x000000000013FFFF] "FACTORY" (512 blocks) [PART] [0x0000000000140000-0x000000000213FFFF] "BOOTIMG" (65536 blocks) [PART] [0x0000000002140000-0x000000000413FFFF] "RECOVERY" (65536 blocks) [PART] [0x0000000004140000-0x000000004413FFFF] "ROOTFS" (2097152 blocks) [PART] [0x0000000044140000-0x000001FFC413FFFF] "USER" (-4194304 blocks) [platform_vusb_on] PASS [TOOL] PMIC not dectect usb cable! [TOOL] <UART> listen ended, receive size:0! [TOOL] <UART> wait sync time 150ms->5ms [TOOL] <UART> receieved data: () Device APC domain init setup: bootloader load uboot ,the address of uboot is 81E00000 [PART]partition name UBOOT [PART]partition start block 0x200 [PART]partition size 0x80000 [PART]partition blks 0x400 [PART]partition flags 0x0 [PART]partition name 0x8 [bean] part->startblk(0x200) bdev->blksz(0x200) part->part_id(8) hdr(0xFFB50000) [BlkDev.c 101 ]partition block size 0x200 ,blks:0xECE000 [BlkDev.c 101 ]partition block erase size 0x200 [PART] load "UBOOT" from 0x0000000000050000 (dev) to 0x81E00000 (mem) [SUCCESS] [PART] load speed: 5978KB/s, 300000 bytes, 49ms [BT_SD_PG] device info 0x8590 0x8A00 0xCB01 0x102 0:dram_rank_size:80000000 [PLFM] md_type[0] = 255 [PLFM] md_type[1] = 255 [PLFM] boot reason: 0 [PLFM] boot mode: 0 [PLFM] META COM0: 0 [PLFM] <0xFFB7CC10>: 0x0 [PLFM] boot time: 1901ms [PLFM] DDR reserve mode: enable = 0, success = 0 [BLDR] jump to 0x81E00000 [BLDR] <0x81E00000>=0xEA0000B8 [BLDR] <0x81E00004>=0xE59FF014
  3. Here's what I get when trying to boot (data is from my serial adapter): I2C_WriteByte nack returned I2C Device Address Write Abitration Error I2C_WriteByte nack returned I2C Device Address Write Abitration Error I2C_WriteByte nack returned I2C Device Address Write Abitration Error I2C_WriteByte nack returned I2C Device Address Write Abitration Error Wakeup Sub CPU 1234567 CPU Wakeup done! WFI is expected. CPU0 is Master! U-Boot 2016.01-armbian (Sep 02 2019 - 08:57:37 +0200) DRAM: 1 GiB MMC: NEXELL DWMMC: 0, NEXELL DWMMC: 1 loaded from SD, getting env from MMC 1 *** Warning - bad CRC, using default environment MIPI: display.0 HDMI: display.0, preset 0 (1280 * 720) HDMI: phy ready... LCD: [HDMI] dp.0.1 1220x680 16bpp FB:0x46000000 In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ** File not found /boot.scr ** ## Executing script at 40000000 Wrong image format for "source" command 1277 bytes read in 31 ms (40 KiB/s) ## Executing script at 40000000 Wrong image format for "source" command Card did not respond to voltage select! ** Bad device mmc 0 ** ## Executing script at 40000000 Wrong image format for "source" command ** Bad device mmc 0 ** ## Executing script at 40000000 Wrong image format for "source" command nanoPi# Here's what gpg and sha256sum output: % gpg --verify Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img.asc gpg: assuming signed data in 'Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img' gpg: Signature made Mon Jan 20 00:04:11 2020 EST gpg: using RSA key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 gpg: Good signature from "Igor Pecovnik <igor@armbian.com>" [unknown] gpg: aka "Igor Pecovnik (Ljubljana, Slovenia) <igor.pecovnik@gmail.com>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: DF00 FAF1 C577 104B 50BF 1D00 93D6 889F 9F0E 78D5 % sha256sum -c Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img.sha Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img: OK Output of mount: # mount --ro Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img /mnt/usb mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. dmesg doesn't mention anything about the mounting problems. Gdisk outputs: # gdisk -l Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img GPT fdisk (gdisk) version 1.0.1 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *************************************************************** Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Disk Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img: 2957312 sectors, 1.4 GiB Logical sector size: 512 bytes Disk identifier (GUID): 9FF78C6C-5C9B-4B4D-A4F3-B0B52827C119 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 2957278 Partitions will be aligned on 2048-sector boundaries Total free space is 8158 sectors (4.0 MiB) Number Start (sector) End (sector) Size Code Name 1 8192 2957311 1.4 GiB 8300 Linux filesystem The board I'm using is the Nano PI Fire3 LTS. It has worked before, although with a different Micro SD card. I accidentally erased it's SD card and I'm trying to reinstall. My current Micro SD card is a SanDisk Ultra 32GB rated USH-I, (10), U with a 1 inside, and A1. I used dd if=IMG of=DEV BS=8192 status=progress to place the image onto the Micro SD card. I also tried with my original SP Micro SD card without success. If you need anything else, just yell. Thanks!
  4. Is anyone still working with cubietruck? I installed the latest mainline image over Christmas expecting it to have the cedrus driver but apparently it does not. I thought that everything except HDMI audio should be working in mainline now. So I installed the latest legacy image. It plays videos well but bluetooth doesnt work. I switched it on in armbian-config and 'rfkill list' shows it as not disabled but the bluetooth manager shows no adapter and search is grayed out. This is a regression as it used to work to some extent. Also, very importantly for me, neither image switch over to battery power when the AC goes out. This also used to work on legacy, unless it was cubian that worked and armbian never did, I should keep notes...
  5. Hello, I've just found a topic about removing Allwinner legacy. I work with Orange Pi PC Plus board, H3 CPU. Do I understand correctly that the option to build system based on old v.3.4 kernel will be removed? Once I experienced a problem with system shutdown using newer kernel - got System halted message. This is why I decided to continue with legacy kernel. Please advise.
  6. Hi, I always been an retrorangepi user for my Opi1. but the lastest retrorangepi is stuck at 4.1 (I try the 4.2 slim but it's too slim) and the 4.3 beta also if its named as full, lacks of kodi and many emulators. so, my thought is. What if I build my personal emulationstation + lastest kodi on top of lastest armbian? Can I install armbian and then emustation and kodi? Do I have to install all emulator one by one? or I could use retroarch? Can I setup armbian to boot emustation? I think could be a good thing also for study
  7. The newest revision does not boot from current SD images. I'm working to debug why. If anyone else has a board and can test it out, let me know. The eMMC will boot, no problem, so it's just the SD itself. Model: Pine64 Rock64 DRAM: 1022 MiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b50303930343200000000051f1a serial=f55c6806c317581 Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 9 switch to partitions #0, OK mmc1 is current device ** No partition table - mmc 1 ** starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: Core Release: 3.10a USB3: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found scanning bus 3 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT Ideally getting old an new to boot would be ideal, @Igor this might mean a fragmentation for this board though, like having a V2 and older and a V3 and newer build if we can't make them all play nice with one bootloader.
  8. Hi, my rock64 (rev2) with the latest build of Armbian randomly looses its network connection. I couldn't use the armbianmonitor -u as it had no network connection, but when i use ifconfig, I can see it's still got it's settings and is the NIC lights are on. ifconfig showed 6 TX errors. My NIC is set to DHCP with static reserved IP address to an ASUS router. I leave it on 24/7 and check it once a while as it pretty much is used as a NAS with a single USB 3 drive. This morning I connected up via HDMI and a USB keyboard and logged in successfully. I don't have much Linux experience so wasn't sure how to capture the logs to SD card so i could copy them up here later. The NIC dropouts occur about once a week at random days and times. I have tried use ifup and ifdown to try and re-enable the NIC, but when I did this I got a stack dump and I couldn't enter any further commands into Ubuntu. Next time the NIC fails, what command(s) should I use? I've had this issue before on the later ayufun arm64 ubuntu builds too. I see the kernel has been updated to v5 over at ayufun's github, maybe there are some code changes that might help. I did read that dropping the MTU down from 1500 to 1492 might help, but don't really want to make random changes. Any suggestions much appreciated.
  9. Hello, I recently installed Armbian 5.85 legacy on my new Orange Pi Lite in order to try out my new Orange Pi camera, but it's not being recognized at all, even after following the instructions in this topic: I already tried doing the following (as root) unsuccessfully (no errors returned, but still can't detect camera): sunxi-pio -m "PG11<1><0><1><1>" #DOVDD sunxi-pio -m "PE15<1><0><1><0>" #Power_Down sunxi-pio -m "PE14<1><0><1><1>" #reset modprobe gc2035 modprobe vfe_v4l2 Here's the output of lsusb: Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Unfortunately, Armbian 5.20 is no longer available, so I can't try that unless I can compile it from source.
  10. Hello everyone :-). I would like help, I checked on the Web and I found using the forum a script (that I modified) to trigger using DTS LEDs. I adapted the script found here at the end of the page: Topic 112-dtb-howto-add-leds I think that for the section "disk-activity" and "netdev" it misses options but I'm not a developer just a scheming. Can you please explain to me how to add options to the mentioned trigger? I searched a lot of time but did not find any information. Here is my script, everything works fine (compiled with armbian-add-overlay), but "disk-activity" and "netdev" do not work. I tested the write / read trigger on disk but did not work either. Can you explain to me how to add the (device) options for disk-activity (with usb-nand-sata on / dev / sda) and netdev (for eth0)? thank you for the one who can help me to understand or to work this script. My card is OrangePi PC2 H5 1GB Sorry for bad english, my mother language is french. (this message is translatted in english from french) here is my script: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h5"; fragment@0 { target = <&pio>; __overlay__ { gpio_pin: gpio_pin { pins = "PA19","PA7","PA8","PA9","PA10","PD11","PA6","PA1","PA0","PA3"; function = "gpio_out"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { gpiopull: gpiopull { compatible = "gpio-leds"; pinctrl-names = "default"; pinctrl-0 = <&gpio_pin>; status = "okay"; gpio_out_19 { label = "P19:orange:wifiRx"; gpios = <&pio 0 19 0>; linux,default-trigger = "phy0rx"; }; gpio_out_7 { label = "P7:red:wifiTX"; gpios = <&pio 0 7 0>; default-state = "om"; linux,default-trigger = "phy0tx"; }; gpio_out_8 { label = "P8:orange:wifiConnect"; gpios = <&pio 0 8 0>; linux,default-trigger = "phy0assoc"; }; gpio_out_9 { label = "P9:green:wifiDetectUSB"; gpios = <&pio 0 9 0>; linux,default-trigger = "phy0radio"; }; gpio_out_10 { label = "P10:blue:cpuOnline"; gpios = <&pio 0 10 0>; linux,default-trigger = "cpu"; }; gpio_out_11 { label = "P11:white:Act"; gpios = <&pio 3 11 0>; linux,default-trigger = "activity"; }; gpio_out_0 { label = "P0:mmc0"; gpios = <&pio 0 0 0>; linux,default-trigger = "mmc0"; }; gpio_out_1 { label = "P1:disk-activity"; gpios = <&pio 0 1 0>; linux,default-trigger = "disk-activity"; }; gpio_out_3 { label = "P3:etherLink1gbps"; gpios = <&pio 0 3 0>; linux,default-trigger = "0.2:01:1Gbps"; }; gpio_out_6 { label = "P6:cpuled"; gpios = <&pio 0 6 0>; linux,default-trigger = "netdev"; }; }; }; }; }; addDTBTest2.dts
  11. Tag Heuer Watches - Elegant Performers - Tag Watches Small Gravel! Try to avoid buy mens watch, you will discover it in that respect there. Appreciate the natural color from this powder. The notable features in the timepieces with this particular brand are outstanding. read more swiss watch: đồng hồ thụy sỹ cao cấp One brand most jewelers in NYC showcase is Rr. They have classic designs both for males and females. You can wear them anything at all and you will always look great. Adding to that, they are sturdy especially when looked after normally. Before you decide to look into Omega watches and choose the one which you prefer best, here's the concerning the popular brand. At around 3 USD, you get an antique variety with regard to worn being a pendant on neck or could be used as a pocket sit down and watch. This Antique Owl Pattern Brass Quartz Pocket Watch With Chain Belt is encased in metal with exquisite engraving. Its diameter become 18 mm. The first thing we should look into is a lot of purchasing price in clothing is the label. For example the shirt actually costs $1.50 in China to make and a decent company might sell it for $20 off the rack. However, since found on the Gucci, Armani or Express label it always be sold to additional $100 or other. Though the swiss watch making industry has still the supremacy, the labor cost has forced several in the Western industries to China where labor is low quality. China, using their diligence, attended at par with such guest industries in matters of manufacturing watches which less expensive but reliable and in excess of artistic see. People have a desire to change to new style and designer. Watches made in China create the most appropriate environment getting cost hospitable. Online availability of China watches has taken the World market by storm. To possess a tremendous the most established watch company of China is online various 5000 designs of watches. read more: đồng hồ versace The Book of Revelation describes a physical dong ho leluxe structure of enormous proportions arriving to supply the end of age. This structure is said for you to become 1500 miles high, 1500 miles wide and 1500 miles robust. That works out to 3.375 Billion cubic mile after mile. A third of a Trillion cubic miles with outside walls measuring 216 feet strong. That ought to handle most incoming meteorites with minimal deteriorate. The biggest expense of leluxe backpacks are packaging and marketing. Real product is a fraction for the container the liquids are packaged for. Luxury cosmetic packaging creates value its keep is not really one. The Men's Luno watch was clearly influenced by its predecessor, the Museum Watch. Are cheaper . the same black dial, the gold marker at the twelve o'clock hour, combined with the sapphire crystal watch cover. The two most obvious discrepancies within close cousins are the bracelet along with the hour gloves. The Luno's bracelet is stainless steel, which provides a slightly sportier version that can be worn practical or at play. The Luno features gold-plated watch hands and also gold-plated bezel. Neither watch should be worn in the water, however, though they're they are water resistant up to 99 tootsies. When you create an online site or web page, avoid anything that wastes the reader's time or causes confusion. Too many fancy features slow across the loading speed up. If you want targeted traffic to read your content, make certain it is easy to read. Your structure and design must be straightforward and organized. When you are building a website site, you need to consider what is best for that readers they're more going to stay for the website longer. Involved with powered the 3 cylinder gas powerplant. There are even some stylists that do custom fittings for full lace hair pieces. The texture of the Guerlain Terracotta Mineral Flawless Bronzing Powder is absolutely fabulous. read more: https://leluxe.vn #leluxe #donghothuysy #donghoversace #donghohermes #donghosalvatoreferragam
  12. Hello, I've been using an OrangePi PC with legacy distribution for a long time as a mini-server, it worked Ok except for some seemingly random freeze. I'm using it with an unsupported monitor size (1600x1200), so I had a modded version, and I never updated the system files to avoid having to recompile. I'd like to update Armbian to the mainline kernel version, but I want to keep all my settings/additions/installed programs, so I'd prefer to NOT do a complete re-install. Is there a way to do an upgrade without losing everything?? If not, how can I keep track of all the modifications currently installed so I can re-install them? TIA
  13. I have a Renegade ROC-3328-CC board, and trying to get the touch to work on the touchscreen (Typical resistive Touch screen 3.5" HDMI HAT type screen). I'm using the Armbian_5.75_Renegade_Ubuntu_bionic_default_4.4.174_desktop.img, and everything is working except the touch on the screen. Does anyone have success with this combination? By reading through topics on the forum, it seems to me that I need to be on the mainline kernel (since it has fbtft and ads7846 drivers), but I'm not finding any packaged images using mainline that will support his board. Anyone have a mainline Image for the Renegade? I tried the Tinker images which are on Rockchip 3328, but they completely fail to boot. Only next step I'm seeing is to build a custom kernel, or try to backport the fbtft + ads7846.
  14. Hi. I want to run the desktop at a 800x600 resolution, to get better FPS at full screen gaming (HDMI screen). I fiddled with OpenGL, and it looks like I got a lot better FPS by just using glshim. Is there a known approach to getting 800x600 resolution? h3disp does not show 800x600 as an option. This is the Armbian Ubuntu Xenial image. Regards, Morten