... which is in fact what IT eventually used, but thanks
Interestingly, the first time they ran it with a full check after the copy, it failed with some obscure errors due to corporate networking rules. Hamsters ran for 16 hours and then failed. The next weekend they tried again - good move, fully verified.
<italic>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.
Based on sorting out other busses e.g. I2C, CAN I'd recommend:
Build in, or use, some logging facility to record what's happening on each chip, even if its only a count or letter stored to show where you're code is going.
Use a USB to SPI converter or something you know works to prove each work individually - it's much easier when one end is a 'known' rather than with and 'unknown' at each end of the wire.
Read the manuals on the chips and on the SPI bus - I know it's obvious, but chip manuals tend to focus on how the chip works - not on the bus. Get the manual on the bus protocol.
Have someone else look at it and show them, OK perhaps you wouldn't be posting here if you could do that but it really helps. I saw someone debug for days without turning power on to a stepper motor he was trying to step.
Try and scope the interaction signals, and work through them, after all there should show exactly what's happening: which chip is not responding or signalling as expected.
Don't handle just the happy path, handle the error cases as well - e.g. set timeouts and set sone code to log if the time out occurs even if its just to log what the error was.
I took out my 5 years old laptop to re-install and give it to my daughter.
As she's working with Windows in the school I intend to install Windows 7 (Professional).
As the laptop has 4 GB memory I'm not sure what would be better, install 32 bit and loose some memory range or install 64 bit and loose - maybe - some performance?
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
You didn't said about the processor. still based on your question,
Win 7 (Any version except Basic) x32 bit can not use more then 3.25 GB of RAM (even if you have 16 GB RAM)
while Win7 x64 bit can use any amount of RAM, So as you have 4GB and if you want to use full of it you have to load Windows 7 x64bit - or any O/S x64bit it may Vista/Win8 Anything.
Performance : x64bit will support almost every application that developed for a x32bit machine. And there will be no performance issue. I m using x64bit in my Home PC (that have 8GB) and in my Laptop (4GB)
Only drivers will not support x64bit if they made for x32bit.
Here is a link where you can get all Laptop and other components drivers in one page.
Hi, I'm trying to interface a gap sensor with pic micro-controller but I'm not winning. I wanna design a barcode reader. Can anyone help me with the circuit that I can use to interface the gap sensor with a PIC16F series please.
I've always wondered if it was possible to take an old 6502 or 65816 microprocessor, which run in the 1-3 MHz range, and get it to run in the GHz range. I know I can run an emulator of an Apple II machine at high speed, but has anyone ever done it with the real hardware?
Something about a blazing fast computer with a simplified instruction set (only 256 opcodes!) that really appeals to me!