[Project] Uboot

How could this kill the device?
Is Uboot going to overwrite eboot, or what?

Hi LVL, that's been a while.

It's not (yet) going to overwrite eboot.
In the future that's my goal but before we can do that we should be sure that its fully functional ofcourse.

Thing is that I am not fully sure how the nand operations in uboot work (stil need to research this) I presume it will not try to write towards nand.
But if it works in a similar way like a linux kernel we might end up with a problem like r3wdy if you remind that one.
So the reason i inform that it may be dangerous, is due that fact

On the other hand, I did not change the base from uboot yet before merging to the xip.bin, so It may be that uboot wont boot due a bad base address :P

Evow04, I tested your Uboot XIP and unfortuantly it doesn't work

Originally Posted by HondaRacer

Evow04, I tested your Uboot XIP and unfortuantly it doesn't work

oh yeah, thank you for sacrificing you phone
did you was able to rebuild it?

Originally Posted by misi66

oh yeah, thank you for sacrificing you phone
did you was able to rebuild it?

Yes, I was able to fix it. I talked to Evow04 about what settings he choose in MPack. It isn't more danger than installing a Android firmware.

So did he figured out what might be a problem?

Thanks for the video HondaRacer,
I think it might be a wrong base address, or a kernel crash but we can only know this by using a debug cable

I`m having little time today so I will see when I can try again to build an other package.

figured out what might be a problem

Let´s hope we do soon :-)


Anyone having an USB debug cable and M8?

Alright,
made a new build v0.2 :-)

It should start up (I hope),
but not yet boot into android, it´s a build to see if I can get Uboot up and running.

For those who want to know the risk, no more then v0.1 & according HondaRacer that means no more risk then using Android on M8.
Xip.bin is made with Mpack using the default settings like you use to build a dualboot.

If it runs there will still be a lot of work to do :-)

-made previous download link for v0.1 privat since it did not work -

Why you can't test this version?!
You don't have a M8 and try to help us?

during the day time I am at work, so I have no access to USB ports :-)
& Made this build last night just before I went to sleep but just managed to pack it in a xip during a boring meeting:P So I am interested to know if it works without needing to wait until this late evening :-)

Originally Posted by evow04

during the day time I am at work, so I have no access to USB ports :-)
& Made this build last night just before I went to sleep but just managed to pack it in a xip during a boring meeting:P So I am interested to know if it works without needing to wait until this late evening :-)

No problem Evow04, I build a Uboot XIP and post my results

Tested v0.2. It has the same problem as v0.1 (stuck on 'Meizu' screen)

@HondaRacer, yes I forgot to implement

Code:

CONFIG_SHOW_BOOT_PROGRESS

So the only real output should come via serial out, very stupid of me !

I'll try a next build this weekend so I can check for myself, but see your PM's, I have send something interesting to you.

Damned, some good & bad news.

the good, managed to build a new debug cable, worked fine on M8SE.
the bad, I finished my current work and I broke my plug & ttl convertor :@

I'll try to fix it but it's a tiny piece of crap so I might end up buying a new TTL convertor & will look for some one who can solder better then me to make stronger connections on the usb plug.

And in some other news, apparently we all overlooked the fact that Sepa had a uboot build that was up and running. But not in the way I want;
eboot load tinyloader load uboot load dnw & that one finally loaded Zimage over USB.
I want (in phase 1):
eboot load tinyloader load uboot mount Movinand boot Zimage

So I looked at SEPA & Bills code to find out they are similar, So I tried my own v0.2 build on my SE without luck, but I tried SEPA build.. also with no luck.

For the ones interested here is a stripped debug, they hang at a code "K45"

Code:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2011.03.18 20:21:26 =~=~=~=~=~=~=~=~=~=~=~=
//////////////////////////////////////////Evow04 build///////////////////////////////////////////////
::IUD_IOControl:FLASHIMAGE!!
::FlashImage:begin to write os image to boot media!!
+WriteOSImageToBootMedia: g_dwTocEntry =1, ImageStart: 0x80100000, ImageLength: 0x7f00528, LaunchAddr:0x8010e294
Progress Percent:2%
Progress Percent:100%

LaunchAddr=0x80030000 PhysicalJump=0x50030000
Microsoft Windows CE Bootloader Common Library Version 1.4 Built Aug 20 2009 18:21:23
Microsoft Windows CE Bootloader for the Samsung SMDK6410 Version 2.4 Built Sep 20 2009(2)
[Eboot] ++InitializeDisplay()
Press [SPACE] to enter boot monitor.
Press [ENTER] to download image stored on boot media, or [SPACE] to enter boot monitor.
Initiating image download in 2 seconds. 
Starting auto-download ... 

++ShadowNK()
M8TinyLoader: Check UART2.

Selected Android.
Found zImage magic at 0x518785A4.

K45

//////////////////////////////////////////sepa build///////////////////////////////////////////////
Windows CE Kernel for ARM (Thumb Enabled) Built on Oct 20 2009 at 18:39:19
-- Shadow Eboot --
LaunchAddr=0x80030000 PhysicalJump=0x50030000
Microsoft Windows CE Bootloader Common Library Version 1.4 Built Aug 20 2009 18:21:23
Microsoft Windows CE Bootloader for the Samsung SMDK6410 Version 2.4 Built Sep 20 2009(2)
Press [SPACE] to enter boot monitor.
.Press [ENTER] to download image stored on boot media, or [SPACE] to enter boot monitor.
Initiating image download in 2 seconds. 
Starting auto-download ... 

++ShadowNK()
M8TinyLoader: Check UART2.

Selected Android.
Selected Android.
Found zImage magic at 0x518785A4.

K45

So It seems to be normal that HondaRacer couldn't run my build.

ps, I also found out that onscreen debug should need a LCD driver, but I am sure we can rip this from Bill's or LBE's source . Only need to find out to activate it in uboot source code.

if someone wanted to know if I made any progress:
I did not spend any time on it for now, I should try to make a new build where I edit the config.mk to get TEXT_BASE on 0x518785A4 (it matches the found location in the above log file, my current text base is 0x50107000).

I hope that this mod would solve my issue that it wont start.
But I am not in the mood to reflash my M8 again cause I am tired to backup & restore all the time:-)
in a few weeks I´ve got some time off, maybe I will try it at that moment.

but for those that would try to do some own stuff I added the sources to our wiki
http://wiki.meizume.com/Meizu_M8_Uboot
http://wiki.meizume.com/Meizu_M8_Uboot_Build

UPDATE 11/05/11
So I just made my new build like documented above.
The uboot binary is uploaded here & will try it tomorow in the evening.
Can do it right now since i need to search my ttl debug cable first