Hi Steve, Boot the board, login, then use this command: cat /dev/mtdblock5. Put the scope at SCK(pin 6) , SI (pin 5) or SO (pin 2) (That EEPROM is U65), you can see the signal. Does this help? Regards, Viet Hoang.
Stephen Berry <[EMAIL PROTECTED]> wrote: Does anyone have any experience in getting the SPI interface running on the 355? It looks to me that the SPI framework as shipped with the 355 doesn't work. To prove this I put a scope on the SPI eeprom on the EVM board - and the part isn't used during boot. I have made an assumption that the onboard eeprom was there for things like MAC addresses and other important numbers... My driver does the same thing on my hardware - no hardware response when I issue spi transactions (the software returns zeros). I do have Joshua Hintze's SPI code - but I would rather have my driver fit into an existing, working framework (if it exists). Does anyone have any patches for the original MVL 2.6.10 SPI code (1.3beta) - or anything else that may help? Thanks, Steve Berry ID2 _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source Send instant messages to your online friends http://uk.messenger.yahoo.com
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
