files, you need to use the extern
> keyword!
>
> Best regards,
> Raphael
> On Jun 21, 2014 10:45 PM, "Joel Davidson" wrote:
>
>> On Sat, 21 Jun 2014, it would appear that Kustaa Nyholm wrote:
>>
>>> On 18/06/2014 16:41, "Maarten Brock"
.c file. If I define it at the .h file
> then I get into trouble with linker if I include the .h file
> in multiple .c files...not god.
>
> br Kusti
Why not put:
#ifndef __VARDEF
volatile BDT __at (0x0400+0*8) ep0_o;
#define __VARDEF
#endif
...other defines
in your .h?
Joel
--
Joel
Hi Richard-
I've used the usb_pickit s/w with my pickit 1 and it provides a great
set of utilities. You'd have to do some research to see if the code
will work with your PICstart.
Joel
--
Joel Davidson
Austin, TX
On Sat, 7 Jun 2014, it would appear that Richard Gray wrote:
Ael-
It looked like your source code was missing the config register
information, which sets up the internal oscillator, reset operation,
etc. Perhaps the other compiler did that automatically?
Joel
On Wed, 22 Jan 2014, it would appear that Ael Gain wrote:
> Thanks for your quick answer!
>
> A
A google search for "z-80 disassembler" yields a number of
possibilities. You'll have to look through the results to see
which ones can take input in intel hex format.
Joel
On Fri, 29 Mar 2013, it would appear that Richard Gray wrote:
> Hi Folks,
>
> I have a ROM image from a Z80-based board in
compile for pic32)
>
> I found it's easier to build a stack from scratch with inspirations from other
> codes.
>
> At least that's my experience.
>
> Best regards
> Sebastien
>
> Le 29/03/2013 15:47, Joel Davidson a ?crit :
>> Luis-
>>
>> Does Mi
Luis-
Does Microchip have any libraries available on their website that
would provide the functionality you need? It's been a while since
I've done much pic assembly programming, but I was under the
impression that gpasm could compile mplab code pretty easily. Of
course I may be totally wrong o
ar to be working here.
Sorry for the bother, and thanks for the suggestions and pointers with
respect to my interrupt save/restore confusion.
Joel
--
Joel Davidson
Austin, TX
j...@prismnet.com
--
Live Security
ole of the problem in the interrupt code though,
as changing this doesn't resolve the hang issue.
I'm running from the most current code base, revision 8053, on
Fedora fc15.i686.PAE.
Any help or pointers as to what I may be doing wrong would be
appreciated. Thanks.
Joel
--
Joel Da
yet, or is there something
>> else going on here?
>
> The PIC backends are usually useable, though they are not as mature as
> most other backends.
>
> Best regards
> Raphael
Raphael-
I rebuilt sdcc as you s
nt
I've rebuilt the .c and .h files with inc2h.pl, and was seeing the same
warnings when I ran with sdcc installed from a binary using yum.
Is the pic support really not ready to go yet, or is there something
else going on here?
Thanks for any help y'all can provide.
11 matches
Mail list logo
