Hi,

I've been having a few problems with implementing USB on a 18F2550 and, judging by the zero replies to my previous posts, it seems that I'm not alone.

Could this be down to the sparse documentation in the pbp manual?

I've finally cracked the problem, and have data going to and from my development board and my PC, but this has been a laborious and time-consuming exercise.

BTW, if anybody is interested, I'm more than happy to share the results of my labours.

Don't get me wrong. I'm more than prepared to R.T.F.M. and have not only bought Jan Axelson's 'bible' but have spent many hours scouring the 'net before resorting to the forums.

Call me lazy, but I don't think it should be necessary for me to become an expert in the field of USB communications when it is such a small part of my overall project.

Overall, I feel that the pbp manual could be improved in this respect. Sure, they have provided the commands, and that has indeed removed the slog of assembler coding from us, but a more detailed explanation of what is going on 'behind the scenes' so to speak, would not go amiss.

Another example would be that way that the relevant underlying resource usage is not explained. Again, I understand the monumental task of providing us with a [it must be said, superb] basic compiler that has to take into account the vast number of different uControllers out there.

But, when my code inexplicably breaks, for example, when I'm using a timer under my own assembler interrupts, and my LCD routines go south, I have to assume that the 'serout2' command is competing with me for the same resource?

I may be wrong - I'm perfectly capable of accepting that it's MY coding skills [or lack of] that are the problem but again, better documentation would save us all hours of frustrating debugging, no?

Just a few thoughts. Whinge over. Any comments?

Giulio