02-17-2010 06:22 PM
This is what I have created so far.
1st Frame to configure it, I have included the specs on the SPI Comm details below, directly from the User's guide on the device.
2nd Frame: Drop the pin to low to initiate SPI Communication. (I found this from another answer on the forum)
3rd Frame: Simultaneously Read/ and Write an "H" in hex ascii = 48 to the device
4th Frame: Wait, at least 50 microseconds,
5th Frame: Read two bytes response
6th Frame: Raise CS pin to end communication
7th Frame: Finish and terminate
My problem lies in the communication aspects, I cannot make the two things talk to each other. I am in some serious need of help and am facing some deadlines, any help will be greatly appreciated. As far as data conversion to usable numbers I can manage but I just need it to talk. Please Help
Solved! Go to Solution.
02-19-2010 01:35 PM
02-19-2010 01:44 PM
Tilgath,
So are you getting any errors during build or run time? What board are you communicating from? Do you see anything being transmitted out (your h value)?
02-19-2010 01:50 PM
The Device has yet to successfully run. With the new changes I just made I included a counter for the interations so I could see if it was making it through any of them. But its not doing anything. I dont get an error, but the processor status says it "Stopped at 0x00000039A" Still no luck
Thanks
02-19-2010 01:52 PM
02-19-2010 02:30 PM
The problem is in hardware:
- the microcontroller is configured as a SPI master which means it is driving SCK, SS and MOSI.
- but the Honeywell thing is driving SCK as well!!!
Do you need the OLED display in your application?
02-19-2010 03:02 PM
Funny you should mention the OLED I have been talking to a couple of the application engineers during this feed and I have decided to give up on the SPI, which I thought would be easier, and am going to use UART instead. Mostly because the OLED and the MicroSD card problem. So im going back to square one, thanks to the both of you. I call it solved!
-Joel