Nasty U-Boot problem SOLVED

Hi
i have a nasty problem with my Sam's U-Boot.
Have tried to verify how boot priorities were set; they seemed OK CDRom first, SATA dr(ive second, so i left hyavibg saved that (should probably not have, but i did not see how to leave), then since i wwas still in UBoot used the ESC switch.
Now i don't have a boot anymore:
- if no bootCDROm present the initial U Boot sequence goes on (passing through the phase were you have the opportunity to press any key to stop autoboot, but autoboot does not respond to key being hit)
- i did make an autobooting copy of my sys drawer, but it did not work, that's why i wanted to verify the boot priorities
- using it U Boot scans the CD tells me "No ELF image at address 0x0c89.. bad ELF image loader" then tells me the same story as when i have no bootCD, invites me to press a key to continue, but keuboard does not wor

I made the bootCDROM with AmiDVD
Any idea how to go on with this?
I have used my OS4.1 install CD, and can get to my OS4.1 partitions, but his takes ages.

@JosDuchIt

Do at Uboot prompt:

sete menuboot_cmd boota
sete boot1 s4siicdrom
sete boot2 s4sii
save
boota

It should boot now from a CD if one is in the drive, or on HD.

@Elwoodle

Hi using my OS4.1 install CD i was able using the enter key
(here it worked) to enter the UBoot program
and reset the booting priorities ok


Thanks for your help

Joseph

@JosDuchIt

Have tried to verify how boot priorities were set;
You're waisting your time. There's a wrong mask value in UBoot that reads the CDROM wrong. The work-around is make CDROM the first boot device.
That's why you're having boot problems.

Edit: I seemed to missed this thread earlier!

@Snuffy


What went wrong was that when looking for the boot prioities in U-boot i found everything Ok, but still managed to save and exit having the CDROM set as boot priority 1 and 2.
After that, my keyboard did not respond any more. (big panic)
Luckily i found that when i used the (old) OS4.1 install disk, my keyboard responded, i interrupted the boot with the keyboard and was able to have access to U-boot again. I then did set the priority 2 to HD?

Everything OK from then

Thanks for your reaction