Reply by ssonderhoff January 25, 20112011-01-25
This particular issue has been resolved
--- In l..., "ssonderhoff" wrote:
>
> Hi,
> I am attempting to hook up a SPI battery backed up clock DS3234 to the SSPm port on a Logomatic V2 from sparkfun. I have yet to show any sort of communication, however that is getting ahead of myself. I initialize the port as shown on one of the NXP application notes and try to send data to the RTC. The logomatic uses SPI0 for an SD/MMC card which promptly loses it's ability to access the card - this is entirely dependant on running the SPI1 initialization routine. I save the (pre-SPI1 initialization) port configuration (IODIR0) and return it back to the original state as well as disable SPI1 but the problem remains.
>
> My general question is - does anyone have an idea what is changed by the SSP initialization that could cause the issue with SPI0?
>
> Thanks,
> Stefan
>

An Engineer's Guide to the LPC2100 Series

Reply by ssonderhoff January 24, 20112011-01-24
Hi,
I am attempting to hook up a SPI battery backed up clock DS3234 to the SSPm port on a Logomatic V2 from sparkfun. I have yet to show any sort of communication, however that is getting ahead of myself. I initialize the port as shown on one of the NXP application notes and try to send data to the RTC. The logomatic uses SPI0 for an SD/MMC card which promptly loses it's ability to access the card - this is entirely dependant on running the SPI1 initialization routine. I save the (pre-SPI1 initialization) port configuration (IODIR0) and return it back to the original state as well as disable SPI1 but the problem remains.

My general question is - does anyone have an idea what is changed by the SSP initialization that could cause the issue with SPI0?

Thanks,
Stefan