gnupic: Thread: a couple newbie questions

Hi all,

just getting started here, and thought before i start programming hardware i 
could play around with the simulator gpsim.
However i believe i am doing something wrong because every statement I'm 
getting an INVALID.  I am using to sample .asm files that seem to assemble 
fine.

the command i'm using is:
gpsim -pp16c84 Blink.hex
gpsim -pp16c84 Blink.cod

or when i try to load it i get a:
***ERROR: parse error, expecting `BIT_FLAG'
its probably something simple.
What exactly is a cod file?
This after referring to the manual.


2nd question: 
I found a usb programmer that states it has Linux and FreeBSD drivers built 
in.  Has anyone ever tried one of these?
USB Powered MPLAB Compatible 8/14/18/28/40 Pin ZIFF+ ICSProgammer 
made by olimex.
It can be viewed here:
http://www.sparkfun.com/shop/index.php?shop=1&cart=76401&cat=3&


3rd question:
If the above is a bad idea, any suggestions on where and what to buy?  It 
needs to be a parallel one.

Thanks in advance

Joe

On Fri, 2 Jul 2004, it was written:

> Hi all,
>
> just getting started here, and thought before i start programming hardware i
> could play around with the simulator gpsim.
> However i believe i am doing something wrong because every statement I'm
> getting an INVALID.  I am using to sample .asm files that seem to assemble
> fine.
>
> the command i'm using is:
> gpsim -pp16c84 Blink.hex

That works for me.


> gpsim -pp16c84 Blink.cod

This should be:

gpsim -s Blink.cod

The .cod file is a symbol file. It contains all of the information about 
your project (like the processor, the .hex code and where the source files 
are located).

You may've captured an intermediate snap shot of the CVS code that wasn't 
working. Try updating your cvs image and see if that fixes your problem.

Scott

Hi, Joe!

I'd suggest you to use the following command if you'd like to the .cod 
symbol file:
gpsim -s Blink.cod -pp16c84 Blink.hex
If you start gpsim this way, your problem should disappear

IMHO, command "gpsim -pp16c84 Blink.cod" is invalid because cod-file 
should be loaded with '-s' prefix. All commads are disassembled as 
INVALID if you didn't load any cod file.

As i know, cod-file contains some symbolic information (like variable 
names, its addresses and the like).

Joseph Greenawalt wrote:

>Hi all,
>
>just getting started here, and thought before i start programming hardware i 
>could play around with the simulator gpsim.
>However i believe i am doing something wrong because every statement I'm 
>getting an INVALID.  I am using to sample .asm files that seem to assemble 
>fine.
>
>the command i'm using is:
>gpsim -pp16c84 Blink.hex
>gpsim -pp16c84 Blink.cod
>
>or when i try to load it i get a:
>***ERROR: parse error, expecting `BIT_FLAG'
>its probably something simple.
>What exactly is a cod file?
>This after referring to the manual.
>
>
>2nd question: 
>I found a usb programmer that states it has Linux and FreeBSD drivers built 
>in.  Has anyone ever tried one of these?
>USB Powered MPLAB Compatible 8/14/18/28/40 Pin ZIFF+ ICSProgammer 
>made by olimex.
>It can be viewed here:
>http://www.sparkfun.com/shop/index.php?shop=1&cart=76401&cat=3&
>
>
>3rd question:
>If the above is a bad idea, any suggestions on where and what to buy?  It 
>needs to be a parallel one.
>
>  
>
We use Averon MP3 as prograamer and ICD for PIC16F87X controlled by 
Microchip MPLAB under Windows. It's connected to COM-port. I wouldn't 
suggest you to buy this thing because it's quite expensive, slow and has 
a lot of limitations ( like it doesn't support p16c84).

>Thanks in advance
>
>Joe
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>
>  
>

-- 

Best regards,
Alex Ziranov.

Pyastra project: http://pyastra.sourceforge.net/

ICQ: 22365524
Jabber: estyler (at) plotinka (dot) ru

On Fri, 2 Jul 2004, estyler wrote:

> Hi, Joe!
>
> I'd suggest you to use the following command if you'd like to the .cod symbol 
> file:
> gpsim -s Blink.cod -pp16c84 Blink.hex
> If you start gpsim this way, your problem should disappear

again, all you need is:

gpsim -s Blink.cod

I probably should make this command line entry generate an error.

Scott

That did it, thanks!

On Friday 02 July 2004 2:30 pm, estyler wrote:
> Hi, Joe!
>
> I'd suggest you to use the following command if you'd like to the .cod
> symbol file:
> gpsim -s Blink.cod -pp16c84 Blink.hex
> If you start gpsim this way, your problem should disappear
>
> IMHO, command "gpsim -pp16c84 Blink.cod" is invalid because cod-file
> should be loaded with '-s' prefix. All commads are disassembled as
> INVALID if you didn't load any cod file.
>
> As i know, cod-file contains some symbolic information (like variable
> names, its addresses and the like).
>
> Joseph Greenawalt wrote:
> >Hi all,
> >
> >just getting started here, and thought before i start programming hardware
> > i could play around with the simulator gpsim.
> >However i believe i am doing something wrong because every statement I'm
> >getting an INVALID.  I am using to sample .asm files that seem to assemble
> >fine.
> >
> >the command i'm using is:
> >gpsim -pp16c84 Blink.hex
> >gpsim -pp16c84 Blink.cod
> >
> >or when i try to load it i get a:
> >***ERROR: parse error, expecting `BIT_FLAG'
> >its probably something simple.
> >What exactly is a cod file?
> >This after referring to the manual.
> >
> >
> >2nd question:
> >I found a usb programmer that states it has Linux and FreeBSD drivers
> > built in.  Has anyone ever tried one of these?
> >USB Powered MPLAB Compatible 8/14/18/28/40 Pin ZIFF+ ICSProgammer
> >made by olimex.
> >It can be viewed here:
> >http://www.sparkfun.com/shop/index.php?shop=1&cart=76401&cat=3&
> >
> >
> >3rd question:
> >If the above is a bad idea, any suggestions on where and what to buy?  It
> >needs to be a parallel one.
>
> We use Averon MP3 as prograamer and ICD for PIC16F87X controlled by
> Microchip MPLAB under Windows. It's connected to COM-port. I wouldn't
> suggest you to buy this thing because it's quite expensive, slow and has
> a lot of limitations ( like it doesn't support p16c84).
>
> >Thanks in advance
> >
> >Joe
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: ####@####.####
> >For additional commands, e-mail: ####@####.####