[DEV] Spica Bootloader

[nebkat]

Thanks to darth_llamah and ften we have have found the spica bootloader sources. The original link is here (src/kernel/bootloader), but a version with some of my fixes is available at my github 2.6.32 repo. If you are going to use from my repo just modify the directories in this commit (https://github.com/nebkat/I5700-kern...7c7e9b459f4556).

Now I'm stuck at this, so I need to compile libtxsr.a.

Please only post development related posts.

[tom3q]

Thanks to darth_llamah and ften we have have found the spica bootloader sources. The original link is here

These aren't Spica sources, but Acclaim sources. There may (and probably do) exist some subtle (or even significant) differences between these two phones.

My recommendation is to stay away from the bootloader and forget that such thing exists. We don't really need to change it. This is really dangerous and if you don't have proper hardware (JTAG interface) you may be sure that you will end up with a seriously bricked phone.

[nebkat]

But in the config files spica is there Kernel/bootloader/loke/configs/spica/spica-rev02-bootloader.config. Doesn't that works for spica because they wouldn't include spica config if its incompatible. I forgot to mention that we need people with jtag for testing.

[ker0ltjuh]

isnt it easier to port roms etc when you have an unlocked bootloader?

[tom3q]

Doesn't that works for spica because they wouldn't include spica config if its incompatible.

You never can be sure. This is Samsung and they may just have hardcoded some Acclaim-specific values into source code. And this is not the only way what they could make the sources incompatible with Spica. So this is only safe if you've got a JTAG interface.

Anyway, there is still no point in modifying the bootloader. Our bootloader IS already unlocked. Our bootloader does everything Linux kernel expects from it. Nothing less, nothing more.

[nebkat]

Our bootloader is unlocked afaik. I have made some progress in compilation but now I got this:

/root/android/kernel/Kernel/bootloader/loke/common/txsr/libtxsr.a(BMLInterface.o): In function `BML_StorePIExt':
/home/release/Customer/SEC.TELE/NAOS_Android_S3C6410/build_current/drivers/xsr/Core/BML/BMLInterface.c:8500: undefined reference to `BBM_UpdatePIExt'
/root/android/kernel/Kernel/bootloader/loke/common/txsr/libtxsr.a(BMLInterface.o): In function `_GenSWECC':
/home/release/Customer/SEC.TELE/NAOS_Android_S3C6410/build_current/drivers/xsr/Core/BML/BMLInterface.c:5319: undefined reference to `ECC_GenM'
/home/release/Customer/SEC.TELE/NAOS_Android_S3C6410/build_current/drivers/xsr/Core/BML/BMLInterface.c:5337: undefined reference to `ECC_GenS'
/root/android/kernel/Kernel/bootloader/loke/common/txsr/libtxsr.a(BMLInterface.o): In function `_ChkSWECC':
/home/release/Customer/SEC.TELE/NAOS_Android_S3C6410/build_current/drivers/xsr/Core/BML/BMLInterface.c:5475: undefined reference to `ECC_GenM'
/home/release/Customer/SEC.TELE/NAOS_Android_S3C6410/build_current/drivers/xsr/Core/BML/BMLInterface.c:5488: undefined reference to `ECC_CompM'
/home/release/Customer/SEC.TELE/NAOS_Android_S3C6410/build_current/drivers/xsr/Core/BML/BMLInterface.c:5539: undefined reference to `ECC_GenS'
/home/release/Customer/SEC.TELE/NAOS_Android_S3C6410/build_current/drivers/xsr/Core/BML/BMLInterface.c:5549: undefined reference to `ECC_CompS'
/root/android/kernel/Kernel/bootloader/loke/common/txsr/libtxsr.a(BMLInterface.o): In function `BML_Format':
/home/release/Customer/SEC.TELE/NAOS_Android_S3C6410/build_current/drivers/xsr/Core/BML/BMLInterface.c:3742: undefined reference to `BBM_Format'
/home/release/Customer/SEC.TELE/NAOS_Android_S3C6410/build_current/drivers/xsr/Core/BML/BMLInterface.c:3764: undefined reference to `BBM_Repartition'
make[2]: *** [Pbl.bin] Error 1
make[1]: *** [_dir_arch/arm/mach-s3c] Error 2
make: *** [_dir_Pbl] Error 2

[rrrulo]

isnt it easier to port roms etc when you have an unlocked bootloader?

And kernels! All that stuff I guess. Maybe we can make a collect.via paypal to buy a jtag for the dev working on bootloader.

Enviado desde mi GT-I5700 usando Tapatalk

[tom3q]

And kernels! All that stuff I guess. Maybe we can make a collect.via paypal to buy a jtag for the dev working on bootloader.

Please read my post from above. ([DEV] Spica Bootloader)

And it isn't hard to port kernels for Spica, because of the bootloader, hardware or anything. It is, because original kernels contain seriously broken drivers, written in an unportable way, so it's better to rewrite them from scratch than modify them for API changes in newer kernels (and this takes time).

[ker0ltjuh]

Please read my post from above. ([DEV] Spica Bootloader)

And it isn't hard to port kernels for Spica, because of the bootloader, hardware or anything. It is, because original kernels contain seriously broken drivers, written in an unportable way, so it's better to rewrite them from scratch than modify them for API changes in newer kernels (and this takes time).

but still if we have the real bootloader sources and we can compile/modifie them, maybe it doesnt matter but its good for samdroid image :P

[tom3q]

but still if we have the real bootloader sources and we can compile/modifie them, maybe it doesnt matter but its good for samdroid image :P

It's not good, because I can already imagine some random people trying to compile them and bricking their phones... Bootloader is where the fool-proof thing ends.
IMHO, the "modify only if you really need to" methodology is the best possible.