[Avila] Always checksum error after flashing new redboot image

[José Luis Ferrer]

Hi all,

    Yes, the hardware configuration of all the boards is the same, all 
with eeproms, although the PCB's version are different (2 boards 
0221004B-02 and 1 board 0221004B-01) which don't have to create any 
issue (moreover, the board that fails is -02). If there's some 
configuration difference I am not able to see it now :/
    However, when I boot the same Linux image on that board, it only 
detects 32MB of SDRAM memory instead of the 64MB taht should be 
available (the memory chips in all the boards have the same ID). This 
issue is curious, since the old Redboot version was for a 64MB memory 
and worked fine (I'll check ASAP is the old version of redboot with old 
Linux image detects the 64MB).
   
    The econfig tool seems to work properly, I've executed several times 
on redboot console and checked the values listing with econfig -l and 
eeprom tools, also the checksum in the eeprom varies after changing some 
values. After changing the values, and swithching the power (not using 
the reset command) the same prompt about the checksum error message 
appears again, with the last values configured with the last econfig 
execution.

    Thanks for your quick answers,

José Luis Ferrer

Chris Lang escribió:
> Jose,Tim,
>
> Regarding Jose's problems, I find it interesting that the econfig tool
> is not working on 1 board but it is working on the other 2 boards. Are
> all of these boards identical as far as the hardware configuration? Some
> of our O.E.M's, i.e. Valemount, do not load an eeprom onto the board.
> This would result in the issue that you are seeing. If they are the same
> hardware configuration, then there may be a different issue. Does the
> econfig tool seem to run successfully? At the end of the tool, does it
> output a message with periods showing that it is writing successfully?
>
> As far as the things Tim points out. The re-read I believe had been
> taken care of, this was a redboot issue that I believe I worked out do
> to the fact that when you issue a redboot 'reset' command, it does not
> actually re-initialize any hardware including chip-selects, etc... I
> will revisit this to try to clean-up the software reset.
>
> The boot_script_data does get taken as input and it is very much an
> annoyance. This is an outstanding issue in this redboot, but do to the
> fact that it was just an annoyance and not a 'show stopper' it was
> pushed through this release, and it will be fixed in subsequent
> release's.
>
> The flash timings that Tim has reported are being looked at and will
> most likely be adjusted to ensure proper booting 100% of the time.
>
> Thanks for the feedback.
>
> Chris Lang
> Gateworks Corporation
> clang at gateworks.com
>
>
> On Mon, 2007-10-08 at 09:04 -0700, Tim Harvey wrote:
>   
>> Jose,
>>
>> I've noticed a few issues with the new bootloader that you should watch out for:
>>   - after updating the eeprom the bootloader does not 're-read' the
>> values so you have to power-cycle the board for the new settings to
>> take (can't just use the redboot 'reset' command) - this may be your
>> issue
>>
>>   - if the bootloader does not detect new eeprom config it prompts you for settings but the 'boot_script_data' var (the boot script) gets taken as input to the prompts (not your issue - just an annoyance - simply break out of the prompts and run 'econfig' again)
>>   - the new flash timings are a bit too strict.  I've seen issues with GW2347's not booting about 20% of the time with the flash timings in the new bootloader (not your issue as your clearly booting)
>>
>> Tim
>>
>> ----- Original Message ----
>> From: José Luis Ferrer <jlferrer at entel.upc.edu>
>> To: Avila at lists.gateworks.com
>> Cc: Avila <avila at lists.unixstudios.net>
>> Sent: Monday, October 8, 2007 3:55:06 AM
>> Subject: [Avila] Always checksum error after flashing new redboot image
>>
>> Hi,
>>
>> After flashing a new redboot (2.04) to a GW-2348-4 board, when booting, 
>> the redboot always prompts a message about error in eeprom checksum, 
>> with the execution of econfig tool in order to write the adequate values 
>> into the eeprom (GPIO0/5-14 and model). However, writing new values does 
>> not solve the problem, because the same error message appears always. 
>> Also, when executing Linux image, the message “EEPROM checksum error, 
>> loading Default values” appears.
>> The same redboot image has been flashed to another 2 identical boards 
>> without errors and the eeprom tool seems to work properly since memory 
>> can be read and written from the redboot console.
>> In addition, flashing the old version from redboot (2.02) works fine and 
>> images from Linux and rootfs are executed and loaded successfully.
>> Any suggestions in what can cause the problem?
>>
>> Regards,
>>
>> José Luis
>>
>>
>> _______________________________________________
>> Avila mailing list
>> Avila at lists.gateworks.com
>> http://lists.gateworks.com/cgi-bin/mailman/listinfo/avila
>>
>>
>>
>>
>> _______________________________________________
>> Avila mailing list
>> Avila at lists.gateworks.com
>> http://lists.gateworks.com/cgi-bin/mailman/listinfo/avila
>>     
>
>
>