|
|
View previous topic :: View next topic |
Author |
Message |
drdelphi
Joined: 22 Apr 2007 Posts: 22 Location: Romania
|
|
Posted: Wed Feb 11, 2009 5:40 pm |
|
|
Did anyone notice in versions 4.084 and 4.085 that boolean variables refuse to be assigned the false value ? (pic24fj32ga002)
The same program that worked in 4.083, behaves odd in current version. I had to replace boolean with int8 and now it works again. |
|
|
Guest
|
SPI slave mode |
Posted: Wed Mar 11, 2009 1:42 pm |
|
|
Just wondering if anyone has had success programming the pins for slave mode? I'm getting the following error when trying to declare the bus as a slave:
Option invalid: Not valid for H/W-SAMPLE_COUNT
This is how i've set up the pins:
//set up SPI bus for compass
#pin_select SDI2 = PIN_F3
#pin_select SDO2 = PIN_F4
#pin_select SCK2OUT = PIN_F5
#use spi (SLAVE, SPI2, MODE=1, bits=8, stream = COMPASS1)
The same pin configuration will compile for a device running in master mode. |
|
|
Guest
|
All Inherent Problems With PCDIDE Resolved |
Posted: Mon Mar 16, 2009 10:38 pm |
|
|
Rebooted system and was able to Compile and debug with Zero
Problems. However that was after installing the Microchip C30
development Tools on my system.
PCDIDE was $350 down the drain at this point.
Did get a card in mail about buying maintenance
for an additional $150. how quaint.
Upper CCS Management should be discharged
for releasing for sale such a abomnation ... |
|
|
richi-d
Joined: 28 Aug 2007 Posts: 106
|
Problems when compiling |
Posted: Mon Apr 06, 2009 11:58 am |
|
|
Always when I press the Build all button this Error Message pops up:
"The configuration bits in the file are invalid and may cause problems if programmed.
Do you want to set them to their default value?
Please note that you will need to either rebuild the file or export memory again to correct the file."
I use MPLABIDE8.10 and 8.30, Real ICE (same with ICD2), Compiler Version 4.089. PIC24FJ128GA106...
When I press in the message the "YES" Button I can read "Build succeed", if I press "NO" also "Build succeed"
Here the configuration bits:
//#FUSES FRC_PLL,NOWDT,NOPROTECT,DEBUG,NOCOE,NOIESO,NOPR
I tried it with and without //
Whats wrong? |
|
|
straw
Joined: 22 Apr 2009 Posts: 2
|
Dspic33FJ256GP710 digital input (Port B and E) undetectable |
Posted: Thu Apr 23, 2009 1:34 am |
|
|
Is there anybody come across this problem, where digital signal from Port B and E undetectable. And there is no problem if I tris the ports to output. Anyone can help, please? |
|
|
Guest
|
Re: Dspic33FJ256GP710 digital input (Port B and E) undetecta |
Posted: Wed May 20, 2009 4:20 pm |
|
|
straw wrote: | Is there anybody come across this problem, where digital signal from Port B and E undetectable. And there is no problem if I tris the ports to output. Anyone can help, please? |
Hi,
try this:
setup_adc_ports(no_analogs);
setup_adc_ports2(NO_ANALOGS); |
|
|
Garfield Guest
|
Just Sent This on PCD Compiler......Comments |
Posted: Wed Jun 03, 2009 6:03 am |
|
|
Hi,
I am contacting you regarding the 16bit PCD compiler that I have been paying for since November 2007.
This week I started a project that needed a PIC24FJ256GB106 to be used, so I thought that it would be plain sailing using your compiler as it has been in circulation since Nov 2007.
Well was I wrong, this compiler is riddled with SIMPLE bugs that should have been caught months ago.
1) The help file that comes with the compiler does not does not match up with the commands allowed, you need to download the manual to get the proper command syntax to use.
2) The set_compare() function does not work, writes data into IC9BUF address 0x184.
3) The set_pwm_duty() function does not work, writes data into IC9CON1 address 0x80
4) And yes pin_select OC1 = PIN_G6
5) pin_select U1RX = PIN_B5 sets U1RX correctly and also sets U1CTS to RP1 (not what I asked it to do)
6) pin_select U2RX = PIN_B7 sets U2RX correctly and also sets U2CTS to RP1 (not what I asked it to do)
7) Now I have two pins trying to access RP1.....!!!
8) If I set the #fuses for the device, MPLAB does not like them. If I set them manually from within the software using a #ROM statement then MPLAB accepts them.
9) The compiler is not handling data within a structure correctly, see below.
Code: |
typedef union
{
int16 data;
struct
{
int8 OCM:3;
}b;
}
|
Code: |
.................... OCxCON1.data = 0;
00306: CLR 95A
.................... OCxCON1.b.OCM = PWM_ON_NO_FAULT;
00308: MOV 95A,W4
0030A: AND #3F8,W4 <-----why AND with 3F8.....need to AND with FFF8
0030C: IOR #6,W4
0030E: MOV.B W4L,W0L
00310: MOV.B W0L,95A
.................... OCxCON1.b.OCTSEL = use_timer;
00312: MOV #FFE3,W0
00314: AND.B 95B
00316: MOV.B 95C,W0L
00318: SL W0,#2,W0
0031A: AND.B #1C,W0L
0031C: IOR.B 95B
|
Had to use below to get the software to work.
Code: |
.................... OCxCON1.data = PWM_ON_NO_FAULT | (use_timer << 10);
00306: MOV 95C,W0
00308: SL W0,#A,W0
0030A: IOR W0, #6,W0
0030C: MOV W0,95A
|
This was written to get around the fact that the set_ compare() and set_pwm_duty() functions do not work.
10) These problems were found after four days of playing with the compiler....and I have not yet even got into using it in anger yet.
Today I had to make a decision......to continue with your compiler or move to another......well sorry to say you have lost out......
I do not have the time to check every c function or data access that your compiler generates to check that it does what it should do
so I have had to move to the Microchip C compiler.
Instead of announcing that version 4.100 is coming how about fixing the problems that you already have and supplying a compiler that I can use.
I look forward to your response.
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|