Comment #2 on issue 154 by robhamerling: USB RAM locations (BDT & Data)
http://code.google.com/p/jallib/issues/detail?id=154
In general: when required information for the Jallib device files cannot be
obtained from MPLAB .dev or .lkr files the 'standard' solution is to put it
in 'devicespecific.json' (in the tools directory). This file currently
contains for example the default config bits setting and the ADC group.
The file devicespecific.json could be extended for USB library support,
resulting in the declaration of one or more constants in the Jallib device
files. When these constants are not defined the device doesn't have an USB
module or the USB libraries do not support this device (yet).
This would require the following actions:
1. extend devicespecific.json with (for example) USBBASE = 0x....
for every PIC which is supported by the USB libraries
(to begin with for the devices mentioned in comment # 1)
2. adapt the dev2jal script to generate
const USB_BASE_ADDRESS = 0x....
and generate new device files
3. Adapt the USB libraries to use new constants like USB_BASE_ADDRESS
in the new device files
If this looks like a workable solution I need to know which contants are
required (or desired) in the device files!
--
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.
