[U-Boot] Need Help on *** Warning - bad CRC, using default environment
Hi,
I have got this contact from web when I actually searching for some solutions to get rid off the issue on "Warning - bad CRC, using default environment". And I have gone through the some of the mail thread.
Am also facing the same issue that when I hard reset the board, U-boot starts and stops at line as below *** Warning - bad CRC, using default environment. From your mail thread conversation, its almost clear that this is due to uninitialization env variables / non-matching CRC, hence it needs to be "saveenv". But now the actual problem here is am not getting the U-boot prompt (#) to enter uboot commands. As soon as the board hard rebooted it comes and hangs at the same line, so not able to enter any commands there. If anyone can suggest anything that helps to bring up, will be really great. Thanks in advance.
Uboot-logs: =========== Flash: 16 MB NAND: No NAND device found!!! 0 MiB *** Warning - bad CRC, using default environment "Hangs".
Regards, Balaji.
Hi Bala,
On 04/08/2011 13:14, Bala Ss wrote:
Hi,
I have got this contact from web when I actually searching for some solutions to get rid off the issue on "Warning - bad CRC, using default environment". And I have gone through the some of the mail thread.
Am also facing the same issue that when I hard reset the board, U-boot starts and stops at line as below *** Warning - bad CRC, using default environment. From your mail thread conversation, its almost clear that this is due to uninitialization env variables / non-matching CRC, hence it needs to be "saveenv". But now the actual problem here is am not getting the U-boot prompt (#) to enter uboot commands. As soon as the board hard rebooted it comes and hangs at the same line, so not able to enter any commands there. If anyone can suggest anything that helps to bring up, will be really great. Thanks in advance.
Uboot-logs:
Flash: 16 MB NAND: No NAND device found!!! 0 MiB *** Warning - bad CRC, using default environment "Hangs".
It might help if you specified which version of U-Boot you run and for which board it is built.
Note that if you're not using the mainline U-Boot but a custom vendor one, you should inquire with the vendor.
Note also that if you're using the mainline U-Boot, then you should make sure you're using the latest version.
Regards, Balaji.
Amicalement,
Hello Albert Aribaud,
Thanks for your reply.
The board contains LSI ARM processor and the U-boot is customised for the same.
Regards, Balaji.
On Thu, Aug 4, 2011 at 4:49 PM, Albert ARIBAUD albert.u.boot@aribaud.netwrote:
Hi Bala,
On 04/08/2011 13:14, Bala Ss wrote:
Hi,
I have got this contact from web when I actually searching for some solutions to get rid off the issue on "Warning - bad CRC, using default environment". And I have gone through the some of the mail thread.
Am also facing the same issue that when I hard reset the board, U-boot starts and stops at line as below *** Warning - bad CRC, using default environment. From your mail thread conversation, its almost clear that this is due to uninitialization env variables / non-matching CRC, hence it needs to be "saveenv". But now the actual problem here is am not getting the U-boot prompt (#) to enter uboot commands. As soon as the board hard rebooted it comes and hangs at the same line, so not able to enter any commands there. If anyone can suggest anything that helps to bring up, will be really great. Thanks in advance.
Uboot-logs:
Flash: 16 MB NAND: No NAND device found!!! 0 MiB *** Warning - bad CRC, using default environment "Hangs".
It might help if you specified which version of U-Boot you run and for which board it is built.
Note that if you're not using the mainline U-Boot but a custom vendor one, you should inquire with the vendor.
Note also that if you're using the mainline U-Boot, then you should make sure you're using the latest version.
Regards,
Balaji.
Amicalement,
Albert.
Hello Bala,
Bala Ss wrote:
Hi,
I have got this contact from web when I actually searching for some solutions to get rid off the issue on "Warning - bad CRC, using default environment". And I have gone through the some of the mail thread.
Am also facing the same issue that when I hard reset the board, U-boot starts and stops at line as below *** Warning - bad CRC, using default environment. From your mail thread conversation, its almost clear that this is due to uninitialization env variables / non-matching CRC, hence it needs to be "saveenv". But now the actual problem here is am not getting the U-boot prompt (#) to enter uboot commands. As soon as the board hard rebooted it comes and hangs at the same line, so not able to enter any commands there. If anyone can suggest anything that helps to bring up, will be really great. Thanks in advance.
Uboot-logs:
Flash: 16 MB NAND: No NAND device found!!!
I think that your Environment is in NAND, and as there is no NAND, u-boot couldn;t find an environemnt ...
Please send the u-bot version and on which board you use, so we maybe can help you!
bye, Heiko
Dear Bala Ss,
In message CADzqVQ3J_0dfH6nHFtPc_ER_b8qBbca_deokYxS5vbRSE6OKJQ@mail.gmail.com you wrote:
I have got this contact from web when I actually searching for some solutions to get rid off the issue on "Warning - bad CRC, using default environment". And I have gone through the some of the mail thread.
Hm... Did you try google?
If you search for "Warning - bad CRC, using default environment" google will show the relevant entry in our FAQ as the very first hit.
It's really quite difficult to miss that, and I kind of admire how you manage to do that.
Am also facing the same issue that when I hard reset the board, U-boot starts and stops at line as below *** Warning - bad CRC, using default environment. From your mail thread conversation, its almost clear that this is due to uninitialization env variables / non-matching CRC, hence it needs to be "saveenv". But now the actual problem here is am not getting the U-boot prompt (#) to enter uboot commands. As soon as the board hard rebooted it comes and hangs at the same line, so not able to enter any commands there.
As Albert already wrote: without any information about CPU type, board name, origin and version of the U-Boot code you are using it is impossible to answer this question.
Best regards,
Wolfgang Denk
participants (4)
-
Albert ARIBAUD -
Bala Ss -
Heiko Schocher -
Wolfgang Denk