Same here. It is not I don't want to use the USB based PICs or Microchip software stacks. It is I cannot afford for a loss of business due to PIC silicon errata or SW stack bugs. (When I released a product, I want to make sure I will have a nice sleep in the night.) The only exemption we got, so far, is our BB0703 and BB0703+, they used aged PIC18F2550 in HID. Honestly PK2 is the best design I have ever seen from Microchip. But, that's it, only for BB0703 and BB0703+s. Pains (such as: the original PK2 designer cannot turn on the POR due to reason 123...; cannot turn on BOR due to reason 123...; cannot turn on WDT due to reason 123 ...; canot...; cannot...;) on this family of USB chips kills all my interest to use it for other applications. Everything (important features, such as POR, BOR, WDT) promised on the user manual are denied on the silicon errata or undocumented practices. Special thanks for PK2 designer who figured out how to make a good/ok product with such a hard-to-believe badly designed silicon. But that's just for him/his team. Not everybody get all his lucky. I agree, they are all tiny issues, but put them together, I cannot have a nice sleep at night if I put it in my products. Always try to use FTDI or Silicon Labs single chip solution for USB designs if budget isn't so tight. (By the way, Microchip still doesn't figure out how to make a full-speed USB MCU without crystal, which has been the industry standard for so many years.) Industry temp (-40-85C) version FX2lp almost cost doubled its commercial (0-70C) version. Funny N. Au Group Electronics, http://www.AuElectronics.com http://www.AuElectronics.com/products http://augroups.blogspot.com/ ________________________________ From: Philip Pemberton To: Microcontroller discussion list - Public. Sent: Thu, January 14, 2010 7:51:29 PM Subject: Re: [PIC] MCHPFSUSB USB stack bug Funny NYPD wrote: > Based on what I knew, I will also try to avoid new (<2 years) > Microchip PICs on USB, Ethernet, and CAN as far as I can. I'm planning on migrating this design across to a Cypress EZ-USB chip as soon as it's out of the "initial testing" stage. Basically I'm going to have an FX2lp chip on a bodge-board, then write the code, then do the PCB with the FX2lp. I'm sick of all the gotchas, catches and bugs in the PIC18F4550. The catch being that I lose the option of asking Microchip for a VID/PID Sublicence -- meaning that I then have to pony up the $2k for a USB-IF Vendor ID allocation. Not an attractive prospect, especially when there isn't a chance in hell I'm going to find a use for 65,536 Product IDs. Maybe 10 or 11, but not 2^16... (65,000 0805 0.1uf capacitors on the other hand... those I could probably use up quite quickly... :) ) -- Phil. piclist@philpem.me.uk http://www.philpem.me.uk/ -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist