AnsweredAssumed Answered

Did the SPI bus definition change somewhere between LTIB's uboot and current uboot?

Question asked by Ed Sutter on Oct 14, 2013
Latest reply on Oct 14, 2013 by Ed Sutter

Until today I had been using u-boot as it comes with LTIB (u-boot-2009.08).

 

I'm trying to get a little more up-to-date, so I updated to u-boot-2013.10-rc4 today.

In the older version I was able to do an sf probe on bus 1 and bus 5 (I have a sabersd board

with U14 populated (ECSPI-1) and I also have a second device on ECSPI-5 that we are

using to boot from).

 

Now that I've updated it appears that the bus definitions have shifted down by one because

an array is used to carry ECSPI[1-5] base addresses.  The function spi_setup_slave()

takes an incoming 'bus' value as an argument and used it as an offset into a 5-element table

containing each of the ECSPI[1-5] base addresses.  This means that bus 0 now refers to

ECSPI1, etc...  Is this a known change or am I doing something wrong?

Outcomes