Origen_quad now needs 4 bootloader binaries instead of three

Bug #1155702 reported by vishal
30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Fix Released
Critical
Fahad Kunnathadi
Linaro Image Tools
Fix Released
Critical
Milo Casagrande

Bug Description

We now have 4 bootloader binaries that need to be flashed to boot origen quad. Here is the procedure:
sudo dd if=origen_quad.bl1.bin of=/dev/sdX bs=512 seek=1
sudo dd if=origen_quad-spl.bin.signed of=/dev/sdX bs=512 seek=31
sudo dd if=u-boot.bin of=/dev/sdX bs=512 seek=63
sudo dd if=exynos4x12.tzsw.signed.img of=/dev/sdX bs=512 seek=761

length field, if needed could be with number of SECTORS
origen_quad.bl1.bin = 30
origen_quad-spl.bin.signed = 31
u-boot.bin = 698
exynos4x12.tzsw.signed.img 312

These binaries can be assumed to be in the boot.tar.bz2. Let me know once the bug is assigned. I will then share the tarball containing these binaries. Fahad can help in testing the experimental branch.

The binaries can be found on insignal's website as well:
http://forum.insignal.co.kr/viewtopic.php?f=6&t=66&p=4078#p4078

Related branches

vishal (vishalbhoj)
Changed in linaro-image-tools:
assignee: nobody → Fahad Kunnathadi (fahad-k)
assignee: Fahad Kunnathadi (fahad-k) → nobody
Changed in linaro-android:
assignee: nobody → Fahad Kunnathadi (fahad-k)
importance: Undecided → Critical
Fathi Boudra (fboudra)
Changed in linaro-image-tools:
status: New → Confirmed
Changed in linaro-android:
status: New → Confirmed
Changed in linaro-image-tools:
importance: Undecided → Critical
assignee: nobody → Milo Casagrande (milo)
milestone: none → 2013.03
Changed in linaro-android:
milestone: none → 13.03
Revision history for this message
Milo Casagrande (milo) wrote :

Hi,

quoting from the first commnet:

"These binaries can be assumed to be in the boot.tar.bz2"

Do we have to assume a special folder inside the boot tarball, or will they just be in the "root" of the tarball?
Also, do we already have a boot tarball with those file so that I can locally test it?

Revision history for this message
Milo Casagrande (milo) wrote :

The linked branch adds support for the Origen Quad bootloader binaries.
It needs to be tested: I can create an image file and I can write on an SD card, but I cannot test further.

Changed in linaro-image-tools:
status: Confirmed → In Progress
Revision history for this message
Fahad Kunnathadi (fahad-k) wrote :

With the changes, Ive tested the l-a-m-c code, it boots up

But we have some problem with bootargs , so I have copied this config file in boot folder and changed the envstart to 1599
samsung_env_start: 1599,
As tushar informed the envstart has changed
the config file copied in boot folder is attached.

This isent getting reflected with l-a-m-c flashing. is there something we have to do on it.

Revision history for this message
Milo Casagrande (milo) wrote :

Hi Fahad,

I can change the "samsung_env_start" in the code, since that value is also present there, but that means it will be changed for all the use of the Origen Quad board.

If that value really changed and the old one is not used anymore, I guess it will be safe to change, otherwise, what you can do is update the Android config file with the new value.

I'm not sure how much backward compatible it has to be.

So the option are two:
- change the value in the code, with possible backward incompatibility
- change the value in the shipped config file

Revision history for this message
vishal (vishalbhoj) wrote :

We have never had an official Origen quad release till date. We need not be backward compatible here since we don't have the binaries which were needed to older builds.

Also keep it configurable in a way that the config from hwpack overrides the default value.

Revision history for this message
Milo Casagrande (milo) wrote : Re: [Bug 1155702] Re: Origen_quad now needs 4 bootloader binaries instead of three

On Wed, Mar 20, 2013 at 10:36 AM, vishal <email address hidden> wrote:
> We have never had an official Origen quad release till date. We need not
> be backward compatible here since we don't have the binaries which were
> needed to older builds.

That is done, I changed the value in the code.

> Also keep it configurable in a way that the config from hwpack overrides
> the default value.

When we added the Android hwpack support, it was done in that way: if
you pass a config file on the command line, it overrides everything.

--
Milo Casagrande | Infrastructure Team
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

Fathi Boudra (fboudra)
Changed in linaro-image-tools:
status: In Progress → Fix Committed
Revision history for this message
Fahad Kunnathadi (fahad-k) wrote :

Hi Milo,

The changes, was supposed to update the bootenv,

But, I am not getting the bootenv updated yet.
We will need to cross verify with tushar, if somethings not right, about bootenv .

Revision history for this message
Milo Casagrande (milo) wrote :

Hi Fahad,

On Wed, Mar 20, 2013 at 7:00 PM, Fahad Kunnathadi <email address hidden> wrote:
> Hi Milo,
>
> The changes, was supposed to update the bootenv,

the changes did not touch bootenv directly, and bootenv should not be
modified by those changes.
If also that needs to be updated, it is better to cross check and
understand what the expected bootenv should be.

Let me know.

--
Milo Casagrande | Infrastructure Team
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

Revision history for this message
Fahad Kunnathadi (fahad-k) wrote :

Hi Milo,
After some experiments on bootenv we found we can erase the bootenv set by command
dd of=/dev/sdc if=/dev/zero bs=512 count=1 seek=1601

So 1601 is the actual bootenv location.
We did the same change replacing 1599 in origen_quad config .
So the bootenv , dont get set after doing the change. check the patch attached.

Also we had the config file in place , then it must give the actual bootenv while using printenv.

Revision history for this message
Milo Casagrande (milo) wrote :

Hi Fahad,

On Thu, Mar 21, 2013 at 9:44 AM, Fahad Kunnathadi <email address hidden> wrote:
> After some experiments on bootenv we found we can erase the bootenv set by command
> dd of=/dev/sdc if=/dev/zero bs=512 count=1 seek=1601
>
> So 1601 is the actual bootenv location.
> We did the same change replacing 1599 in origen_quad config .
> So the bootenv , dont get set after doing the change. check the patch attached.

I applied the patch, but have to understand a couple of things:
- your patch changed the samsung_env_start value also for *all* other
boards, not only for the Origen Quad: is that the new value for all
Samsung based boards (Origen, Origen Quad, SMDK...), or is it just to
be used for Origen Quad?
- I'm not getting the serial_tty line: is it really "ttySAC2 test"?
With that line the bootargs command will result in this:

'console=ttySAC2 test,115200n8 test root=UUID=deadbeef rootwait ro'

--
Milo Casagrande | Infrastructure Team
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

Revision history for this message
Fahad Kunnathadi (fahad-k) wrote :

Hi milo,
The patch was just for informative, it is not needed to change for all the board..
Only thing needed to change out of it is 1599 to 1601 in only for Origen_quad config .

Then it was the u-boot issue , the boot.scr file was not getting read from u-boot
we have fixed that now.

thanks for the support

Revision history for this message
Milo Casagrande (milo) wrote :

Hello Fahad,

can you please try the branc linked on this bug? It now contains the
new changes.
Let me know.

--
Milo Casagrande | Infrastructure Team
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

Revision history for this message
Fahad Kunnathadi (fahad-k) wrote :

Hi milo,

Works fine .

regards
Fahad K

vishal (vishalbhoj)
Changed in linaro-android:
status: Confirmed → Fix Committed
Milo Casagrande (milo)
Changed in linaro-image-tools:
status: Fix Committed → Fix Released
Fathi Boudra (fboudra)
Changed in linaro-android:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.