As you can see from my commit, I added a slip usb serial example. There was also an error in slip.jal if your sent packet is the same as slip_mtu. We where missing byte 10 but didn't notice. I didn't notice it in my networking since slip_mtu was always larger then sent packets.
download these: http://jallib.googlecode.com/svn/trunk/sample/18f67j50_slip_poll_usb_serial.jal http://jallib.googlecode.com/svn/trunk/include/protocol/slip.jal I tested it on windows. Once you plug in usb and open the port via your PC, the PIC will send you 1,2,3,0xC0,5,6,0xDB,8,9,0x0A via slip. Slip will encode it and you will receive it on your PC encrypted like this: C0 01 02 03 DB DC 05 06 DB DD 08 09 0A C0 Then when you send back C0 01 02 03 DB DC 05 06 DB DD 08 09 0A C0 from your PC to your PIC. The PIC will decode the data and send back to the PC on the serial port (not via slip procedures). You will get 01 02 03 C0 05 06 DB 08 09 0A Your serial_data_available works, please add it to usb_serial. Thanks, I was waiting for this. I have this procedure in my sample, buildbot will fail unless it is removed. you can remove it or let me know. Maybe you can add a SLIP 18f4550_slip_poll_usb_serial.jal sample, or whatever PIC you are using. -- this can be removed when added to usb_serial function usb_serial_data_available'get() return bit is if ( usb_cdc_line_status() == 0x00 ) then return false end if if ( !usb_cdc_rx_avail() ) then return false end if return true end function Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
