I have question about getting baseaddress for other devices about edk2-a72q HOT 30 CLOSED

This address i got from uefiplat.cfg in xbl.efi

from edk2-a72q.

Thank you for your reply
Are there any other device specific values that I should care?
How do I make ACPI tables?

from edk2-a72q.

Addresses in DeviceMemoryMap.h needs to be changed to make dxe's work.(uefiplat.cfg has all needed addresses)

ACPI tables in this repo, from sc7180(it's exactly same SOC as sm7125 but with stronger cores)
sm7325 most likely same as sc7280 because they share same codename "yupik"

from edk2-a72q.

So to get ACPI tables I need to extract it from SC7280 devices?

from edk2-a72q.

I changed every addresses in DeviceMemoryMap.h using my uefiplat.cfg except this

#ifdef MEMORY_8G
{0xC0000000, 0x1C0000000, EFI_RESOURCE_SYSTEM_MEMORY,
SYSTEM_MEMORY_RESOURCE_ATTR_CAPABILITIES, ARM_MEMORY_REGION_ATTRIBUTE_WRITE_BACK,
AddMem, EfiConventionalMemory},
#else
{0xC0000000, 0x140000000, EFI_RESOURCE_SYSTEM_MEMORY,
SYSTEM_MEMORY_RESOURCE_ATTR_CAPABILITIES, ARM_MEMORY_REGION_ATTRIBUTE_WRITE_BACK,
AddMem, EfiConventionalMemory},
#endif

Where did you find 0xC0000000 address?
I couldn't find this in uefiplat.cfg

from edk2-a72q.

It's from /proc/last_kmsg(xbl boot part)

I Combined Size of RAM Entry 1 and RAM Entry 2 to get 0x1C0000000
And used RAM Entry 2 Base as starting Address

I didn't used RAM Entry 0 because it's used by some things like "HYP" or "SMEM"

Edit: also you need to change GalaxyA72_6G.dsc
In 8G version i combined RAM Entry 1 Base and Size to get 0x280000000 and subtracted by 0x80000000 to get full memory size after 0x80000000

from edk2-a72q.

UEFI Start [ 1196]

• 0x09FC01000 [ 1198] Sec.efi
  ASLR : ON
  DEP : ON (RTB)
  Timer Delta : +1 mS
  RAM Entry 0 : Base 0x0080000000 Size 0x003A800000
  RAM Entry 1 : Base 0x0100000000 Size 0x0100000000
  RAM Entry 2 : Base 0x00C0000000 Size 0x0040000000

Didn't know samsung devices had /proc/last_kmsg support

So I think I changed everything but my device (Galaxy Tab S7 FE Wifi 6G RAM) keep stuck at boot screen

What is expected behaviour when edk2 boot up?
Does it show efi shell screen?

My device have vendor_boot.img and boot.img (both using android boot image version 3)
Can this be a problem?

from edk2-a72q.

In GalaxyA72.dsc Change Address to "Display Reserved" from uefiplat.cfg to make Framebuffer work.

It's seems edk2 boots.
If there is problem with boot.img it's should fail booting zImage and go to OdinApp.

from edk2-a72q.

That was it!
Changin framebuffer address did the trick

But it crashes with Synchronous Exception at 0x00000001FF2954D0
Have any clue about it?

from edk2-a72q.

Recompiled DEBUG build for more logs

from edk2-a72q.

Try to remove this line (without this line it's should get correct timer frequency)
Edit: it's seems this value is the same in sm7325

from edk2-a72q.

Maybe PcdArmArchTimer* is different on sm7325.
I never had this error before.

from edk2-a72q.

Tried removing multiple lines but no go
Any other suggestions?

Oh BTW I commented out all ACPI related lines
Can this be a problem?

from edk2-a72q.

Correct PcdArmArchTimer* is required for TimerDxe to work.

ACPI tables only used in windows.

from edk2-a72q.

[deleted]

ABL and XBL files

[deleted]

edk2 now I am using

Can this will help you?

from edk2-a72q.

Try this values:
gArmTokenSpaceGuid.PcdArmArchTimerSecIntrNum|29
gArmTokenSpaceGuid.PcdArmArchTimerIntrNum|30
gArmTokenSpaceGuid.PcdArmArchTimerHypIntrNum|0 #or 26
gArmTokenSpaceGuid.PcdArmArchTimerVirtIntrNum|27

from edk2-a72q.

Sadly still no go for both values (0 or 26)

from edk2-a72q.

Try commenting TimerDxe.inf in SMT733.dsc and SMT733.fdf and use TimerDxe.efi from xbl
FILE DRIVER = 49EA041E-6752-42CA-B0B1-7344FE2546B7 {
SECTION DXE_DEPEX = SMT733/Binary/ArmTimerDxe/ArmTimerDxe.depex
SECTION PE32 = SMT733/Binary/ArmTimerDxe/ArmTimerDxe.efi
SECTION UI = "ArmTimerDxe"
}
ArmTimerDxe.zip

from edk2-a72q.

I think it worked!

But I think UFS driver from 845 causes crash
Which tool did you use to extract efi drivers from XBL?
I might try put every efi drivers on to it

from edk2-a72q.

Yes UFSDxe from 845 uses qcom ufs protocol v3 and sm7325 most likely has v4 or v5.

I used UEFITool.exe to extract it.

from edk2-a72q.

How do I get GUID thing like this?
FILE DRIVER = 49EA041E-6752-42CA-B0B1-7344FE2546B7
Does UEFITool provide it?

from edk2-a72q.

Yes. UFSDxe has same GUID in sm7325 "0D35CD8E-97EA-4F9A-96AF-0F0D89F76567"
UFSDxe.zip

from edk2-a72q.

I think there is no error but device just automatically reboots after several times
I checked log frame by frame but there was no errors
What would be the problem?

from edk2-a72q.

UFSDxe and other drivers in xbl uses it's own DebugLib, etc. Thats why it's doesn't print errors.
It's seems UFSDxe gives Assert (in qcom edk2 prod build, assert writes to pshold address to reboot phone)

Also making UFS work on samsung can be really hard.

from edk2-a72q.

Damn if I cannot use UFS
Is there a chance that I can use SDcard instead?
My galaxy tab have SDcard slot

from edk2-a72q.

BTW disabling UFS driver did loaded efi shell
How do I type anything in efi shell?
Does usb OTG works?

from edk2-a72q.

Making SDCard work even harder, it's requires SdccDxe.efi patch(to enable driver loading, It's disabled by default because UFS boot mode is default) and PMIC.efi

OTG doesn't work without PMIC.efi

And we don't have PMIC.

from edk2-a72q.

Damn am I doomed then?
No UFS, SDcard, USB
What would be other alternatives?

from edk2-a72q.

Right now windows impossible to make work on samsung because storufs.sys causes some weird issues with Samsung UFS. (WinPE only if UFSDxe somehow works)

The only things that has working UFS is downstream linux kernel and mainline linux kernel.

from edk2-a72q.

Thank you for teaching me whole day for me.
Have a nice day

from edk2-a72q.