I'm trying to head off an IT inflicted disaster. IT wants to move the s/w team I am on to a new machine. They desperately need to do this, and I'm not arguing. However, the LAST time they moved a lot of our files (backup development zip files for example), the transfer (xcopy) corrupted them. It wasn't until a year later when I needed the old code the problem was discovered.
So, alternatives to xcopy? I'm sure there must be something better out there that will do a binary check for a good copy...
Anything else I should fear?
Charlie Gilley You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Yes, anyone can learn how to create a printer driver.
If you want to know how, it would take an entire book to describe. That's not something you're going to learn from a couple of forum posts. You've been told where to start, and, yes, there are books out there that will teach you how to create drivers.
I am currently using a dsPIC33FJ128MC802 [^] on a DM300027[^] (starter) board to read data from the ADAS1000[^] evaluation board (for ECG) via the J4 SPI pins. I have the SPI pins (SCLK, MOSI, MISO and CS) of both boards connected correctly according to the ADAS1k documentation.
I am having trouble getting the two (ADAS1k and dsPIC) to talk to each other. I set up the uProc's SPI and then tried to configure the ADAS1k by sending based on an example in the ADAS1000 documentation.
These commands should configure the ADAS1k to send out a 150Hz Test Tone Sine Wave on each channel.
The MOSI is enveloped by a CS, and it is sent as 4 bytes, for example 0x8500000B is sent as 0x85 followed by 0x00, 0x00, 0x0B.
To read data on the MISO, the SPI sends out four 0x00 bytes to generate clock signals for the MISO.
Writing 0x55555555 followed by 0xAAAAAAAA shows a signal on the MISO, which looks like a 0x0050. I haven't been able to get signals on MISO in other cases. I tried writing to a register and reading it back after a few ms delay, but nothing showed up on the MISO.
I've captured the scope of the SPI (MOSI, SCLK and CS) signals on both boards and they seem to be fine. The MOSI signal seems as expected. I'm still unable to see anything on MISO though.
Any suggestions on what else I can do to troubleshoot this issue? Thank you.
Last Visit: 31-Dec-99 18:00 Last Update: 8-Mar-14 14:36