Gabor Csuri

Members
  • Content Count

    5
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Posts posted by Gabor Csuri


  1. On 11/3/2018 at 10:57 AM, jock said:

    Try to run fdisk /dev/mmcblk0 and then issue the command p to take a look to the real partitions on the device

    Hi jock,

     

    thank you for your answer! I realized that partitions defined in the factory dtb. I'm using the mainline dtb so I had to define with the blkdevparts. Now I can access factory partitions with mainline kernel...

     

    best regards, Gabor


  2. Hi, 

     

     ok, I had to half the frequency in the device-tree. mmcblk1 mmcblkboot0, mmcblkboot1, mmcblkgp0 and mmcblkrpmb have appeared.

    How can I access the system,logo,env ...etc partitions ?

    In earlier kernel logs (4.12) I found:

    [    3.369031] mmcblk0: emmc:0001 AWPD3R 14.6 GiB 
    [    3.377416] mmcblk0boot0: emmc:0001 AWPD3R partition 1 4.00 MiB
    [    3.383431] mmcblk0boot1: emmc:0001 AWPD3R partition 2 4.00 MiB
    [    3.385447] mmcblk0rpmb: emmc:0001 AWPD3R partition 3 4.00 MiB
    [    3.392229] Enter aml_emmc_partition_ops
    [    3.395735] [mmc_read_partition_tbl] mmc read partition OK!
    [    3.400990] add_emmc_partition
    [    3.404385] [mmcblk0p01]           bootloader  offset 0x000000000000, size 0x000000400000 
    [    3.412716] [mmcblk0p02]             reserved  offset 0x000002400000, size 0x000004000000 
    [    3.421077] [mmcblk0p03]                cache  offset 0x000006c00000, size 0x000020000000 
    [    3.429441] [mmcblk0p04]                  env  offset 0x000027400000, size 0x000000800000 
    [    3.437806] [mmcblk0p05]                 logo  offset 0x000028400000, size 0x000002000000 
    [    3.446176] [mmcblk0p06]             recovery  offset 0x00002ac00000, size 0x000002000000 
    [    3.454532] [mmcblk0p07]                  rsv  offset 0x00002d400000, size 0x000000800000 
    [    3.462900] [mmcblk0p08]                  tee  offset 0x00002e400000, size 0x000000800000 
    [    3.471284] [mmcblk0p09]                crypt  offset 0x00002f400000, size 0x000002000000 
    [    3.479641] [mmcblk0p10]                 misc  offset 0x000031c00000, size 0x000002000000 
    [    3.488001] [mmcblk0p11]            instaboot  offset 0x000034400000, size 0x000020000000 
    [    3.496370] [mmcblk0p12]                 boot  offset 0x000054c00000, size 0x000002000000 
    [    3.504732] [mmcblk0p13]               system  offset 0x000057400000, size 0x000040000000 
    [    3.513100] [mmcblk0p14]                 data  offset 0x000097c00000, size 0x00030c200000 
    [    3.521334] amlmmc_dtb_init: register dtb chardev
    [    3.526130] amlmmc_dtb_init: register dtb chardev OK
    [    3.531101] Exit aml_emmc_partition_ops OK.

    Is it removed from the latest kernels?

     

    best regards, Gabor

     


  3. Hi,

     

     I've just tried mainline kernel 4.19 with my two TV boxes and first impression is wow! it works!  It's faster than expected! Thanks!

    With Magicsee N5 I can't access the internal eMMC. I use factory bootloder, meson-gxl-s905x-p212 dtb, released 4.19 kernel.

    I got:

     

    root@lepotato:~# dmesg|grep mmc
    [    0.000000] Kernel command line: console=ttyAML0,115200 root=/dev/mmcblk0p2
    [    0.979648] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.2
    [    0.985812] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.1
    [    0.992676] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.1
    [    0.999184] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.2
    [    1.005962] meson-gx-mmc d0072000.mmc: Linked as a consumer to regulator.2
    [    1.012580] meson-gx-mmc d0072000.mmc: Linked as a consumer to regulator.1
    [    1.019383] meson-gx-mmc d0072000.mmc: Got CD GPIO
    [    1.050790] meson-gx-mmc d0074000.mmc: Linked as a consumer to regulator.4
    [    1.052173] meson-gx-mmc d0074000.mmc: Linked as a consumer to regulator.1
    [    1.058938] meson-gx-mmc d0074000.mmc: allocated mmc-pwrseq
    [    1.100626] mmc0: new high speed SDHC card at address 0001
    [    1.107836] mmcblk0: mmc0:0001 SD8GB 7.28 GiB 
    [    1.122762]  mmcblk0: p1 p2
    [    1.694717] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.2
    [    1.700530] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.1
    [    1.707411] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.1
    [    1.713888] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.2
    [    1.737590] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.2
    [    1.738912] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.1
    [    1.745766] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.1
    [    1.752240] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.2
    [    1.759846] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.2
    [    1.765629] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.1
    [    1.772497] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.1
    [    1.778990] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.2
    [    1.833559] EXT4-fs (mmcblk0p2): mounted filesystem with writeback data mode. Opts: (null)
    [    2.193186] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.2
    [    2.198747] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.1
    [    2.205782] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.1
    [    2.212138] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.2
    [    2.627095] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.2
    [    2.629932] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.1
    [    2.636841] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.1
    [    2.643348] meson-gx-mmc d0070000.mmc: Dropping the link to regulator.2
    [    4.942703] EXT4-fs (mmcblk0p2): re-mounted. Opts: commit=600,errors=remount-ro
    [    5.641638] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.2
    [    5.641745] meson-gx-mmc d0070000.mmc: Linked as a consumer to regulator.1
    [    5.641821] meson-gx-mmc d0070000.mmc: allocated mmc-pwrseq
    [    5.697460] mmc2: queuing unknown CIS tuple 0x01 (3 bytes)
    [    5.708349] mmc2: queuing unknown CIS tuple 0x1a (5 bytes)
    [    5.713097] mmc2: queuing unknown CIS tuple 0x1b (8 bytes)
    [    5.714044] mmc2: queuing unknown CIS tuple 0x14 (0 bytes)
    [    5.716514] mmc2: queuing unknown CIS tuple 0x80 (1 bytes)
    [    5.716561] mmc2: queuing unknown CIS tuple 0x81 (1 bytes)
    [    5.716607] mmc2: queuing unknown CIS tuple 0x82 (1 bytes)
    [    5.716638] mmc2: new high speed SDIO card at address 0001
    [  242.654386] Workqueue: events_freezable mmc_rescan
    [  242.654487]  mmc_wait_for_req_done+0x44/0x160
    [  242.654497]  mmc_wait_for_req+0x98/0xd4
    [  242.654505]  mmc_send_tuning+0x11c/0x1b8
    [  242.654521]  meson_mmc_execute_tuning+0x6c/0x20c
    [  242.654531]  mmc_execute_tuning+0x48/0xbc
    [  242.654543]  mmc_init_card+0x9f0/0x19c4
    [  242.654554]  mmc_attach_mmc+0xac/0x170
    [  242.654564]  mmc_rescan+0x394/0x3cc

    SDcard is recognized and works but internal one is didn't. How I can access the internal eMMC? Why I got mmc_rescan hints periodically ?

     

    My second box is Beelink MiniMX. GBit phy is initialized but there is no link ... - I use the standard meson-gxbb-p201.dtb. I need to change something in the device-tree?

     

    bets regards, Gabor