Jump to content

Zaxter

Members
 View Profile  See their activity

  • Posts

    9

  • Joined

  • Last visited

 Content Type 

Posts posted by Zaxter

    Opening serial port causes kernal panic

    in Allwinner sunxi

    Posted

    I was able to solve the problem. It was related to UART settings in the Fex file.

    Somehow, I hadn't set the pull-up on UART6 & UART7. ->



    
[uart_para6]
    
uart_used = 1
    
uart_port = 6
    
uart_type = 2
    
uart_tx = port:PI12<3><default><default><default>
    
uart_rx = port:PI13<3><default><default><default>
    
#                          ^
    
#                          |
    
#                         Here


    It should've been ->



    
[uart_para6]
    
uart_used = 1
    
uart_port = 6
    
uart_type = 2
    
uart_tx = port:PI12<3><1><default><default>
    
uart_rx = port:PI13<3><1><default><default>


    I guess I will be moving to the mainline kernel in the future.

    0

    Opening serial port causes kernal panic

    in Allwinner sunxi

    Posted

    Thanks for pointing me in the right direction @zador.blood.stained.
    Here are the crash logs from serial console: 

    root@micro:~# cat /dev/ttyS2
<4>i2c-0, xfer timeout

[   63.123577] i2c-0, xfer timeout
<3>axp_mfd 0-0034: failed reading at 0x23

[   63.130520] axp_mfd 0-0034: failed reading at 0x23
<3>[cpu_freq] ERR:try to set voltage failed!

[   63.139404] [cpu_freq] ERR:try to set voltage failed!

    And here's the dmesg output for registered uarts:

    root@micro:~# dmesg | grep uart
[    0.996902] [uart]: used uart info.: 0xc9
[    1.001620] [uart]: serial probe 0 irq 33 mapbase 0x01c28000
[    1.027944] sunxi-uart.0: ttyS0 at MMIO 0x1c28000 (irq = 33) is a U6_16550A
[    1.889704] [uart]: serial probe 3 irq 36 mapbase 0x01c28c00
[    1.921599] sunxi-uart.3: ttyS1 at MMIO 0x1c28c00 (irq = 36) is a U6_16550A
[    1.933439] [uart]: serial probe 6 irq 51 mapbase 0x01c29800
[    1.965318] sunxi-uart.6: ttyS2 at MMIO 0x1c29800 (irq = 51) is a U6_16550A
[    1.977174] [uart]: serial probe 7 irq 52 mapbase 0x01c29c00
[    2.009053] sunxi-uart.7: ttyS3 at MMIO 0x1c29c00 (irq = 52) is a U6_16550A

    Have you seen something like this before?

    0

    Opening serial port causes kernal panic

    in Allwinner sunxi

    Posted

    Why do you think so? If I remember correctly uart_port = 6 should configure /dev/ttyS6, but you can check the source code if you want to confirm port numbering scheme

     

    I'm not sure why, but this is the behaviour I'm currently seeing.  :blink:

    It may have to do with the fact that I've set uart_used = 0 for all UARTs but 0,3,6 & 7. So, although I do get ttyS0 -> ttyS7, UARTs 0,3,6 & 7 are configured as ttyS0 to ttyS3 & I can't access >ttyS3.

    $ cat /dev/ttyS7
cat: /dev/ttyS7: Input/output error
    0

    Opening serial port causes kernal panic

    in Allwinner sunxi

    Posted

    I'm running Armbian_5.20_Micro_Debian_jessie_3.4.112 on an Olimex A20 micro board.

    I find that opening serial port device `/dev/ttyS2` causes the system to crash. The board heartbeat LED either stops or blinks rapidly. The board itself is not pingable.

    I can reproduce this issue with a simple from the shell using: 

    cat /dev/ttyS2

     or from c code using:

    fd = open("/dev/ttyS2", O_RDWR | O_NOCTTY | O_NDELAY);

    `/dev/ttyS2` is linked to UART6. In the fex file, I have configured it like so:

    [uart_para6]
uart_used = 1
uart_port = 6
uart_type = 2
uart_tx = port:PI12<3><default><default><default>
uart_rx = port:PI13<3><default><default><default>

    Note that the UART6 is on MUX3 as it should be according to sunxi's pio documentation for A20.

     

    Any ideas?

     

    0

    NAND Install fails on subsequent boots with 'Error: /proc must be mounted'

    in Allwinner sunxi

    Posted

    Thanks for your reply Igor.

     

    I just wanted to mention that I'm able to boot from NAND without any problems using your recent `Armbian_5.20_Micro_Debian_jessie_3.4.112.img` image on the same board. Everything including ethernet works perfectly fine even on subsequent attempts.

    This leads me to believe that my problem here (i.e. proc not being mounted on boot) is not related to the GMAC. 

    0

    NAND Install fails on subsequent boots with 'Error: /proc must be mounted'

    in Allwinner sunxi

    Posted

    Hi All,

     

    I'm using a rather old Armbian (wheezy) image on an Olimex Micro.

    I've installed a lot of apps on it, so I don't want to be moving to a newer image.

     

    I'm trying to copy my SD card image to NAND using the `nand-sata-install.sh` script that came with the image. 

     

    All goes well. The script partitions the NAND, reboots, installs all files and shuts down. 

    When I remove the SD card and power on, the board boots and everything is still alright. 

     

    Now, on subsequent poweroffs or reboots, the board does boot, but I doesn't connect to ethernet. 

    Boot logs from debug UART show that `proc` isn't mounted. 

    Error: /proc must be mounted

    What could be the reasons for this? 

     

    0

    /dev/nand missing

    in Allwinner sunxi

    Posted

    There's no /proc/nand either. :( 
     

    I have tried a lot of different images here and I have the same problem. I'll check to see if there's something wrong on the hardware side.

    Thank you again for your help @igor. 

    1

    /dev/nand missing

    in Allwinner sunxi

    Posted

    Thanks for your replies @wildcat and @igor.

     

    I think my fex config is alright. I use the same fex with another board and the nand device shows up straight away.

    I also don't get why Livesuite fails to write to the nand. 

     

    Quick question: 

    Would the nand device (i.e. /dev/nand) show up even if it was never partitioned / pre-written with an Android NAND image?

    1

    /dev/nand missing

    in Allwinner sunxi

    Posted · Edited by Zaxter
    added spoiler tags / please improve the output / use http://pastebin.com/ please

    Hi All, 
     
    I'm using Armbian_5.10_Micro_Debian_jessie_3.4.112 on a custom A20 board with NAND based off the Olimex A20 Micro.
    I don't see /dev/nand on it.
     
    $ zgrep NAND /proc/config.gz
CONFIG_SUNXI_NAND_PARTITION=y
CONFIG_SUNXI_NAND=y
# CONFIG_SUNXI_NAND_COMPAT_DEV is not set
# CONFIG_SUNXI_NAND_TEST is not set
    I even tried to Livesuite an Android NAND image, but it also failed. I'm pasting the logs below.
     
    What does it generally mean to have a missing /dev/nand?
     
    Thanks.
     

     
    $ sudo ./LiveSuit.sh
    Starting x86-64/LiveSuit.


    library file path: /home/asrolabe/Downloads/sunxi-livesuite/x86-64/plgvector.dll
    library file path: /home/asrolabe/Downloads/sunxi-livesuite/x86-64/LangPlg.dll
    LoadFile 24
    Open 274: Language file format is UTF-8
    library file path: /home/asrolabe/Downloads/sunxi-livesuite/x86-64/LiveProc.Plg
    library file path: /home/asrolabe/Downloads/sunxi-livesuite/x86-64/plgvector.dll
    library file path: /home/asrolabe/Downloads/sunxi-livesuite/x86-64/luaeFex.dll
    Register./luaBase.dll l_RegAllFun Sucess!
    Register./luaeFex.dll l_RegAllFun Sucess!
    Register./luadec.dll l_RegAllFun Sucess!
    IMAGEWTY
    ItemTableSize = 1048576
    Closing image now!


    Clos image OK!

    Register./luaBase.dll l_RegAllFun Sucess!
    Register./luaeFex.dll l_RegAllFun Sucess!
    Register./luadec.dll l_RegAllFun Sucess!
    IMAGEWTY
    ItemTableSize = 1048576
    Closing image now!

    Clos image OK!

    Register./luaBase.dll l_RegAllFun Sucess!
    Register./luaeFex.dll l_RegAllFun Sucess!
    Register./luadec.dll l_RegAllFun Sucess!
    IMAGEWTY
    ItemTableSize = 1048576
    Closing image now!

    Clos image OK!

    Dev Plugin The Device Path is: /dev/aw_efex0
    Register./luaBase.dll l_RegAllFun Sucess!
    Register./luaeFex.dll l_RegAllFun Sucess!
    Register./luadec.dll l_RegAllFun Sucess!
    IMAGEWTY
    ItemTableSize = 1048576
    Closing image now!

    Clos image OK!

    Register./luaBase.dll l_RegAllFun Sucess!
    Register./luaeFex.dll l_RegAllFun Sucess!
    Register./luadec.dll l_RegAllFun Sucess!
    IMAGEWTY
    ItemTableSize = 1048576
    Closing image now!

    Clos image OK!

    [Tl_Msg]Init : imgFilePath=/home/asrolabe/Documents/ACD/A20_android_422_TS_USB_UART_I2C_WIFI_LAN_HDMI_LCD_1024x600_release_3.img, imgLen=[0, 532252672], workMode=8

    IMAGEWTY
    ItemTableSize = 1048576
    ./buffer.cpp, pBuffer = 0x7f2f7020a9e4, nLen = 16380, crc32 = 4120441415[Tl_Msg]Down index[1] start

    [Tl_Msg]partName=bootloader, pktSubType=BOOTLOADER_FEX00, verifyFile=VBOOTLOADER_FEX0

    [Tl_Msg]partAddrHigInSec=0x0, partAddrLowInSec=0x8000, partSzHigInSec=0x0, partSzLowInSec=0x8000

    [Tl_Msg]isEncrypt=false, toVerify=true

    [Tl_Msg]Down index[1] end

    [Tl_Msg]Down index[2] start

    [Tl_Msg]partName=env, pktSubType=ENV_FEX000000000, verifyFile=VENV_FEX00000000

    [Tl_Msg]partAddrHigInSec=0x0, partAddrLowInSec=0x10000, partSzHigInSec=0x0, partSzLowInSec=0x8000

    [Tl_Msg]isEncrypt=false, toVerify=true

    [Tl_Msg]Down index[2] end

    [Tl_Msg]Down index[3] start

    [Tl_Msg]partName=boot, pktSubType=BOOT_FEX00000000, verifyFile=VBOOT_FEX0000000

    [Tl_Msg]partAddrHigInSec=0x0, partAddrLowInSec=0x18000, partSzHigInSec=0x0, partSzLowInSec=0x8000

    [Tl_Msg]isEncrypt=false, toVerify=true

    [Tl_Msg]Down index[3] end

    [Tl_Msg]Down index[4] start

    [Tl_Msg]partName=system, pktSubType=SYSTEM_FEX000000, verifyFile=VSYSTEM_FEX00000

    [Tl_Msg]partAddrHigInSec=0x0, partAddrLowInSec=0x20000, partSzHigInSec=0x0, partSzLowInSec=0x100000

    [Tl_Msg]isEncrypt=false, toVerify=true

    [Tl_Msg]Down index[4] end

    [Tl_Msg]Down index[5] start

    [Tl_Msg]partName=recovery, pktSubType=RECOVERY_FEX0000, verifyFile=VRECOVERY_FEX000

    [Tl_Msg]partAddrHigInSec=0x0, partAddrLowInSec=0x228000, partSzHigInSec=0x0, partSzLowInSec=0x10000

    [Tl_Msg]isEncrypt=false, toVerify=true

    [Tl_Msg]Down index[5] end

    [Tl_Msg]Down index[6] start

    [Tl_Msg]partName=UDISK, pktSubType=DISKFS_FEX000000, verifyFile=

    [Tl_Msg]partAddrHigInSec=0x0, partAddrLowInSec=0x3c0000, partSzHigInSec=0x0, partSzLowInSec=0x0

    [Tl_Msg]isEncrypt=false, toVerify=false

    [Tl_Msg]Down index[6] end

    [Tl_Msg]Down number is 6

    [Tl_Msg]sec[platform]

    [Tl_Msg]sec[card2_boot_para]

    0x7f2f7020a9e0, 541, 4, =40x7f2f7020a9e0, 540, 2, =2[Tl_Msg]sec[card_boot]

    [Tl_Msg]sec[target]

    [Tl_Msg]sec[dram_para]

    [Tl_Msg]sec[DllInfo]

    [Tl_Msg]sec[uart_para]

    [Tl_Msg][platform]

    [Tl_Msg]eraseflag = 0x0

    [Tl_Msg]

    [Tl_Msg][card2_boot_para]

    [Tl_Msg]sdc_clk = port:PC7<3><1>

    [Tl_Msg]card_line = 0x4

    [Tl_Msg]sdc_d0 = port:PC8<3><1>

    [Tl_Msg]card_ctrl = 0x2

    [Tl_Msg]sdc_cmd = port:PC6<3><1>

    [Tl_Msg]sdc_d2 = port:PC10<3><1>

    [Tl_Msg]sdc_d3 = port:PC11<3><1>

    [Tl_Msg]card_high_speed = 0x1

    [Tl_Msg]sdc_d1 = port:PC9<3><1>

    [Tl_Msg]

    [Tl_Msg][card_boot]

    [Tl_Msg]logical_start = 0xa000

    [Tl_Msg]

    [Tl_Msg][target]

    [Tl_Msg]storage_type = 0xffffffffffffffff

    [Tl_Msg]

    [Tl_Msg][dram_para]

    [Tl_Msg]dram_baseaddr = 0x40000000

    [Tl_Msg]dram_chip_density = 0x1000

    [Tl_Msg]dram_size = 0x400

    [Tl_Msg]dram_rank_num = 0x1

    [Tl_Msg]dram_io_width = 0x10

    [Tl_Msg]dram_tpr0 = 0x42d899b7

    [Tl_Msg]dram_cas = 0x9

    [Tl_Msg]dram_odt_en = 0x0

    [Tl_Msg]dram_tpr1 = 0xa090

    [Tl_Msg]dram_zq = 0x7f

    [Tl_Msg]dram_bus_width = 0x20

    [Tl_Msg]dram_tpr4 = 0x0

    [Tl_Msg]dram_emr3 = 0x0

    [Tl_Msg]dram_clk = 0x180

    [Tl_Msg]dram_emr2 = 0x10

    [Tl_Msg]dram_emr1 = 0x4

    [Tl_Msg]dram_tpr5 = 0x0

    [Tl_Msg]dram_tpr3 = 0x0

    [Tl_Msg]dram_type = 0x3

    [Tl_Msg]dram_tpr2 = 0x22a00

    [Tl_Msg]

    [Tl_Msg][DllInfo]

    [Tl_Msg]

    [Tl_Msg][uart_para]

    [Tl_Msg]uart_debug_rx = port:PB23<2><1><default><default>

    [Tl_Msg]uart_debug_port = 0x0

    [Tl_Msg]uart_debug_tx = port:PB22<2><1><default><default>

    [Tl_Msg]

    [Tl_Msg]Init end

    [Tl_Msg]fel in: dev[/dev/aw_efex0]

    [Tl_Msg]platform id checked OK

    [Tl_Msg]To down sys para

    [Tl_Msg]To down and Run fes1-1

    [Tl_Msg]To clear fes aide log

    [Tl_Msg]To down and Run fes1-2

    [Tl_Msg]To clear fes aide log

    [Tl_Msg]OK test fel Down and Up in len=8192

    [Tl_Msg]OK to test dram

    [Tl_Msg]Update dram size to 1024MBytes

    [Tl_Msg]nMsgRet=1

    [Tl_Msg]To down fes2_1

    [Tl_Msg]To down fes2_2

    [Tl_Msg]To clear fes aide log

    [Tl_Msg]not hasRetLog

    [Tl_Msg]Fel end

    Fel Thread Finished!
    Dev Plugout The Device Path is: /dev/aw_efex0
    Dev Plugout The Device Path is: /dev/aw_efex0
    Dev Plugout The Device Path is: /dev/aw_efex0

     

     

     

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept