Hello guys,

This is a derivative of my previous post for adapting mpc8xxx_spi to work with mpc8360e spi in cpu-mode.

I'm seeing something funny with using the 'sf probe' command, but not the sspi command.

Using 'sspi' command, I got a good response:

=> sspi 0 32 9f spi_xfer: tx 9f000000 [32 of 32] bits spi_xfer: ... 9f000000 written [0] iR 0 ev 3 <-- [tm] isRead spi->event [0] spi_xfer: rx 1fffa270 = ff202013 spi_xfer: transfer ended. Value=ff202013 *** spi_xfer: exit FF202013 =>

When using 'sf probe', only the first tx data got transmitted (verified with scope):

sf probe 0:0 spi_xfer: tx 9fffd600 [8 of 8] bits spi_xfer: ... 9fffd600 written [0] iR 0 ev 3 <-- [tm] isRead spi->event [0] spi_xfer: rx 00000000 = ffff0001 spi_xfer: transfer ended. Value=ffff0001 *** spi_xfer: exit spi_xfer: tx 000102ff [32 of 40] bits spi_xfer: ... 000102ff written <-- Never got sent out! [0] iR 0 ev 1 <-- [tm] isRead spi->event [1] iR 0 ev 1 <-- [tm] isRead spi->event [2] iR 0 ev 1 <-- [tm] isRead spi->event ... [1000] iR 0 ev 1 *** spi_xfer: Time out during SPI transfer spi_xfer: transfer ended. Value=00000000 spi_xfer: tx 03ffffff [8 of 8] bits spi_xfer: ... 03ffffff written <-- Never got sent out! [0] spi_xfer: rx 1f5b4da8 = 13000000 spi_xfer: transfer ended. Value=13000000 *** spi_xfer: exit SF: Got idcode 13 00 00 00 00 Failed to initialize SPI flash at 0:0 =>

On the oscilloscope, even though "spi_xfer: ... 000102ff written" is shown, I only see the first byte (9f) being sent and the clock stops there, explaining the debug printout during getting rx data that shows the rx buffer never got any data

I have tried replacing the spi->tx = tmpdout statement (and all register access) with out_be##(&spi->tx, tmpdout) in case the compiler is optimizing things out, but this makes no difference.

but if this is true, won't the MPC8349EMDS see this problem also?

What am I missing here?

Modified driver is attached.

Thanks for all the help!

- Richard