::Programming CluesHardware CluesKnown issues in PBP 2.60A.Devices affected:16F1947Commands affected: HSERIN2, HSEROUT2Date encountered: 01/2011Error class: Safe (always reported)Library routines were omitted for the 16F1xxx partsthat can make use of HSERIN2 and HSEROUT2 commands.A compile error will result when trying to use thesecommands.Fix:We anticipate the timely release of a patch to fixthis. Check back in a few days, or contactsupport.Devices affected: AllEnhanced 14-Bit parts (16F1937, 1827, etc.)Commands affected: HPWMDate encountered: 11/2010Error class: Apparent (no error, but consistently failsinitial testing)HPWM miscalculates the timer prescaler when usinghigher frequency system clocks and relatively lowfrequency output for PWM. (For example:system osc = 32MHz and PWM output = 2KHz. Theactual PWM output will be 500Hz.)Fix:if you can't obtain a usable PWMfrequency. We have a library modification, butwe would like to test it in more cases before wepublish or issue a patch.Below are previously-known issues in PICBASIC PRO Compiler 2.60(All issues listed below have been fixed in version 2.60A.
If you are a user of version 2.60, you should download the to bring your version to 2.60A.)Devices affected: All Enhanced 14-Bit parts (16F1937, 1827, etc.) when using MPASM 5.36Commands affected: All commandsDate encountered: 07/2010Error class: Critical (compile errors in most cases, but some silent bugs)Microchip's release of MPASM 5.36 changes functionality of the assembly operator 'high' for the enhanced 14-bit MCUs. This thouroughly wrecked our command and macro libraries for all families of parts that share the enhanced 14-bit instruction set.Fix:We released a patch within a few days of being notified of this issue. All users should use the to update from 2.60 to 2.60A.Devices affected: 18F2420/2520/4420/4520 FamilyCommands affected: WRITECODEDate encountered: 03/2010Error class: Apparent (no error, but consistently fails initial testing)The WRITECODE command will not write to all locations of code space because the block size is declared incorrectly for this family. Write operations will seem to ignore portions of code space, while writing successfully to other locations.Workaround:In the PBP install folder, locate the.INC file for the device that you are compiling for (18F2420.INC, 18F2520.INC, 18F4420.INC, or 18F4520.INC). Open the file in a text editor and find the line 'BLOCKSIZE EQU 64'. Change the setting to 32: 'BLOCKSIZE EQU 32'.Devices affected: PIC18F46J11 FamilyCommands affected: ADCINDate encountered: 12/2009Error class: Apparent (no error, but consistently fails initial testing)The ADCIN command always doubles the channelparameter. AN0 reads correctly, channel-1 reads AN2, channel-2reads AN4, etc.DEFINE ADCCLOCK writes to the wrong register,breaking all ADCIN commands.
Picbasic Pro Projects
Picbasic Pro Rapidshare With Crack Mac
Even if you omit the define, it stillwrites a default value to the wrong register.Workaround:For the DEFINE ADCCLOCK issue, always write 'DEFINEADCCLOCK 0' and then set the actual clock selection by writing tothe ADCON1 register using direct access:DEFINE ADCCLOCK 0 'safe settingADCON1 =%10000011 ' set ADC clock 3, right justifyFor the channel select, you could read even-number channels with ahalf-value setting.