[U-Boot-Users] Latest git not working for MPC8349EMDS

[Timur Tabi]

Benedict, Michael wrote:
> David Hawkins wrote:
>> Confusing eh!?
> 
> Very!  Thank you for explaining it.
> 
>> Look at the p14, and follow along with that example, see if you
>> can see the right bytes in memory.
> 
> Almost, but not quite.  For one, the flash was locked, and that was why
> the flash erase/copy would not take before.  Secondly, the eleventh byte
> is different, which I think just means I have a different rev than
> yours, 0x43 vs. 0x7f (and I can verify that it is a read-only register):
> 
> => md.b f8000000 20
> f8000000: 2f 0c 40 08 86 af 07 33 ff ff 43 12 ff ff ff 02
> /. at ....3..C.....
> f8000010: 22 07 05 19 24 ff ff ff ff ff ff ff ff ff ff ff
> "...$...........
> 
>> Take the time to read the document I sent. Read the MPC8349 manual
>> with regards to resetting the processor. Eventually it'll make
>> sense. I found it confusing to start with. Hopefully this will
>> help you.
>>
> 
> Big help already, I was able to flash the new u-boot to fe000000, when I
> could not before.  Unfortunately, I am still booting to the old u-boot
> at fff00000(?)  I apologize if I am being dense, but I thought your
> document indicates flashing fe000000 with a u-boot.bin would be all that
> is required to boot from low memory.  See below:

Not quite.  The HRCW at fe000000 must indicate that you want to boot from fe000000 
(actually, fe000100).  To do that, configure U-Boot with "make MPC8349ITX_LOWBOOT_config" 
and flash that u-boot.bin at fe000000.

> => md fe000000
> fe000000: 04040404 04040404 04040404 04040404    ................
> fe000010: 00000000 00000000 00000000 00000000    ................
> fe000020: b0b0b0b0 b0b0b0b0 60606060 60606060    ........````````
> fe000030: a0a0a0a0 a0a0a0a0 00000000 00000000    ................

Your HRCW is 04040000 b060a000, which means lowboot.  You must have something overriding 
your HRCW.  How is J22 jumpered?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale