[U-Boot] about ## Unknown FLASH on Bank 0

[Wolfgang Denk]

Dear Peter Pan,

please keel the mailinmg list on Cc:

In message <48abf2c20910261812g75d17990jd1793f0560bc882c at mail.gmail.com> you wrote:
> 
> I also think the 1.2.0 is an ancient version, so I migrate my u-boot from
> 1.2.0 to u-boot-2009-08 yestoday, the same "Unknown Flash Bank" problem
> happened.
> I changed a little in the common files, all of which I think should not lead
> to this "Unknown Flash Bank" problem.
> I use MPC8247, and all my changes are:

Which exact board are you using?

> 1. in /common/env_common.c, I add my environment variables to array
> default_environment.

Bad, very bad. You should never meddle with this file. You should add
your custom settings to your board config file only.

> 2. in /cpu/mpc8260/cpu_init.c, in function cpu_init_f, I common this line
> "immr->im_clkrst.car_rsr = RSR_ALLBITS;", because I will need RSR register
> value later
> 3. in /cpu/mpc8260/serial_smc.c, we use BRG1 for SMC1 instead of BRG7

You are not supposed to meddle with these files. No changes to such
common files are necessary to port U-Boot to custom hardware.

> 4. in /include/mpc8260.h, we add a hardware dog kick function, and modified
> functiion "reset_8260_watchdog" a little to kick the hardware dog.
> 5. in /common/main.c, we add support to the two jumper on our board, which
> is just two "if... else...".

Such changes should be done in board specific code, not in common
files.

> 6. in our board specific files, they all works fine before and I did not
> change a thing.
> Make all the changes above, the u-boot works fine. then I modified the
> /common/cmd_mem.c, we make the mtest command to test memory only once(in
> CFG_ALT_MEMTEST mode).
> I change the "for(;;)" to for(;iterations == 1;)", then the "Unknown Flash
> Bank" happens.
> I printed out the 4 Flash IDs, the Manufacture Id changes from 0x01(normal)
> to 0x808(wrong!!), other IDs are all normal.

This makes zero sense to me.

I understand you have a custom board with local modifications. That
means we don't know neither your hardware nor your code, which makes
it impossible to help. From the symptoms you describe, there must be
something fundamentally broken with your port, but without seeing your
code we cannot even guess what this might be.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The high cost of living hasn't affected its popularity.