ungeskriptet__ has quit [Remote host closed the connection]
ungeskriptet has joined #sm7150-mainline
<soupborsh[m]> Hello, I want to try to boot android using U-Boot. Is there some memory map avialable, I do not know where to load images to?
<soupborsh[m]> I put my boot.img and dtbo.img into cust partition, it is scsi 0:7
<soupborsh[m]> soupborsh[m]: Yes there is memory map in bdinfo
<soupborsh[m]> I did load boot.img to 0x110000000 and dtbo.img to 0x120000000. However this command fails:
<soupborsh[m]> ```=> abootimg get dtb --index=0 0x120000000 0x1800000
<soupborsh[m]> Incorrect boot image header```
<soupborsh[m]> * I did load boot.img to 0x110000000 and dtbo.img to 0x120000000. However this command fails:... (full message at <https://matrix.org/oftc/media/v1/media/download/AZoQVznupoTvhCHJ-lbWHAcevZRwmZQJSFAO8MPJmxGnpdysIIuS3ahOrzX_y_Yut9wajyDxNIRV5Id3a9If1iRCeWH4zLiQAG1hdHJpeC5vcmcvZmVWeURCYmZFaEJ2dVhQcE1rSktuUUJJ>)
<z1r343l2[m]> Where did u store them
<z1r343l2[m]> Try like
<z1r343l2[m]> abootimg get dtb --index=0 dtb0_start dtb0_size
<soupborsh[m]> <soupborsh[m]> "I put my boot.img and dtbo.img..." <- You mean boot.img and dtbo.img? I got them using dd and then placed into cust partition formatted with fat32
<z1r343l2[m]> Hmm makes sense
<soupborsh[m]> I did abootimg addr 0x110000000 and now that my previous command does not produce output.
<soupborsh[m]> abootimg get ver outputs 2
<soupborsh[m]> If needed here is how I loaded those images into memory:
<soupborsh[m]> ```
<soupborsh[m]> I do not know if this adresses are correct, they are random. Do not pay attention to file names, I just use Lindroid.
<soupborsh[m]> s/use/used/
<z1r343l2[m]> is the dtb maybe as separate image and not in boot in this case?
<soupborsh[m]> I think it is dtbo.img but seems like documentation assumes that it is in boot.img
<soupborsh[m]> Maybe there is a way to extract fdt from dtbo and then load that instead
<soupborsh[m]> Thanks. I guess dtb/fdt could be obtained using this: https://wiki.postmarketos.org/wiki/SM7150_Mainlining#Extracting_downstream_device_tree_blob
<z1r343l2[m]> soupborsh[m]: Oh interesting
<soupborsh[m]> I will try later, I will go eat
<soupborsh[m]> Then on some small amount of text black artifacts were drawn and phone rebooted.
<soupborsh[m]> Maybe I think it loads kernel where u-boot is and that messes everything up, 0x8000 is reserved memory here
<soupborsh[m]> Maybe I need to change load address of kernel
<soupborsh[m]> * of kernel and dtb and something more
<soupborsh[m]> Please tell me how to it if you now
<z1r343l2[m]> It say 2 different Things Here O.o
ungeskriptet_ has joined #sm7150-mainline
ungeskriptet has quit [Ping timeout: 480 seconds]
<Vilez[m]> Hi there
<Vilez[m]> can anyone help me? how can i find info like that?
<Vilez[m]> I'm trying to find the panel model and manufacturer of sweet_k6a but cannot find anything, i tried to search for schematics or anything that can help but couldnt find anything related
<Vilez[m]> * Hi there
<Vilez[m]> I'm trying to find the model and manufacturer of the panel of sweet\_k6a (k6-38-0e-0b-dsc) but cannot find anything, i tried to search for schematics or anything that can help but couldnt find anything related
<Vilez[m]> can anyone help me? how can i find info like that?
aka_[m] has joined #sm7150-mainline
<aka_[m]> <Vilez[m]> "Hi there..." <- panel vendor is AMS OSRAM
<aka_[m]> not sure about controller
<aka_[m]> xiaomeme loves novatek but not sure if they do controllers for oleds
<soupborsh[m]> <z1r343l2[m]> "It say 2 different Things Here O..." <- I tried with - for ramdisk too
<soupborsh[m]> It did go little bit further
<soupborsh[m]> ```
<Vilez[m]> <aka_[m]> "panel vendor is AMS OSRAM" <- Thanks,
<Vilez[m]> How did you find this?
<aka_[m]> seems im wrong
<aka_[m]> display alone on photos
<aka_[m]> have AMS number on it
<aka_[m]> AMS seems to be also company but maybe its really samsung's oled
<Vilez[m]> the panel is too similar to redmi note 10 pro's one( k6-38-0a-0c-dsc) which is looks like that is samsung ams667yr01(
<Vilez[m]> Using driver of the redmi note 10 pro's is mostly working on sweet_k6a's panel, it's just that the color looks wrong, they're darker and generally they're orange-ish
<z1r343l2[m]> Have a normal sweet global If that helps Findling out
<z1r343l2[m]> Samsung E3 SuperAMOLED i think here
<z1r343l2[m]> <soupborsh[m]> "=> fatload scsi 0:7 0x110000000..." <- say, how do u even enter commands, oth usb-otg and usb serial dont really seem to work in u-boot on my end
<z1r343l2[m]> s/oth/both/
<soupborsh[m]> usb serial works for me
<z1r343l2[m]> should it show up as a ty?
<z1r343l2[m]> *ty
<soupborsh[m]> I do: picocom -b 115200 /dev/ttyACM0 -g path/to/log.txt
<z1r343l2[m]> s/ty/tty/
<soupborsh[m]> IDK why it is /dev/ttyACM0
<z1r343l2[m]> ah serial seem to work i just didnt see the device without root perms
<soupborsh[m]> I added my user to some group, I think it was tty to use picocom without root.
<soupborsh[m]> or "dialout"
<soupborsh[m]> * ~or "dialout"~ not this
<soupborsh[m]> I think that group is uucp
<z1r343l2[m]> should it see my internal storage as ammc normally?
<soupborsh[m]> For me it is scsi for some reason, it does not see emmc
<soupborsh[m]> I hope someone smart will figure out how to boot Android. That will allow dual boot.
<soupborsh[m]> * will allow easy dual boot.
<soupborsh[m]> I extracted android boot.img using unpack_bootimg and then packed it again into boot_new.img but with --base 0xf0000000. Random address that u-boot did not complain about.
<z1r343l2[m]> how do i load the bootimage from a file rather the partition
<soupborsh[m]> Also I think it uses 2 dtbs, since there is kernel, ramdisk and dtb in boot.img.
<z1r343l2[m]> did u try that merging thing it mentions in the doc
<soupborsh[m]> z1r343l2[m]: I am not pro, but I did copy boot partition from android to boot.img file and then I formatted cust partition to fat32 and placed it there. From u-boot I can load it into some address by using:
<soupborsh[m]> `fatload scsi 0:7 SOME_ADDRESS boot.img`
<z1r343l2[m]> thats what i needed
<soupborsh[m]> 7th partition in 0th scsi device is cust partition on my surya.
<soupborsh[m]> * boot.img file using dd and then
<soupborsh[m]> <z1r343l2[m]> "did u try that merging thing..." <- No, I did not. Will probably try further only tomorow, it is late already.
<soupborsh[m]> I am learning in real time as I try random things.
<soupborsh[m]> Maybe I should ask in pmos low level group.
<soupborsh[m]> * is late here already.
<soupborsh[m]> Ok, goodbye it was a pleasure to communicate with you.
<soupborsh[m]> I needed to return to android so I flashed dtbo and boot but for test with boot_new.img with different base, it did not boot successfully. It boots okay with original base.
<soupborsh[m]> s/base/img/
<soupborsh[m]> Maybe U-Boot should be relocated and kernel booted where it supposed to be booted.
ungeskriptet_ has quit [Remote host closed the connection]
ungeskriptet has joined #sm7150-mainline