Building a Hex With Ch 8 Source Files

[Abraxas]

Greetings. I'm using this book from Chapter 8 onwards, for a variety
of reasons I won't get into. After opening the project in the IDE
8.36, a build is unsuccessful as follows:

Debug build of project `E:\code\chap8\ledflash_nomacros.mcp' started.
Language tool versions: pic30-as.exe v3.20, pic30-gcc.exe v3.20, pic30-
ld.exe v3.20, pic30-ar.exe v3.20
Preprocessor symbol `__DEBUG' is defined.
Tue Jul 26 04:18:54 2011
----------------------------------------------------------------------
Clean: Deleting intermediary and output files.
Clean: Done.
Executing: "C:\Program Files\Microchip\MPLAB C30\bin\pic30-gcc.exe" -
mcpu=24HJ32GP202 -x c -c "..\common\pic24_clockfreq.c" -
o"pic24_clockfreq.o" -I"..\include" -D__DEBUG -g -Wall -O1
..\common\pic24_clockfreq.c:188:2: warning: #warning Clock configured
for FRCPLL, FCY = 40 MHz
Assembler messages:
FATAL: can't create pic24_clockfreq.o: Permission denied
Halting build on first failure as requested.
----------------------------------------------------------------------
Debug build of project `E:\code\chap8\ledflash_nomacros.mcp' failed.
Language tool versions: pic30-as.exe v3.20, pic30-gcc.exe v3.20, pic30-
ld.exe v3.20, pic30-ar.exe v3.20
Preprocessor symbol `__DEBUG' is defined.
Tue Jul 26 04:18:57 2011
----------------------------------------------------------------------
BUILD FAILED

I note that all I have is C and header files plus one bootldr.gld
file. I'm guessing my rush to start at CH 8 has caused me to skip over
instructions, in an earlier chapter on how one gets from these files
to a successfully compiled hex file. Can anyone tell me what the steps
are or what is causing this build failure ? Thanks.

[Bryan A. Jones]

Looking at your output:

FATAL: can't create pic24_clockfreq.o: Permission denied

Perhaps you loaded this up in another session of MPLAB? Try deleting it manually then recompiling.

--
You received this message because you are subscribed to the Google Groups "PIC24 Assembly-to-C Book" group.
To post to this group, send email to pic24-assemb...@googlegroups.com.
To unsubscribe from this group, send email to pic24-assembly-to-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pic24-assembly-to-c-book?hl=en.

--
Bryan A. Jones, Ph.D.
Assistant Professor
Department of Electrical and Computer Engineering
231 Simrall / PO Box 9571
Mississippi State University
Mississippi state, MS 39762
http://www.ece.msstate.edu/~bjones
bjones AT ece DOT msstate DOT edu
voice 662-325-3149
fax 662-325-2298

Our Master, Jesus Christ, is on his way. He'll show up right on
time, his arrival guaranteed by the Blessed and Undisputed Ruler,
High King, High God.
- 1 Tim. 6:14b-15 (The Message)

[Abraxas]

How I loaded it was by clicking on the project file on the DVD. Once
loaded, I simply clicked on Build All. In hopeful compliance with your
suggestion of two instances of the IDE being opened, I shut everything
down and repeated the same opening procedure with the same error and
result.

> Mississippi state, MS 39762http://www.ece.msstate.edu/~bjones

[Bob]

Please try copying the files on the DVD to the C: drive. I believe
that the problem is that by opening the project on the DVD, MPLAB is
trying to write the object files and whatnot back to the DVD, which is
write protected.

The "FATAL: can't create pic24_clockfreq.o: Permission denied "
message indicates that new files cannot be created in the target
directory.

[Abraxas]

Sorry for the bother but now, after copying the files to my hard
drive, I still can't build all. I now get the error:

Debug build of project `C:\Electronics\Reese Book\Reese Code DVD\code
\chap8\ledflash.mcp' started.

Language tool versions: pic30-as.exe v3.20, pic30-gcc.exe v3.20, pic30-
ld.exe v3.20, pic30-ar.exe v3.20
Preprocessor symbol `__DEBUG' is defined.

Wed Jul 27 23:04:33 2011

----------------------------------------------------------------------
Clean: Deleting intermediary and output files.

Clean: Deleted file "C:\Electronics\Reese Book\Reese Code DVD\code
\chap8\pic24_clockfreq.o".

Clean: Done.
Executing: "C:\Program Files\Microchip\MPLAB C30\bin\pic30-gcc.exe" -
mcpu=24HJ32GP202 -x c -c "..\common\pic24_clockfreq.c" -
o"pic24_clockfreq.o" -I"..\include" -D__DEBUG -g -Wall -O1
..\common\pic24_clockfreq.c:188:2: warning: #warning Clock configured
for FRCPLL, FCY = 40 MHz
Executing: "C:\Program Files\Microchip\MPLAB C30\bin\pic30-gcc.exe" -

mcpu=24HJ32GP202 -x c -c "..\common\pic24_configbits.c" -
o"pic24_configbits.o" -I"..\include" -D__DEBUG -g -Wall -O1
..\common\pic24_configbits.c:259: error: 'BKBUG_ON' undeclared here
(not in a function)
..\common\pic24_configbits.c:259: error: 'COE_ON' undeclared here (not
in a function)

Halting build on first failure as requested.
----------------------------------------------------------------------

Debug build of project `C:\Electronics\Reese Book\Reese Code DVD\code
\chap8\ledflash.mcp' failed.

Language tool versions: pic30-as.exe v3.20, pic30-gcc.exe v3.20, pic30-
ld.exe v3.20, pic30-ar.exe v3.20
Preprocessor symbol `__DEBUG' is defined.

Wed Jul 27 23:04:36 2011
----------------------------------------------------------------------
BUILD FAILED

[Bob]

Please try downloading the code archive from:

http://www.reesemicro.com/Home/pic24-software-library-collection

(click on the 'downloadable libraries' link). We have updated the
libraries
several times since the book was released, I don't know why the DVD
version
is failing. If you download the library from the code site, at least I
will know what version
you have so that I can repeat the problem.

Thanks.

[Abraxas]

SUCCESS !!! THANK YOU. Hopefully will not see this problem return
although it would have been interesting to find out what it was
exactly that caused the problem. Anyhow, I'm off and running. Thanks
again.

[Bob]

Glad you got it working. There have been several compiler changes
that have caused problems with some files -- we try to keep the Web
version up to date with Microchip changes.

[icserny]

> ..\common\pic24_configbits.c:259: error: 'BKBUG_ON' undeclared here (not in a function)
> ..\common\pic24_configbits.c:259: error: 'COE_ON' undeclared here (not in a function)

The error messages above appeared because Microchip changed their
software/hardware, and the Config bits BKBUG and COE are no longer
existing/supported (and are not defined in the header files). You can
simply remove their ocurence from file pic24_configbits.c.

Modify the following line:
_FICD(BKBUG_ON & COE_ON & JTAGEN_OFF & ICS_PGD1);

to this:
_FICD( JTAGEN_OFF & ICS_PGD1)


Hope this helps.

István

[Bryan A. Jones]

Isvan,

Thanks for the report -- pardon my slow response. I haven't seen this before -- which chip are you compiling for and what version of the compiler do you use?  v3.30 of the compiler is fine for the PIC24HJ32GP202, but I suspect this pops up on another chip.

Thanks again for the help!

Bryan

--

You received this message because you are subscribed to the Google Groups "PIC24 Assembly-to-C Book" group.
To post to this group, send email to pic24-assemb...@googlegroups.com.
To unsubscribe from this group, send email to pic24-assembly-to-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pic24-assembly-to-c-book?hl=en.

["István, Cserny"]

Hi Bryan,

The changes I've mentioned are related to PIC24HJ128GP502 and "relatives" (I think also  the popular PIC24HJ64GP502 shoud be among them). The the software on the CD which comes with your PIC24 book used to set up the BKBUG and COE bits. This was OK (but probably useless, since - as far I as know - these bits were never implemented in the hardware ) for the MPLAB 8.15 and the "contemporary" C30 compaler (probably ver 3.11). 

Newer versions of MPLAB/C30 , however, don't define these configuration bits for these chips, so one must either remove these config bit settings from the original software (which comes on the CD), or should upgrade the PIC24 support library from your webpage.

Best regards,

Istvan

[Abraxas]

It was the books specified HJ32GP202.As for compiler version I regret
that I have just installed a new op sys and wiped out my MChip
installations. It was however a very up to date version... 8 point
something if I recall correctly.

On Aug 9, 4:17 am, "István, Cserny" <icse...@gmail.com> wrote:
> Hi Bryan,
>
> The changes I've mentioned are related to PIC24HJ128GP502 and
> "relatives" (I think also  the popular PIC24HJ64GP502 shoud be among
> them). The the software on the CD which comes with your PIC24 book used
> to set up the BKBUG and COE bits. This was OK (but probably useless,
> since - as far I as know - these bits were never implemented in the
> hardware ) for the MPLAB 8.15 and the "contemporary" C30 compaler
> (probably ver 3.11).
>
> Newer versions of MPLAB/C30 , however, don't define these configuration
> bits for these chips, so one must either remove these config bit
> settings from the original software (which comes on the CD), or should
> upgrade the PIC24 support library from your webpage.
>
> Best regards,
>
> Istvan

> 2011.08.09. 5:40 keltez�ssel, Bryan A. Jones �rta:

>
>
>
>
>
>
>
> > Isvan,
>
> > Thanks for the report -- pardon my slow response. I haven't seen this
> > before -- which chip are you compiling for and what version of the
> > compiler do you use?  v3.30 of the compiler is fine for the
> > PIC24HJ32GP202, but I suspect this pops up on another chip.
>
> > Thanks again for the help!
>
> > Bryan
>

> > On Thu, Jul 28, 2011 at 1:07 PM, icserny <icse...@gmail.com
> > <mailto:icse...@gmail.com>> wrote:
>
> >     > ..\common\pic24_configbits.c:259: error: 'BKBUG_ON' undeclared
> >     here (not in a function)
> >     > ..\common\pic24_configbits.c:259: error: 'COE_ON' undeclared
> >     here (not in a function)
>
> >     The error messages above appeared because Microchip changed their
> >     software/hardware, and the Config bits BKBUG and COE are no longer
> >     existing/supported (and are not defined in the header files). You can
> >     simply remove their ocurence from file pic24_configbits.c.
>
> >     Modify the following line:
> >     _FICD(BKBUG_ON & COE_ON & JTAGEN_OFF & ICS_PGD1);
>
> >     to this:
> >     _FICD( JTAGEN_OFF & ICS_PGD1)
>
> >     Hope this helps.
>

> >     Istv�n

>
> >     --
> >     You received this message because you are subscribed to the Google
> >     Groups "PIC24 Assembly-to-C Book" group.
> >     To post to this group, send email to
> >     pic24-assemb...@googlegroups.com

> >     <mailto:pic24-assemb...@googlegroups.com>.

> >     To unsubscribe from this group, send email to
> >     pic24-assembly-to-...@googlegroups.com

> >     <mailto:pic24-assembly-to-c-book%2Bunsu...@googlegroups.com>.

> >     For more options, visit this group at
> >    http://groups.google.com/group/pic24-assembly-to-c-book?hl=en.
>
> > --
> > Bryan A. Jones, Ph.D.
> > Assistant Professor
> > Department of Electrical and Computer Engineering
> > 231 Simrall / PO Box 9571
> > Mississippi State University
> > Mississippi state, MS 39762

> >http://www.ece.msstate.edu/~bjones<http://www.ece.msstate.edu/%7Ebjones>

[Bryan A. Jones]

The CD that comes with the book is out of date; however, the .zip archive on the web works for me with v3.30.

[Abraxas]

"zip archive on the web" ??????????????????? would be where ??? Sorry
I just had to upgrade to Windows 7 to support other software and have
lost my IDE. I'll download latest version.Please advise if you have
another preferred IDE

> Mississippi state, MS 39762http://www.ece.msstate.edu/~bjones

[Abraxas]

I just installed 8.76. The new 'X" IDE is a beta edition so I avoided
that.

[Bob]

The libraries are here:
http://www.reesemicro.com/Home/pic24-software-library-collection

[Abraxas]

I don't see the include files, amongst other things, in this new
directory listing. Are we to construct a hybrid combination of old and
new ? Also while we are on the topic of include files: Page 294
introduces some Macros that apparently automate pin configurations.
All I can see in the include libraries are the Hex files. I'd like to
see what's in this code...ie the source code. Honestly, I'd be happy
to just be able to set up my 4 PortB pins to drive a stepper in open
drain (via driver chips of course). I can't even figure out how to do
this by way of these readings. Do I add pic24hj32gp202_ports.h to my
project and then #include <pic24hj32gp202_ports.h> in my header ? I
then added the lines :

#include <p24HJ32GP202.h>
#include <pic24hj32gp202_ports.h>

void Main()

{


CONFIG_RB0_AS_DIG_OUTPUT();
CONFIG_RB1_AS_DIG_OUTPUT();
CONFIG_RB2_AS_DIG_OUTPUT();
CONFIG_RB3_AS_DIG_OUTPUT();

}

"I wouldn't give a fig for the simplicity this side of complexity, but
I'd give my life for the simplicity on the other side of complexity"
some smart judge in the USA.

[Abraxas]

Re my unpublished last post. Although indicating the path to the
include file eliminated many build errors, the following code derived
from the books templates also does not build due to

"C:\Electronics\MyPicProjects\DCStepper1\DCStepper1.c: In function
'Main':
C:\Electronics\MyPicProjects\DCStepper1\DCStepper1.c:16: error: syntax
error before 'CONFIG_RB1_AS_DIG_OD_OUTPUT'

Halting build on first failure as requested.
"

#include <p24HJ32GP202.h>
#include <c:\electronics\Reese Book\Reese Code DVD\code\include\devices
\pic24hj32gp202_ports.h>

#define CONFIG_OutputPin0() CONFIG_RB0_AS_DIG_OD_OUTPUT()
#define CONFIG_OutputPin1() CONFIG_RB1_AS_DIG_OD_OUTPUT()
#define CONFIG_OutputPin2() CONFIG_RB2_AS_DIG_OD_OUTPUT()
#define CONFIG_OutputPin3() CONFIG_RB3_AS_DIG_OD_OUTPUT()

void Main() {

CONFIG_OutputPin0()
CONFIG_OutputPin1()
CONFIG_OutputPin2()
CONFIG_OutputPin3()

}

On Aug 22, 8:31 am, Bob <rbrees...@gmail.com> wrote:

[Bob]

Hi,

You do not have to include <p24HJ32GP202.h>. The new code archive has
the include, common, lkr directories
now all under the 'lib' directory. This means any of your old
projects based on the original CDROM locations
would reference the library files in the wrong place.

The only header file your main code needs to include are (the stdio.h
if you use a printf statement):
#include "pic24_all.h"
#include <stdio.h>

The 'pic24_all.h' file includes all of the right files.
Do not try including any of the device specific include files under
lib/, the correct files will be included automatically.

To create a new project, just open any one of the projects that are in
the code archive, and do 'Project>Save Project As' and rename as your
new project. Delete the C file from the project that contains the
'main' function, then add your file that has your 'main' function.
Use 'Configure>Set Device' in MPLAB to set to whatever device you wish
to use (by default, will already be set to p24HJ32GP202.

Let me know if you have other questions.

[Abraxas]

I'm sorry, I tried all of this and nothing worked. As I said in a
previous post, I just want to set the first 4 bits in Port B to open
drain, digital outputs. I'm using the examples in the book but I am
getting link failures. I've been at this PIC nightmare for about 5
years now... I'm not joking. As one fellow put it, when you are
dealing with PICs its not like you are programming but rather hacking.
I feel like I'm Helen Keller living in a house where the furniture is
rearranged daily. Can somebody not IN THE SIMPLEST TERMS tell me how
to set these pins to open drain digital outputs ?? I don't want
Macros. Despite the best intentions they aren't doing anything for me
except complicating what I think SHOULD BE a very simple task...very
simple code and concealing code that one who is learning needs to see.
Here's what I came up with from the book and your direction on
headers:

#include "pic24_all.h"

int main (void) {

_TRISB0 = 0;
_PCFG2 = 1;
_ODCB0 = 1;

_TRISB1 = 0;
_PCFG3 = 1;
_ODCB1 = 1;

_TRISB2 = 0;
_PCFG4 = 1;
_ODCB2 = 1;

_TRISB3 = 0;
_PCFG5 = 1;
_ODCB3 = 1;

}
= link failure
...maybe I need to pull up my stakes and head to Mississippi...

[Robert Reese]

The code you have listed should compile, there is something else going wrong. It will also configure the pins as you  want.  The fact that you are getting a link failure means that there is something wrong with the MPLAB environment -- either the project file, linker file, or the device selection or something else.

With your current link problem, it seems that you could probably write:
  #include "pic24_all.h"

int main (void) {

/* a comment, empty main */
}

and it still would not compile, something is wrong. Have you tried compiling any of the other projects?

Please post all of the link error messages that you are getting so that we can understand what is happening.
Also post the zip archive of your project if you can.
Thanks.

Believe or not, the macros do make things much easier and less error prone. The problem is that configuring a pin on the PIC depends on whether it is an analog pin or not, has a pullup or not, etc as you know and we have found that the macros are best way to make students productive in getting things to work.  

[Abraxas]

As far as the macro for setting the pins goes, I'm sorry but I don't
see the listing of what exactly is in that macro. I just see the hex
file so it doesn't help us newbies to understand what the underlying C
code is. I'd like, at least the first time around , to see no macros
but the C code...you know " For a digital output, open drain on the
first PortB pin, bits need to be set in 3 registers with the
following 3 lines of code". You can then go on to say that these lines
will be placed in a macro from then on. Could you please kindly print
out the source code for that macro or kindly tell me where the source
code file is ?? Again, I just see the hex file.

> ...
>
> read more »

[Abraxas]

You are correct, the code you asked me to build did not compile. Here
is the result:

----------------------------------------------------------------------
Debug build of project `c:\electronics\Trial.mcp' started.
Language tool versions: pic30-as.exe v3.30, pic30-gcc.exe v3.30, pic30-
ld.exe v3.30, pic30-ar.exe v3.30

Preprocessor symbol `__DEBUG' is defined.

Sun Aug 28 20:51:41 2011

----------------------------------------------------------------------
Clean: Deleting intermediary and output files.

Clean: Deleted file "c:\electronics\Trial.mcs".
Clean: Done.
Executing: "C:\Program Files\Microchip\mplabc30\v3.30c\bin\pic30-
gcc.exe" -mcpu=24HJ32GP202 -x c -c "C:\Program Files\Microchip
\mplabc30\v3.30c\support\PIC24H\h\trial.c" -o"trial.o" -D__DEBUG -g -
Wall
C:\Program Files\Microchip\mplabc30\v3.30c\support\PIC24H\h\trial.c:
1:25: error: pic24_all.h: No such file or directory
C:\Program Files\Microchip\mplabc30\v3.30c\support\PIC24H\h\trial.c:
In function 'main':
C:\Program Files\Microchip\mplabc30\v3.30c\support\PIC24H\h\trial.c:6:
warning: control reaches end of non-void function
C:\Program Files\Microchip\mplabc30\v3.30c\support\PIC24H\h\trial.c:
6:3: warning: no newline at end of file

Halting build on first failure as requested.

----------------------------------------------------------------------
Debug build of project `c:\electronics\Trial.mcp' failed.
Language tool versions: pic30-as.exe v3.30, pic30-gcc.exe v3.30, pic30-
ld.exe v3.30, pic30-ar.exe v3.30

Preprocessor symbol `__DEBUG' is defined.

Sun Aug 28 20:51:42 2011
----------------------------------------------------------------------
BUILD FAILED

On Aug 24, 8:12 am, Robert Reese <rbrees...@gmail.com> wrote:

> ...
>
> read more »

[Robert Reese]

Macros:
The codes for the pin macros are in two places:
  pic24_code_examples/lib/include/pic24_ports.h  -- has macros common to all devices
  pic24_code_examples/lib/include/device/devicename_ports.h  (eg. pic24hgj32gp202_ports.h) -- contains macros specific to a device

The first include file is included by 'pic24_all.h'.
The second include file is automatically included by the setting of the target device in the MPLAB project file.


Link error:
 The link errors show that MPLAB cannot find the pic24_all.h file.  The MPLAB project files in the CDROM assume that the 'lib' directory is relative to the current project via the path:
 '..\lib\include\pic24.h'

This means that that the 'lib' directory is not under c:\electronics', i.e.,   c:\electronics\lib

So if you opened a project file, say 'chap8/reset.mcp' and compiled it, it should work.   If you save off this project file in the same directory or to any 'chapn' directory in the archive.  If you create a new directory that at the same directory level as any of the 'chapn' directories in the archive and save it there, it should work.

However, if you saved your new project in a directory where the relative path '..\lib\include\pic24.h' is not valid, then you will get the link errors that you are seeing.

Two ways to fix this:

1. Copy the pic24_code_examples\lib directory to c:\lib so that the path ..\lib from the c:\electronics directory is valid. Because you may not want the 'lib' directory under c:\, you may want to  create a directory named c:\electronics\my_projects,  copy your project file, main C file to C:\electronics\my_projects, then copy the lib directory to c:\electronics so that c:\electronics\lib exists and ..\lib exists from the c:\electronics\my_projects directory.

Or

2. Try copying your project file and main C file to once of the 'chapn' directories in the archive and compile it there (or else, create a new directory at the same level as the 'chapn' directories (c:\pic24_code_examples\my_projects) and place it in that directory.

To post to this group, send email to pic24-assemb...@googlegroups.com.
To unsubscribe from this group, send email to pic24-assembly-to-...@googlegroups.com.

[Abraxas]

Actually I finally found success using a third option and that was to
simply tell the linker where the include file was by prefacing the
file name with the path.... specifically, in my case :
#include "c:\electronics\MyPicProjects\lib\include\pic24_all.h"

On Aug 29, 8:29 am, Robert Reese <rbrees...@gmail.com> wrote:
> Macros:
> The codes for the pin macros are in two places:
>   pic24_code_examples/lib/include/pic24_ports.h  -- has macros common to all
> devices

>   pic24_code_examples/lib/include/device/*devicename*_ports.h  (eg.

[Robert Reese]

Glad you solved it!  You can also set an option in the project where you place that directory in its include file search path.