[U-Boot-Users] DiskOnChip problem on warm boot

Hi all,
Have had my MPC8260ADS based system up and running for a while now but I have recently noticed a problem when I warm boot. When it comes to detecting the DOC chip I just get a series of 10 "Doc_WaitReady timeout" messages. This takes about a couple of minutes and then it carries on with the boot as normal. Any ideas of what is happening? This does not happen in a power on reset.
Regards,
James
This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please return the message immediately to the sender and delete the message from your systems. Thank you.

Hi James,
I don't know about the "power on reset" vs. "warm boot" aspect of your question, but I regularly get this behavior when working with DiskOnChip devices. I get around it by determining (via printk) how many "floors" are detected in my device at startup, then going back into the driver and limiting the number of floors that are being probed to that number.
What takes so long is the probing of nonexistent "floors", at least in my case.
Chuck
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of James Bates Sent: Thursday, October 09, 2003 6:57 AM To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] DiskOnChip problem on warm boot
Hi all,
Have had my MPC8260ADS based system up and running for a while now but I have recently noticed a problem when I warm boot. When it comes to detecting the DOC chip I just get a series of 10 "Doc_WaitReady timeout" messages. This takes about a couple of minutes and then it carries on with the boot as normal. Any ideas of what is happening? This does not happen in a power on reset.
Regards,
James
This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please return the message immediately to the sender and delete the message from your systems. Thank you.
This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

Thanks that was exactly the problem, I changed MAX_FLOORS from 4 to 1 and it worked perfectly.
Regards,
James
-----Original Message----- From: Chuck Meade [mailto:chuckmeade@mindspring.com] Sent: 09 October 2003 15:46 To: jbates@paradise.co.uk; u-boot-users@lists.sourceforge.net Subject: RE: [U-Boot-Users] DiskOnChip problem on warm boot
Hi James,
I don't know about the "power on reset" vs. "warm boot" aspect of your question, but I regularly get this behavior when working with DiskOnChip devices. I get around it by determining (via printk) how many "floors" are detected in my device at startup, then going back into the driver and limiting the number of floors that are being probed to that number.
What takes so long is the probing of nonexistent "floors", at least in my case.
Chuck
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of James Bates Sent: Thursday, October 09, 2003 6:57 AM To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] DiskOnChip problem on warm boot
Hi all,
Have had my MPC8260ADS based system up and running for a while now but I have recently noticed a problem when I warm boot. When it comes to
detecting
the DOC chip I just get a series of 10 "Doc_WaitReady timeout" messages. This takes about a couple of minutes and then it carries on with the boot
as
normal. Any ideas of what is happening? This does not happen in a power on reset.
Regards,
James
This message is intended only for the use of the individual or entity to
which it is addressed, and may contain
information that is privileged, confidential and exempt from disclosure
under applicable law. If the reader of this
message is not the intended recipient, or the employee or agent
responsible for delivering the message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly
prohibited. If you have received this communication in error please
return the message immediately to the sender and
delete the message from your systems. Thank you.
This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please return the message immediately to the sender and delete the message from your systems. Thank you.
participants (2)
-
Chuck Meade
-
James Bates