Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I'll need to check the PIC datasheet, but it seems to me that their advanced serial ports have built-in support for I2C and SPI in addition to regular UART/USART. I'd forgotten that I2C needs to send address data. That may add unnecessary overhead, since I only need to communicate with one device. Maybe plain old UART will be best after all.
I disagree with this. SPI send and receive can be bit banged in 10 lines of code and is super simple and isn't timing dependent. For chip to chip communication it would always be my go to if I could spare the extra GPIO lines it needs.It usually is, no point using I2C or SPI unless there's some advantage to it - and serial is far easier than either, using hardware or software.
I like I2C because we can use the SAME two pins on the uC chip for several peripherals. That saves pins for other uses.
After Pommie mentioned ready made converter cables, I did a bit more searching, and found that Staples has several listed—some under $5. So, I took a trip to the local store to see if there were any in stock. Unfortunately not. So, I've placed an order with DigiKey for the FTDI breakout board, because I'll have it overnight. I'm too impatient to get it anywhere else.
This USB to serial interface thing seems like it was invented as a stop gap measure to deal with legacy serial devices when USB first arrived on the scene. That's over 15 years ago though, and it appears that these are still nearly as popular as ever. I'm not surprised, because implementing even the simplest USB protocol, the HID device, is an enormous amount of work. If you don't need anything more than what a serial interface can provide, then why complicate things. However, I'm curious whether anyone here has done any projects with the USB module on a PIC.
I'm not surprised, because implementing even the simplest USB protocol, the HID device, is an enormous amount of work. If you don't need anything more than what a serial interface can provide, then why complicate things. However, I'm curious whether anyone here has done any projects with the USB module on a PIC.
Hi,
Sorry it took me so long to get back here.
I have read that with the PIC 16F1455 chip (which has USB pins +D and -D right on it) requires HALF the program memory to hold the USB code (driver). That's nuts if you ask me. Also, Microchip might be charging for the license for that code depending on how it is to be used (personal/commercial).
Maybe they thought the code would be smaller when the designed the 1455 chip. Later they found out i was more complicated than they thought
We dont need to "install' problems along with our solutions.
Geeze, even the cheap chinese chips do better than that.