 |
 |
View previous topic :: View next topic |
Author |
Message |
Ttelmah
Joined: 11 Mar 2010 Posts: 19831
|
|
Posted: Thu Nov 28, 2013 8:24 am |
|
|
This is a distinction between 'CS' (chip select), which would normally be expected to stay low for an entire data transaction, and is used to say what device is to be talked to, and 'SS' (slave select), which drops on a 'per byte' basis, to synchronise the SPI bytes.
It's behaving like the chip is using the line as SS, yet the data sheet shows it used as CS.....
The existing CCS driver, can drive 'SS' directly for you. Just add:
ENABLE=PIN_D4
To your SPI setup, and get rid of all references to the pin in the code.
Best Wishes |
|
 |
MotronixGS
Joined: 13 Jul 2011 Posts: 19
|
|
Posted: Thu Nov 28, 2013 8:29 am |
|
|
Sure!! We say the same...
jeremiah wrote: | MotronixGS wrote: | page 38 datasheet shows a timings diagram, CS is low while the transmission is active. |
This is typical for SPI. CS is low for the entire transaction for most devices out there. |
|
|
 |
MotronixGS
Joined: 13 Jul 2011 Posts: 19
|
|
Posted: Thu Nov 28, 2013 8:30 am |
|
|
Thank you so much for your clarification!!
Ttelmah wrote: | This is a distinction between 'CS' (chip select), which would normally be expected to stay low for an entire data transaction, and is used to say what device is to be talked to, and 'SS' (slave select), which drops on a 'per byte' basis, to synchronise the SPI bytes.
It's behaving like the chip is using the line as SS, yet the data sheet shows it used as CS.....
The existing CCS driver, can drive 'SS' directly for you. Just add:
ENABLE=PIN_D4
To your SPI setup, and get rid of all references to the pin in the code.
Best Wishes |
|
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|