FORUMS
Remove All Ads from XDA

[Guide] Mate 9 Flash and DDR Info

236 posts
Thanks Meter: 397
 
By mankindtw, Senior Member on 22nd April 2017, 08:05 AM
Post Reply Email Thread
  • Steps:
    A. Unlock bootloader and install TWRP 3.0.3-1.
    B. Run TWRP and connect usb cable.
    C. Download HWDev_2017042201.zip
    D. Run "hwdev.bat" and it will use keyword search kernel log for Flash and DDR info
The Following 4 Users Say Thank You to mankindtw For This Useful Post: [ View ] Gift mankindtw Ad-Free
 
 
22nd April 2017, 08:07 AM |#2  
OP Senior Member
Thanks Meter: 397
 
More
I got my mate 9 info
Flash: TOSHIBA THGBF7T0L8LBATAC
DDR: lpddr4
22nd April 2017, 01:10 PM |#3  
Member
Flag München
Thanks Meter: 20
 
More
What kind of DDR info do you expect from the kernel ?
The most obvious one:
Code:
HWMHA:/data/data # cat /proc/ddr_rod
lpddr3
HWMHA:/data/data # cat /proc/ddr_info
ddr_info:
0x401
And your method will report
Code:
ddr: current logic version is lpddr4 verison !!!
The lowlevel flash specs (SAMSUNG KLUCG4J1EB-B0B1):
Code:
HWMHA:/data/data # cat /sys/kernel/debug/ufs/dump_device_desc
Device Descriptor[Byte offset 0x0]: bLength = 0x40
Device Descriptor[Byte offset 0x1]: bDescriptorType = 0x0
Device Descriptor[Byte offset 0x2]: bDevice = 0x0
Device Descriptor[Byte offset 0x3]: bDeviceClass = 0x0
Device Descriptor[Byte offset 0x4]: bDeviceSubClass = 0x0
Device Descriptor[Byte offset 0x5]: bProtocol = 0x0
Device Descriptor[Byte offset 0x6]: bNumberLU = 0x4
Device Descriptor[Byte offset 0x7]: bNumberWLU = 0x4
Device Descriptor[Byte offset 0x8]: bBootEnable = 0x1
Device Descriptor[Byte offset 0x9]: bDescrAccessEn = 0x0
Device Descriptor[Byte offset 0xa]: bInitPowerMode = 0x1
Device Descriptor[Byte offset 0xb]: bHighPriorityLUN = 0x7f
Device Descriptor[Byte offset 0xc]: bSecureRemovalType = 0x0
Device Descriptor[Byte offset 0xd]: bSecurityLU = 0x1
Device Descriptor[Byte offset 0xe]: Reserved = 0x4
Device Descriptor[Byte offset 0xf]: bInitActiveICCLevel = 0x0
Device Descriptor[Byte offset 0x10]: wSpecVersion = 0x2
Device Descriptor[Byte offset 0x12]: wManufactureDate = 0x1610
Device Descriptor[Byte offset 0x14]: iManufactureName = 0x0
Device Descriptor[Byte offset 0x15]: iProductName = 0x1
Device Descriptor[Byte offset 0x16]: iSerialNumber = 0x2
Device Descriptor[Byte offset 0x17]: iOemID = 0x3
Device Descriptor[Byte offset 0x18]: wManufactureID = 0xce01
Device Descriptor[Byte offset 0x1a]: bUD0BaseOffset = 0x10
Device Descriptor[Byte offset 0x1b]: bUDConfigPLength = 0x10
Device Descriptor[Byte offset 0x1c]: bDeviceRTTCap = 0x2
Device Descriptor[Byte offset 0x1d]: wPeriodicRTCUpdate = 0x0
The Following 2 Users Say Thank You to user4774 For This Useful Post: [ View ] Gift user4774 Ad-Free
22nd April 2017, 01:24 PM |#4  
OP Senior Member
Thanks Meter: 397
 
More
Quote:
Originally Posted by user4774

What kind of DDR info do you expect from the kernel ?
The most obvious one:

Code:
HWMHA:/data/data # cat /proc/ddr_rod
lpddr3

No, it's incorrect.
Someone post source code, if it don't specify ddr type and it return default value "lpddr3".
DDR source code
The Following User Says Thank You to mankindtw For This Useful Post: [ View ] Gift mankindtw Ad-Free
22nd April 2017, 01:41 PM |#5  
Member
Flag München
Thanks Meter: 20
 
More
Quote:
Originally Posted by mankindtw

No, it's incorrect.
Someone post source code, if it don't specify ddr type and it return default value "lpddr3".

OK. So this 'lpddr3' is printed based on the /proc/ddr_info value (DDR_TYPE_ADDR&0x00000FFF)
which is the "real" one. Do you have the same 0x401 value ? Our flash chips are obviously from different manufacturers.
Code:
current_bootloader_log: ddr info 0x00000401
While we are at the possible hardware variations: there are 5 LCD panels supported by the kernel:
Code:
JDI_R63452_6P0
JDI_NT35695_CUT3_1
LG_TD4322_6P0
LG_ER69006A
SHARP_TD4322_6P0
I have LG_TD4322_6P0.
This info is also visible on the kernel commandline
Code:
boardid=0x00001585 productid=0x3a001414 ufs_product_name=KLUCG4J1EB-B0B1 LCD_ID=0
22nd April 2017, 04:04 PM |#6  
OP Senior Member
Thanks Meter: 397
 
More
Quote:
Originally Posted by user4774

OK. So this 'lpddr3' is printed based on the /proc/ddr_info value (DDR_TYPE_ADDR&0x00000FFF)
which is the "real" one. Do you have the same 0x401 value ? Our flash chips are obviously from different manufacturers.

I have same lpddr3 from /proc/ddr_rod, but couple of kernel log message show lpddr4.
The Following User Says Thank You to mankindtw For This Useful Post: [ View ] Gift mankindtw Ad-Free
22nd April 2017, 04:13 PM |#7  
5[Strogino]'s Avatar
Senior Member
Flag Moscow
Thanks Meter: 408
 
Donate to Me
More
1. Can you post command to get info about ROM type? Ufs and version or eMMC and version. I want stop hysteria about memory types and don't trust benchmarks.
2. It would be great if somebody will post command to get info about display. 5 different displays is interesting fact
22nd April 2017, 10:08 PM |#8  
Member
Flag München
Thanks Meter: 20
 
More
Quote:
Originally Posted by 5[Strogino]

1. Can you post command to get info about ROM type? Ufs and version or eMMC and version.

The lsscsi command is not included in busybox, so you need to peek yourself in /sys/bus/scsi
Code:
HWMHA:/data/data # cat /sys/bus/scsi/devices/0:0:0:0/vendor
SAMSUNG 
HWMHA:/data/data # cat /sys/bus/scsi/devices/0:0:0:0/model                     
KLUCG4J1EB-B0B1 
HWMHA:/data/data # cat /proc/ddr_info                                          
ddr_info:
0x401
Quote:

2. It would be great if somebody will post command to get info about display. 5 different displays is interesting fact

This is more tricky. The grep panel_probe /splash2/kmsg_log provides such output:
Code:
display: [display]mipi_lg_panel_probe_TD4322: hisilicon,mipi_lg_TD4322_6P0
display: [display]mipi_lg_panel_probe_TD4322: lcd_bl_type=4!
display: [display]mipi_lg_panel_probe_TD4322: pxl_clk_rate=146 M
display: [display]mipi_lg_panel_probe_TD4322: lcd_bl_ic_name=LM36923YFFR!
display: [display]mipi_lg_panel_probe_TD4322: v_back_porch=28
display: [display]mipi_lg_panel_probe_TD4322: v_pulse_width=8
display: [display]mipi_lg_panel_probe_TD4322: lcd-vddio-type=1
display: [display]mipi_lg_panel_probe_TD4322: gpio_lcd_vddio = 67
display: [display]mipi_lg_panel_probe_TD4322: lcd_support_dynamic_gamma = 1
display: [display]mipi_lg_panel_probe_TD4322: hisifb_write_gm_to_reserved_mem has some problem!
The framebuffer driver is buggy too, and needs some patching RGB565 and geometry are ok.
Code:
HWMHA:/data/data # fbset -fb /dev/graphics/fb0                                 

mode "1080x1920-0"
        # D: 0.007 MHz, H: 0.006 kHz, V: 0.003 Hz
        geometry 1080 1920 1080 5760 16
        timings 146000000 23 50 28 14 20 8
        accel false
        rgba 5/11,6/5,5/0,0/0
endmode
23rd April 2017, 11:33 PM |#9  
5[Strogino]'s Avatar
Senior Member
Flag Moscow
Thanks Meter: 408
 
Donate to Me
More
Quote:
Originally Posted by user4774

The lsscsi command is not included in busybox, so you need to peek yourself in /sys/bus/scsi
This is more tricky. The grep panel_probe /splash2/kmsg_log provides such output:

Thanks. I have same chip Samsung KLUCG4J1EB-B0B1
But display is different:
Code:
[display]mipi_jdi_panel_probe_R63452: hisilicon,mipi_jdi_R63452_6P0
[display]mipi_jdi_panel_probe_R63452: lcd_bl_type=4!
[display]mipi_jdi_panel_probe_R63452: lcd_bl_ic_name=LM36923YFFR!
[display]mipi_jdi_panel_probe_R63452: pxl_clk_rate=146 M
[display]mipi_jdi_panel_probe_R63452: v_back_porch=28
[display]mipi_jdi_panel_probe_R63452: v_pulse_width=8
[display]mipi_jdi_panel_probe_R63452: lcd-vddio-type=1
[display]mipi_jdi_panel_probe_R63452: gpio_lcd_vddio = 67
[display]mipi_jdi_panel_probe_R63452: lcd_support_dynamic_gamma = 1
25th April 2017, 03:23 PM |#10  
sashimiyarou's Avatar
Junior Member
Thanks Meter: 8
 
More
Flash: SAMSUNG KLUCG4J1EB-B0B1
DDR: lpddr4
25th April 2017, 08:49 PM |#11  
5[Strogino]'s Avatar
Senior Member
Flag Moscow
Thanks Meter: 408
 
Donate to Me
More
Quote:
Originally Posted by sashimiyarou

Flash: SAMSUNG KLUCG4J1EB-B0B1
DDR: lpddr4

What's about display?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes