Author: [email protected]
Date: Tue Apr 28 13:52:38 2009
New Revision: 950

Modified:
    trunk/include/peripheral/usb/usb_serial.jal
    trunk/sample/18f2450_usb_serial.jal
    trunk/sample/18f4550_usb_serial.jal
    trunk/test/peripheral/usb/test_usb_serial.jal

Log:
updated USB driver reference

Modified: trunk/include/peripheral/usb/usb_serial.jal
==============================================================================
--- trunk/include/peripheral/usb/usb_serial.jal (original)
+++ trunk/include/peripheral/usb/usb_serial.jal Tue Apr 28 13:52:38 2009
@@ -426,13 +426,16 @@
  -- of the entire USB_STRING2 array, the second byte shall be set to
  -- USB_DT_STRING (=0x03).
  -- -----------------------------------------------------------------------
-const byte USB_STRING2[24] =
+const byte USB_STRING2[30] =
  {
-       24,     -- bLength
+       30,     -- bLength
        USB_DT_STRING,  -- bDescriptorType
        "J", 0x00,
        "A", 0x00,
        "L", 0x00,
+       "L", 0x00,
+       "I", 0x00,
+       "B", 0x00,
        " ", 0x00,
        "S", 0x00,
        "e", 0x00,

Modified: trunk/sample/18f2450_usb_serial.jal
==============================================================================
--- trunk/sample/18f2450_usb_serial.jal (original)
+++ trunk/sample/18f2450_usb_serial.jal Tue Apr 28 13:52:38 2009
@@ -31,9 +31,11 @@
  -- 3. Create a basic board with USB PIC device
  -- 4. Compile the program (usb_test_cdc) and transfer into the PIC.
  -- 5. After a (short) while you'll get the "new hardware found" message for
---    "CDC RS232 emulation demo". Point Windows manually to the driver in  
the
---    driver directory xp_drivers. Ignore the warning that this driver  
doesn't
---    have a certificate. Wait for the installation to complete.
+--    "JALLIB Serial". Point Windows manually to the driver in the
+--    driver directory xp_drivers The drivers can be found at:
+--    http://groups.google.com/group/jallib/files?upload=1  
(usb_cdc_drivers_winxp32.zip)
+--    Ignore the warning that this driver doesn't have a certificate.
+--    Wait for the installation to complete.
  --
  -- 6. Open the Windows Device Manager and check out the "ports" section. A  
new
  --    communications port will be there, with a COM number.
@@ -52,7 +54,7 @@
  --
  --
  --
--- This file has been generated on 04/27/09 23:03:32, from:
+-- This file has been generated on 04/28/09 21:22:13, from:
  --    * board: board_18f2450_af.jal
  --    * test : test_usb_serial.jal
  --
@@ -106,7 +108,7 @@
  include print

  -- constants
-const  byte str_welcome[] = "JAL USB Serial Demo app\n"
+const  byte str_welcome[] = "JALLIB USB Serial Demo app\n"

  -- variables
  var word i = 0

Modified: trunk/sample/18f4550_usb_serial.jal
==============================================================================
--- trunk/sample/18f4550_usb_serial.jal (original)
+++ trunk/sample/18f4550_usb_serial.jal Tue Apr 28 13:52:38 2009
@@ -31,9 +31,11 @@
  -- 3. Create a basic board with USB PIC device
  -- 4. Compile the program (usb_test_cdc) and transfer into the PIC.
  -- 5. After a (short) while you'll get the "new hardware found" message for
---    "CDC RS232 emulation demo". Point Windows manually to the driver in  
the
---    driver directory xp_drivers. Ignore the warning that this driver  
doesn't
---    have a certificate. Wait for the installation to complete.
+--    "JALLIB Serial". Point Windows manually to the driver in the
+--    driver directory xp_drivers The drivers can be found at:
+--    http://groups.google.com/group/jallib/files?upload=1  
(usb_cdc_drivers_winxp32.zip)
+--    Ignore the warning that this driver doesn't have a certificate.
+--    Wait for the installation to complete.
  --
  -- 6. Open the Windows Device Manager and check out the "ports" section. A  
new
  --    communications port will be there, with a COM number.
@@ -52,7 +54,7 @@
  --
  --
  --
--- This file has been generated on 04/27/09 23:03:52, from:
+-- This file has been generated on 04/28/09 21:22:34, from:
  --    * board: board_18f4550_af.jal
  --    * test : test_usb_serial.jal
  --
@@ -114,7 +116,7 @@
  include print

  -- constants
-const  byte str_welcome[] = "JAL USB Serial Demo app\n"
+const  byte str_welcome[] = "JALLIB USB Serial Demo app\n"

  -- variables
  var word i = 0

Modified: trunk/test/peripheral/usb/test_usb_serial.jal
==============================================================================
--- trunk/test/peripheral/usb/test_usb_serial.jal       (original)
+++ trunk/test/peripheral/usb/test_usb_serial.jal       Tue Apr 28 13:52:38 2009
@@ -31,9 +31,11 @@
  -- 3. Create a basic board with USB PIC device
  -- 4. Compile the program (usb_test_cdc) and transfer into the PIC.
  -- 5. After a (short) while you'll get the "new hardware found" message for
---    "CDC RS232 emulation demo". Point Windows manually to the driver in  
the
---    driver directory xp_drivers. Ignore the warning that this driver  
doesn't
---    have a certificate. Wait for the installation to complete.
+--    "JALLIB Serial". Point Windows manually to the driver in the
+--    driver directory xp_drivers The drivers can be found at:
+--    http://groups.google.com/group/jallib/files?upload=1  
(usb_cdc_drivers_winxp32.zip)
+--    Ignore the warning that this driver doesn't have a certificate.
+--    Wait for the installation to complete.
  --
  -- 6. Open the Windows Device Manager and check out the "ports" section. A  
new
  --    communications port will be there, with a COM number.
@@ -59,7 +61,7 @@
  include print

  -- constants
-const  byte str_welcome[] = "JAL USB Serial Demo app\n"
+const  byte str_welcome[] = "JALLIB USB Serial Demo app\n"

  -- variables
  var word i = 0

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to