Easy HID Command -Response application

[f_lez]

Where should this go?

I cut'n'pasted from the above code section, into microcodestudio, then added this to the top, before the define

' **************************** Added from other demo
buffer	Var	Byte[16]
cnt	Var	Byte
LED	Var	PORTB.0
Define  OSC 48
'****************************************************

high led

Then at the bottom after overusbservice I added the usb in/out and a led flash to show its alive

idleloop:

    low led
    pause 500
    high led
    pause 500

	cnt = 16	' Specify input buffer size
	USBIn 3, buffer, cnt, idleloop

' Message received

	buffer[0] = "H"
	buffer[1] = "e"
	buffer[2] = "l"
	buffer[3] = "l"
	buffer[4] = "o"
	buffer[5] = " "
	buffer[6] = "W"
	buffer[7] = "o"
	buffer[8] = "r"
	buffer[9] = "l"
	buffer[10] = "d"
	buffer[11] = 13
	buffer[12] = 10
	buffer[13] = 0

outloop:
	
    USBOut 3, buffer, 14, outloop

	Goto idleloop	' Wait for next buffer

usbinit and usbservice was removed from the code of the other demo like it says to.

It looks to me like a worker, but i get compile errors, lots of them

This one

IDLEIF             VAR UIR.4         ; USB Idle Interrupt Flag
<

gives me a bad datatype (first of a few)

and this one

    UIE = $7F                    ; enable USB interrupts

throws up a syntax error with some more below it


I tried it as

INCLUDE "USB_ASM_Service"

At the top of my little test and MCS opened it as a 2nd page, and threw up the same errors.

Just for completeness thats here

include "USB_ASM_Service.pbp"

' **************************** Added from other demo
buffer	Var	Byte[16]
cnt	Var	Byte
LED	Var	PORTB.0
Define  OSC 48
' ****************************************************

high led

idleloop:

    low led
    pause 500
    high led
    pause 500

	cnt = 16	' Specify input buffer size
	USBIn 3, buffer, cnt, idleloop

' Message received

	buffer[0] = "H"
	buffer[1] = "e"
	buffer[2] = "l"
	buffer[3] = "l"
	buffer[4] = "o"
	buffer[5] = " "
	buffer[6] = "W"
	buffer[7] = "o"
	buffer[8] = "r"
	buffer[9] = "l"
	buffer[10] = "d"
	buffer[11] = 13
	buffer[12] = 10
	buffer[13] = 0

outloop:
	
    USBOut 3, buffer, 14, outloop

	Goto idleloop	' Wait for next buffer

[Darrel Taylor]

Looks like you've been busy while I was sleeping.

PBP 2.46 was missing a few registers in the PIC18EXT.bas file.
You can either add these lines to that file, or place them at the top of your program (before the INCLUDE file).

UIR  VAR BYTE EXT
UIE  VAR BYTE EXT
UEIE VAR BYTE EXT
UEIR VAR BYTE EXT

For the _config depricated warning you can add w = -230 to the 18F2550.inc file ...

        LIST p = 18F2550, r = dec, w = -311, w = -230, f = inhx32

hth,

[f_lez]

thanks that was just the little gem of info i was missing!

And it works!

[f_lez]

Simple code in a loop...

' Main Program Loop
Loop:
 
    USBOut 3, Buffer, Cnt, loopy
loopy:
    porta=170 ' fancy led pattern0
    pause 500
    porta=85  ' fancy led pattern1
    pause 500

    goto loop
end

After about 30 minutes, stops running......

Pic is stable etc had it running 24hrs+ on a simple led flasher. (on same dev board)

any guesses?

[Darrel Taylor]

Well, it's a Total guess but ...

Try adding a USBIN statement to the loop.
If anything comes in, and the SIE doesn't get released, everything locks up (including the PC application).

The reason I say it's a guess is because it requires recieved data.
If you are using HyperTerminal then you would need to type something to have it happen.

[f_lez]

Well, it's a Total guess but ...

I dopnt know whats going on TBH, I watched it fail after about 30 mins, twice, I saw it fail after ten, I gave up hitting my head and posted the above, and then left it running, 2hrs later it was still running, I went to bed, got up this morning, still running, I went out for a few hours, come back, still running....

I can only guess something upset the pic at an hardware level because i have changed nothing at the software level. (I have even glued the crystal to the crystal socket!)

Anyhow.... these nuggets..

Plugged indicates when the device is fully connected to the PC.
RX_READY indicates when a report has been received.
TX_READY indicates when it's OK to Send. The device is Plugged and the SIE is ready to accept data.

Do you an an example line for those?

Once upon a time getting data into the pic was fairly easy, now I have to keep the pic doing some monitoring of its io pins but at same time accepting commands from the fake comport, so seeing if any data was waiting, as it seems to have very little in the way of flow control would be useful. (what happened to the wonderful buffers and fifo's on real hardware!)

[Darrel Taylor]

Gremlins, or maybe the cats (if you have any).

Make sure you have plenty of capicitance on the VUSB pin. (.22uF to .47uF)
And have both a 10uF and 0.1uF capacitors on the Power Rails (VSS-VDD).

Plugged, RX_READY and TX_READY are just normal "Bits".

RX_READY indicates that data has been received. It should be cleared after use.

Main:
    IF RX_READY THEN        ; USB data has been rcvd
        RX_READY = 0        ; clear the Ready flag
        USBIN 1, Buffer, Cnt, Main
        LCDOUT $FE,1,STR Buffer
    ENDIF

TX_READY indicates that the device is plugged in and the SIE is ready to accept data to send.

    IF TX_READY THEN         ; USB is Ready to transmit
        TX_READY = 0         ; clear the Ready flag
        ADCIN 0, ADval
        ARRAYWRITE Buffer,[DEC4 ADval," "]
        USBOUT 1, Buffer, Cnt, TXfail
      TXfail:
    ENDIF
GOTO Main