[U-Boot-Users] I2C POST test known problems?
Greetings
Is anyone aware of any problems with the I2C POST test - I've enabled it and it looks like it locks up the CPM with the busy flag in the command register remaining set all the time.
Does anyone know if this is (well) tested code or should I just ignore it and write my own...
Robin Gilks wrote:
Greetings
Is anyone aware of any problems with the I2C POST test - I've enabled it and it looks like it locks up the CPM with the busy flag in the command register remaining set all the time.
Does anyone know if this is (well) tested code or should I just ignore it and write my own...
Give me a chance and I'll remember that nobody else knows what I'm working on!!
System is mpc8xx based, very close to the Motorola FADS hardware (its the updated version!!).
Cheers
Robin, i am also working on this eval board (and our own in house variant) with a 866/859T
I had a patch for wolfgang but it got big and messy so I haven't submitted it yet.
On Thu, Jul 17, 2003 at 10:27:26AM +1200, Robin Gilks wrote:
Robin Gilks wrote:
Greetings
Is anyone aware of any problems with the I2C POST test - I've enabled it and it looks like it locks up the CPM with the busy flag in the command register remaining set all the time.
Does anyone know if this is (well) tested code or should I just ignore it and write my own...
Give me a chance and I'll remember that nobody else knows what I'm working on!!
System is mpc8xx based, very close to the Motorola FADS hardware (its the updated version!!).
Cheers
-- Robin Gilks Senior Design Engineer Phone: (+64)(3) 357 1569 Tait Electronics Fax : (+64)(3) 359 4632 PO Box 1645 Christchurch Email : robin.gilks@tait.co.nz New Zealand
This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
In message 20030716223857.GA13575@zumanetworks.com you wrote:
I had a patch for wolfgang but it got big and messy so I haven't submitted it yet.
I think chances that it will become _smaller_ over time are infinitesimal ...
Best regards,
Wolfgang Denk
In message 3F15D14E.3020006@tait.co.nz you wrote:
System is mpc8xx based, very close to the Motorola FADS hardware (its the updated version!!).
Are you sure I2C is working at all on your board?
Best regards,
Wolfgang Denk
Wolfgang Denk wrote:
In message 3F15D14E.3020006@tait.co.nz you wrote:
System is mpc8xx based, very close to the Motorola FADS hardware (its the updated version!!).
Are you sure I2C is working at all on your board?
I'm not at all sure - in fact I don't think there are any I2C devices on the board but it should still scan the address range and say pass/fail according to its findings without locking up. Very odd that i2c_init gets called twice without a problem (once from Flash very early on) and once later before the POST tests run without a problem but then on the 3rd go (when called from i2c_probe) it hangs up!!
Think I'd better check its being put into Master mode otherwise it won't do anything until it sees a clock presumably...
In message 3F15DCC8.6050106@tait.co.nz you wrote:
I'm not at all sure - in fact I don't think there are any I2C devices on the board but it should still scan the address range and say pass/fail according to its findings without locking up. Very odd that i2c_init
Try running the iprobe command in interactive mode and you'll see why the test takes so long to complete. You may then consider switching to use soft-i2c instead.
Best regards,
Wolfgang Denk
In message 3F15CE75.7070906@tait.co.nz you wrote:
Is anyone aware of any problems with the I2C POST test - I've enabled it and it looks like it locks up the CPM with the busy flag in the command register remaining set all the time.
Works fine here, both with the hardware and the software version of the I2C driver:
... => log show <4>POST memory PASSED <4>POST spr PASSED <4>POST cache PASSED <4>POST watchdog <4>PASSED <4>POST i2c PASSED <4>POST cpu PASSED <4>POST ethernet PASSED <4>POST spi PASSED <4>POST usb PASSED <4>POST sysmon PASSED => diag run i2c => log show <4>POST memory PASSED <4>POST spr PASSED <4>POST cache PASSED <4>POST watchdog <4>PASSED <4>POST i2c PASSED <4>POST cpu PASSED <4>POST ethernet PASSED <4>POST spi PASSED <4>POST usb PASSED <4>POST sysmon PASSED <4>POST i2c PASSED =>
Does anyone know if this is (well) tested code or should I just ignore it and write my own...
Please do not ignore it, and do not write your own. If there are problems I'd rather see them fixed.
Best regards,
Wolfgang Denk
participants (3)
-
Nye Liu -
Robin Gilks -
Wolfgang Denk