I'm considering a new version of the TAP-28 board that has a USB PIC18F on it.
My goal is to kept the same form factor as the TAP-28 with the same connector locations and same features (4 LEDs, 2 switches) on the board to the largest extent possible. I'd like any add-on boards that work with the TAP-28 to work with the new board too. An example of this is my AS1106 7-segment LED display board, which is designed to stack with the TAP-28 and connect to the I2C/SPI connector. The PIC18F USB chips loose 3 port pins to D+, D– and the filter cap needed for Vusb, which requires some sacrifice and changes to the original TAP-28 design.
I'm considering the 18F2550 for the micro but I'm wondering if there's any better choice. As I use Swordfish Basic, I want whichever chip I use to work well with Swordfish. I think Jerry's USB module supports most of the USB parts well now. I also want to stick to a 5v part – too many things I'm interfacing to are 5 volt parts and the interfacing to a 3.3v micro gets messy.
Any suggestions for a part other than the 18F2550? Mapping of the peripherals seems to vary between the USB chips so I have to plan accordingly.
Hi, I have no USB experience or for that matter any PIC18 or SF ( what am i doing hitting reply) but yes, do agree about 5v difficulties, My favored current recipe is PIC24FV32KA302 (no USB) Pickit3 with CX16 - MPLABX (currently revisiting old projects on PIC16F asm )Like the look of the TAP28, What about a TAP28 for PIC24 with an FTDI chip....
Re: Preferred PIC18F USB Chip?
5 years 9 months ago #13598
For the 18F and USB, if you want to stick with a 28-pin 5V part then it seems like the 25K50 probably isn't a bad choice. It has less errata (so far), and it's cheaper than the 2550. You get a few more features, but basically they're pretty similar.
If you want anything really different feature-wise then you need to switch over to the 3V 18FJ series.
Like the look of the TAP28, What about a TAP28 for PIC24 with an FTDI chip....
Since Swordfish is the language I use, a PIC24 is off the table for now. I should get busy and dig into Firewing but a quick look left me a bit dazed and confused. Despite all of David's efforts, it doesn't appear to be catching on – most of the posts on the Firewing forum page are from Swordfish users.
I do like a few of the added features on the 'k version, including a DAC output (even if it is only 5 bits) and the FVR (fixed voltage reference) with three voltage options.
It also has a CTMU (charge time measurement unit) to support CapSense (I.e., touch) applications. A CapSense module for Swordfish would be an awesome addition!
Mapping of the peripheral pins on the 'k version seems a little cleaner than on the 18F2550. For instance, on the '2550, the SPI SDO line is shared with the UART RxD line but things are moved around to avoid this on the 'k version. I think I can maintain the function layout of the TAP-28 although the mapping of the switches and LEDs will change a bit.