Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Thanks for the feedback. I've since spent a few hours reading the datasheet and going over the library. The datasheet states that it does support keeping the cs low for more than one byte if the phase bit is 1. Hardware SPI can send 8 words from a loaded fifo buffer and can presumably keep sending them continuously if you can keep loading the buffer. The energia library on the otherhand is hardcoded to send 8 bits only and read 8 bits only and that's it. Setting the phase bit has no effect on the disfunction of the spi library. Tough luck if you want to access a all 4 channels in one
  2. I have determined the exact problem. The fact that the library is taking control of the CS pin is what caused the problem. After the first 8 bits were sent the energia library was toggling the CS pin and resetting the communication stream before sending the next 8 bits. Looking at the SPI library code again and noting the observed behaviour I can see that the library is utterly useless in that it restricts people to a single 8bit command. Even reads would not be possible as you need to send your command then keep clocking for the response. In fact I just realised it has no read cap
  3. Hi, I'm trying to use an old stellaris launchpad board as a datalogger to an SD card for logging data from an accelerometer. I've already built such a project on the arduino hardware but best I can do is one reading per 2ms and I want to get it logging faster... at least 1 reading every 500us. So I thought I would port it onto the the launchpad boards I had kicking around. Straight up the SD card didn't work trying to use SPI(3) as the underlying SPI bus and I have downloaded and tried about 6 different sd card libraries but got nowhere. What I then did was go back to first princip
  4. That's eventually how I got it set up. I have a linux nas server that I ended up installing it on for remote development. I need to finish setting up an IDE for remote development from Windows but at least now I have it compiling.
  5. Hi Guys, Just saying hello. I've have been playing with the atmel chips for a while and am now looking to start playing with other micros. I have now got myself some stellaris launchpads, an EXP430G2 and an EZ430-Chronos watch that i'm looking to code for. I've been bouncing around the interwebs trying to figure out how to get past the compiler crippleware for the Chronos watch but no luck so far so I think I've been dudded there :-( but at least I should have no issues with the launchpads.
  6. How are you working around the code size restrictions for the Chronos with CCS? I bought one in the recent deals and am totally frustrated that I can't compile the full firmware although I am using the IAR Workbench. I havent tried CCS yet because I understand that the crippleware problem is the same. I'm now looking at Energia and mspgcc for the chronos. I also have Stellaris Launcpads and an EXP430G2 launchpad and want one dev environment for all 3.
  • Create New...