[Avila] Always checksum error after flashing new redboot image

[Chris Lang]

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