-
Notifications
You must be signed in to change notification settings - Fork 404
Open
Description
Hi, i added support for the Galaxy tab S3 tablet from the work of #458 . It's an msm8996 device and i modified the msm8996-samsung.dts
file to include my device:
//omitted sections
reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
lk_region: lk_region@0 {
compatible = "removed-dma-pool";
no-map;
reg = <0x0 0x84C00000 0x0 0x00400000>;
};
sec_debug_region: sec_debug_region@0 {
compatible = "removed-dma-pool";
no-map;
reg = <0x0 0x85000000 0x0 0x00800000>;
};
klog_region: klog_region@0 {
compatible = "removed-dma-pool";
no-map;
reg = <0x0 0x851FF000 0x0 0x00201000>;
};
modem_shared_mem: modem_shared_mem_region@0x93000000 {
compatible = "removed-dma-pool";
no-map;
reg = <0x0 0x93000000 0x0 0x6000000>;
};
};
};
&lk2nd {
gts3llte {
model = "Samsung Galaxy Tab S3 LTE";
compatible = "samsung,gts3llte";
lk2nd,match-bootloader = "T825*";
lk2nd,dtb-files = "msm8996-samsung-gts3llte";
panel {
compatible = "samsung,gts3llte-panel", "lk2nd,panel";
ss_dsi_panel_PBA_BOOTING_HD {
compatible = "samsung,ana38401-ams968hh01";
};
ss_dsi_panel_ANA38401_AMS968HH01_QXGA {
compatible = "samsung,ana38401-ams968hh01";
};
};
};
//other devices
the project compiles and produces lk2nd.img
which i'm able to flash correctly using heimdall. The device then boots lk2nd but fails to load the android boot.img a reflashed after installing lk2nd with:
fastboot flash boot lk2nd.img
fastboot flash lk2nd lk2nd.img
fastboot flash boot boot.img
this is the oem log from lk2nd:
[0] welcome to lk
[10] platform_init()
[10] target_init()
[10] RPM GLink Init
[10] Opening RPM Glink Port success
[10] Opening SSR Glink Port success
[20] Glink Connection between APPS and RPM established
[20] Glink Connection between APPS and RPM established
[40] MMC card: BJNB4R (1.0, 04 2004), manufacturer: 15, OEM: 100, capacity: 31268536320 bytes
[50] SDHC Running in HS400 mode
[160] Done initialization of the card
[160] lk2nd_init()
[160] Booted @ 0x80008000, r0=0x0, r1=0x0, r2=0x83200000
[170] MMU mapping mismatch @ 0x83200000: 0x83201c1e != 0x83200c1a
[170] Found valid DTB with 6696 bytes total
<nge androidboot.em.did=03ea976ee80a androidboot.em.model=SM-T825 androidboot.em.status=0x0 androidboot.warranty_bit=1 androidboot.im.param.offset=10354736>
[300] Detected device: Samsung Galaxy Tab S3 LTE (compatible: samsung,gts3llte)
[310] MDP continuous splash detected: pipe VIG_0, base: 0x9a401000, stride: 6144, src: 1024x1536 (0,0), img: 2048x1536, out: 1024x1536 (0,0), format: 0x224>
[330] MMU mapping mismatch @ 0x9a400000: 0x9a401c1e != 0x9a400c1a
[330] Display refresh: cmd mode: 1, auto refresh: 0 (sel: 0x21f20)
[350] fastboot_init()
[810] fastboot: processing commands
[9090] fastboot: oem log
The MMU mapping mismatch
is concerning, while the devices are pretty similar (galaxy s7 came out in 2016, this tablet in 2017) there might be differences in the reserved-memory section?
Metadata
Metadata
Assignees
Labels
No labels