Release Notes for MPLAB® VDI Visual Device Initializer
MPLAB® IDE v8.15
Software DLL Version v3.0
September 22, 2008
Table of Contents
5 Repairs and
Enhancements Made in v3.0
Click the link below to see device support for the visual initializer (VDI).
This tool has been tested under the following operating systems:
Windows® 2000 SP4, Windows XP SP2, and
Window Vista™
IMPORTANT NOTICE: Beginning with MPLAB IDE v7.51, MPLAB IDE and MPLAB VDI will no longer be tested on Windows 98, Windows ME, or Windows NT. MPLAB IDE and MPLAB VDI may continue to work under these operating systems, but their operation will no longer be verified through testing.
The following documents may be found on our website or MPLAB IDE CD-ROM:
· Device data sheets - various DS numbers
On-line help (Help>Topics) is also available for this tool:
· Tools>Visual Device Initializer
The default location of the Help file and a tutorial is:
· C:\Program Files\Microchip\MPLAB IDE\VDI\hlpMPLABVDI.chm
· C:\Program Files\Microchip\MPLAB IDE \VDI\doc\VDI Tutorial.pdf
On-line Web Seminars are also available for this tool:
· Introduction to the MPLAB Visual Device Initializer (VDI)
N/A
The following is a list of known problems. Bolded prefix represents internal tracking numbers.
VDI-7: Wrong baud rate calculation for CAN/ECAN module.
VDI-401: The option
'Generate Read-Modify-Write instruction sequence for SFR initialization' has
been disabled for all devices in MPLAB VDI.
VDI-600: Code generation
options do not work as expected.
VDI-50: [PIC18F6520/6620/6720/8520/8620/8720] For all five CCP PWM, CCP IC and
CCP OC modules, VDI generates incorrect code for Time base selection.
VDI-186: [PIC18CXX2,
PIC18FXX2] Code generated for initializing PORT A and E does not initialize
ADCON1.
VDI-121: When trying to configure POR/BOR, WDT using
VDI, error message displayed.
VDI-135: In RTCC Configuration window, incorrect code
gets generated for (B1) RTSECSEL of PADCFG1 register for selecting RTCC pin
Output Selection.
VDI-136: In RTCC Configuration window, incorrect code
gets generated for (B13:10) AMASK3:0 of ALCFGRPT for selecting Repeat Alarm.
VDI-138: For ICx, In correct code gets generated for
ICxCON register.Similar error occurs for OC(OCxCON).
VDI-142: For any setting of I2Cx (I2C1 or I2C2), gives
error message "Can't find bitfield `i1_I2CBRG'" being claimed in
control baudRate
VDI-192: The calculated
Fcy shown in oscillator configuration window and also the code generated for
clock source as 'Internal FRC with postscalar' are incorrect.
VDI-194: [ PIC24FJ128GA
FAMILY ] Calculated percentage error for UART baud rate shows wrong value on
apply and code generated does not set BRGH bit even if high baud rate is
selected.
VDI-199: [PIC24FJ64GA004
FAMILY] In SPI configuration window there is no option to select the eight
buffer interrupt modes for SPIx (enhanced buffer mode).
VDI-501: [PIC24FJ64GA004
Family] Selecting various debugging pin pairs in System parameter window will
not generate appropriate code (configuration bits).
VDI-502: [PIC24FJ64GA004
Family] Oscillator - Code generated for switching and monitor mode is not proper.
VDI-520: [PIC24FJ16GA004]
Oscillator module claims OSCI and OSCO pins even when Internal FRC, Internal
LPRC, and Secondary Oscillator modes are selected.
VDI-521: [PIC24FJ16GA004]
The Comparator modules 1 & 2 always claim the pins CxIN+, CxIN- and CVREF,
irrespective of the Inputs selected in the configuration window.
VDI-522: [PIC24FJ16GA004]
Enabling the Interrupt in many peripherals gives 'Can't find bitfield....'
error messages in the Output window.
VDI-537: [PIC24FJ] - On
configuring oscillator module, "can't find pin......" error messages
are seen in the output window.
VDI-538: [PIC24FJxxxGBxxx,
PIC24FJxxxGAxxx] - Generated code doesn't compile due to syntax errors.
VDI-546: [PIC24FJ64GA004
family] - I2C1 module claims both the primary and alternate pairs of pins at
the same time.
VDI-561:
[PIC24FJxxxGAxxx, PIC24FJxxxGBxxx PPS devices] - Code not generated for PPS
initialization.
VDI-616: Configuring any
UART or PPS function of PIC24FxxxGA106 PPS devices will generate many ‘can't
find bit field’ errors.
VDI-160: [dsPIC30F3011/3013/6010/6010A/6015] For any
setting of UART2, gives error message "Can't find bitfield `i1_U2BRG'"
VDI-161: [dsPIC30F3013] For any setting of UART2, gives
error message "Can't find bitfield `i1_U2BRG'". Also, IPC6 register
is not available in code generation.
VDI-525: [dsPIC30F
devices] - Some dsPIC30F devices show two UART1 modules in the left hand
feature/resource pane.
VDI-551: [dsPIC30F] - In
the Interrupts and Traps configuration window, selecting 'Alternate' Interrupt
vector table and enabling interrupts generates an error.
VDI-405: [ dsPIC33 100pin
] Configuring an IO port pin as input on an already claimed pin will not
generate pin assignment conflict. This issue will not
affect code generation.
VDI-441: [dsPIC33 100 pin] Configuring ADC1 and ADC2 simultaneously will generate
pin conflict errors for analog pins that are used by both ADCs. This issue will
not affect code generation.
VDI-477: [dsPIC33 100 pin] In UART configuration
window, if the loopback mode is enabled then UxTX is not claimed.
VDI-541: [dsPIC33F MC devices] MPLAB VDI should make
sure that pins multiplexed with ADC input channels are made digital if they are
not used by the ADC.
VDI-542: [dsPIC33F 60-pin devices] Compiling MPLAB VDI
code gives 'undefined reference to....' error.
VDI-547: [dsPIC33 MC Devices] On configuring DMA, MPLAB
VDI generates many "Can't find bitfield......" errors.
VDI-553: [dsPIC33 MC devices] In the QEI configuration
window, the Digital Filter configuration settings/options are grayed out.
VDI-574: [dsPIC33FxxxGPx06] MPLAB VDI doesn't generate
any code for initializing ECAN (CAN) peripheral.
VDI-577: [dsPIC33 MC devices] MPLAB VDI fails to
generate code for ECAN buffer pointer registers CiBUFPNT1, CiBUFPNT2, CiBUFPNT3
and CiBUFPNT4.
VDI-581: [dsPIC33 MC devices] In PWM configuration
window, there is no provision to enable Fault A and Fault B Interrupts and to
set their priorities.
VDI-593: [dsPIC33 MC devices] MPLAB VDI code always
clears I2CxBRG registers; "Can't find bitfield `i1_I2CBRG'..." errors
generated when I2Cx modules are configured.
The code generation
option ‘Generate Read-Modify-Write instruction sequence for SFR initialization’
is currently not supported.
VDI-375: In the SPI
configuration window, if OK is
clicked without entering a proper baud rate value then an error window pops up
to indicate the same and all the SPI settings made will be lost after the error
window is closed.
VDI-377: Comments giving
SFR bit field information for many Interrupt related registers and other
registers should be updated to reflect the changes made in rev B of the
devices.
· Basic use: Click-and-drag a feature from the palette on the left onto the chip in the middle. Once on the chip, click the feature to configure it.
· Right-click is your best friend in VDI. Right-click the chip graphic to set/view system parameters, like ICD/ICSP.
· “Apply” is also your friend. You can “Apply” incrementally to make sure your configuration won't cause trouble.
· Zoom is neat. Try it after you've configured a port or communications peripheral (or something).
· If there is a conflict between features/peripherals, they turn red and any conflicting pins turn red. Float your cursor over a pin and it will tell you its conflict/assignment. Left-click the peripheral icon and it will tell you, too. (The default left-click-action changes for peripheral icons if they are in conflict.)
· If the compiler or assembler is having trouble finding Visual Initializer files when you build your project, try specifying the paths to these files in the MPLAB IDE Build Options dialog, i.e., Project>Build Options>Project, Directories tab.