On 28/11/2010 05:05, Dena Meier wrote:
> 6. I cannot deny that the PIC18LF2450 firmware may have problems.  This
> was demonstration code
> that came with the PICDEM PIC18 EXPLORER DEMONSTRATION BOARD.  I think th=
e
> code is supplied
> "as is" with no warranties.  I do not have source code, just the HEX
> file.  It would be major
> effort to debug with just the HEX file.
>
> 7. I would like a better USB interface.  I am looking for source code --
> maybe drop the serial
> interface paradigm altogether.  Have the USB deliver data in wider than 8
> bit chunks, having
> extra bits for control and signaling.  The 9 bit PIC serial interface is
> actually very good
> as the extra bit can be used for addressing and packet demarcation, I do
> use the second
> USART in the PIC18F8722 this way, highly successfully.  The extra bit
> means packets don't need
> escape symbols and special symbols to guarantee packet demarcation.  A PC
> USB interface with
> 9 bits per "word" (or more) would be great.
>
> I thank everyone for there input.
> Dena Meier
>
>

I'm not sure what you are trying to do overall, but it sounds like=20
scrapping the RS232 and moving to USB might be a good idea, if that is=20
an option. If it is for anything other than personal/learning use I=20
would certainly not be comfortable relying on the (probably flaky and=20
not debuggable) Microchip demo code. Either that or as you say finding a=20
better RS232 solution (maybe something like one of the FT232 or Cypress=20
type ICs..)
Of course you could spend a lot of time chasing down bugs in .NET and=20
the firmware, but it seems like your time could be spent more=20
productively with a change of course.




--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.