[Avila] Redboot Upgrade

[Ahmet Basagalar]

Let me answer my own questions: (This is for GW2348-4 platform)

1- The current redboot does not allow a remote upgrade from older version 
due to corrupt EEPROM. You need to modify 
packages/hal/arm/xscale/ixdp425/current/src/ixdp425_misc.c.

Here is the diff:

794c794,796
<                               return 1;
---
>                               //Ahmet
>                               //return 1;
>                               strcpy(buf, def);
857c859,860
<                       strcpy(buf, def);
---
>                       //Ahmet - default set to 64 MB on timeout
>                       strcpy(buf, "64");
891c894,897
<               _rb_gets(buf, sizeof(buf), 0);
---
>               _rb_gets(buf, sizeof(buf), 5000);
>               if (ret == _GETS_TIMEOUT ){
>                       strcpy(buf, "y");
>               }

Of course you need to fix GPIO14 as well in addition to the above, this 
matter was discussed on an earlier thread.

2- You need to enable CONFIG_ARCH_IXDP425 in addition to CONFIG_MACH_AVILA, 
and the new kernel will work with both redboots!

Thanks,
Ahmet
----- Original Message ----- 
From: "Ahmet Basagalar" <ahmet at thebluezone.com>
To: "avila" <avila at lists.gateworks.com>
Sent: Tuesday, May 13, 2008 10:14 AM
Subject: Redboot Upgrade


> Hi,
>
> I have two questions:
>
> 1- When we upgrade to new redboot that comes with BSP 0.7.1, it is 
> complaining about "corrupt EEPROM" and tries to write values to EEPROM. Is 
> this process automatic, in other words can I upgrade the Redboot on a 
> remote system without any user interaction?
> Also what would it take to write to the EEPROM location before upgrade so 
> it does not complain and what is the data structure?
>
> 2- The new kernel is uncompatible with older Redboot due to machine id I 
> guess. How can I modify this new kernel so it can work with old and new 
> Redboot at the sametime? That way I do not need to worry about upgrading 
> redboot on remote systems.
>
> Thanks,
> Ahmet