Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

SM-P605 based on Note 3 device tree

OP StNickZA

27th May 2014, 04:01 PM   |  #1  
OP Senior Member
Flag Durban
Thanks Meter: 147
 
534 posts
Join Date:Joined: Dec 2009
More
Hey there,

I hope that you don't mind me posting here, but I figure that this is the best place to get some assistance. I'm attempting to port CM11 to the Galaxy Note 10.1 2014 Edition (SM-P605). This is a very similar device to the Note 3, and as such, I've started by forking the Note 3 device tree. This is the first port that I've attempted, so I am very new to all of this.

I am using the Samsung stock 4.3 kernel sources for my device. When I run "make recoveryimage", everything seems to work fine and I get a recovery.img file. However, despite fiddling with all manner of settings in BoardConfig.mk, I cannot get it to boot. It just gets itself into a bootloop, saying "Recovery boooting..." at the top left, and then rinse-repeat.

I suspect that my problem lies with the ramdisk, and/or the ramdisk offset. The following is taken from the Note 3 BoardConfig.mk.

Code:
# Kernel
BOARD_KERNEL_CMDLINE := console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F
BOARD_KERNEL_BASE := 0x00000000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02900000 --tags_offset 0x02700000
BOARD_KERNEL_SEPARATED_DT := true
BOARD_CUSTOM_BOOTIMG_MK := device/samsung/hlte/mkbootimg.mk
I presume that those offsets are different per device. After a bit of research, I came across an app called unmkbootimg which can supposedly tell me what I need to know. After feeding it my boot.img, I got the following result.

Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <kuisma@ping.se>
Kernel size 7536872
Kernel address 0x8000
Ramdisk size 1375263
Ramdisk address 0x2000000
Secondary size 0
Secondary address 0xf00000
Kernel tags address 0x1e00000
Flash page size 2048
Board name is ""
Command line "console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F"
*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_KERNEL_ADDR is 0xFE208100
OFF_RAMDISK_ADDR is 0x00200100
OFF_SECOND_ADDR is 0xFF100100
Please modify mkbootimg.c using the above values to build your image.
****************
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x1dfff00 --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F' -o new_boot.img
---------------
I've tried 0x00200100 and 0x2000000 for ramdisk offset (purely because I am not sure which one is correct there), but both give the same result (ie. nothing).

I've also tried outputting the log to the LCD with

Code:
BOARD_KERNEL_CMDLINE := console=tty0,115200 fbcon=rotate:1 fbcon=font:VGA8x8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F
This made no difference at all either.

I'm not sure what else to try, so I'm looking for any suggestions please.

If you'd like to take a look at my device tree, it is here:
https://github.com/StNick

Thanks in advance.
28th May 2014, 03:15 PM   |  #2  
Senior Member
Flag Minnesota
Thanks Meter: 1,021
 
467 posts
Join Date:Joined: Jan 2008
More
Code:
*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_KERNEL_ADDR is 0xFE208100
OFF_RAMDISK_ADDR is 0x00200100
OFF_SECOND_ADDR is 0xFF100100
Please modify mkbootimg.c using the above values to build your image.
****************
  • Just to get that out of the way, did you try the above values?
  • What board does the SM-P605 use? (MSM8974AB?) Is it a Qualcomm or Exynos device?
  • You are able to get no output?

This may or may not be the right place to post such a question, but I think you'd be more likely to find the answer to your question here
29th May 2014, 10:31 AM   |  #3  
Senior Member
Thanks Meter: 331
 
1,144 posts
Join Date:Joined: Oct 2012
Quote:
Originally Posted by StNickZA

Hey there,

I hope that you don't mind me posting here, but I figure that this is the best place to get some assistance. I'm attempting to port CM11 to the Galaxy Note 10.1 2014 Edition (SM-P605).
...

Are you certain that this one isn't a better place to start:

http://forum.xda-developers.com/gala...14/development
29th May 2014, 10:34 AM   |  #4  
OP Senior Member
Flag Durban
Thanks Meter: 147
 
534 posts
Join Date:Joined: Dec 2009
More
Quote:
Originally Posted by xclub_101

Are you certain that this one isn't a better place to start:

http://forum.xda-developers.com/gala...14/development

Fairly certain, yes. The work being done on the Note 10.1 2014 Edition all pertains to the Exynos version which is less relevant to my device than the Note 3.

Just looking for some help from guys that have built for a similar device.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes