On March 5, 2009 06:06:26 pm Peter Townson wrote:
> Lucas,
> Actually upon reflection I do have a suggestion:
> Maybe there should be a challenge issued (all in fun) to the subscribers of
> this list to post 'reference' examples - complete with schematics if
> external devices are involved - to
On Thursday 05 March 2009 06:06:26 pm Peter Townson wrote:
> Lucas,
>
> While I agree that I'd also like to see documentation for adc, i2c and
> serial communications etc, these are applications specific to individual
> micro-processors and related peripherals - they are NOT generic and most
> cert
2009/3/5 Frieder Ferlemann
> Hi Matt,
>
> Matt Baker schrieb:
> > With sdcc -mz80 test.c I get
> > at 1: error 131: cannot generate code for target 'z80'
>
> >>> *"sdcc --version *reports
> >>> SDCC : avr/pic16/pic14/xa51 2.8.0 #5117 (Jun 2 2008) (UNIX)
>
> The SDCC you are using had been compil
Peter Townson,
I understand that routines for adc, i2c and serial communications etc are
individual micro-processors. My work is 100% with Microchip, but I worked
few months for Freescale Semiconductors. I also agree that documentation for
these routines shouldn’t be part of the documentation of t
Lucas,
While I agree that I'd also like to see documentation for adc, i2c and serial
communications etc, these are applications specific to individual
micro-processors and related peripherals - they are NOT generic and most
certainly NOT part of the documentation for the compiler - any compiler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
candida lopez rodriguez schrieb:
>
> I tried to add a new section (z80 port and nothing)
>
> Thanks
The new section you created is there. I added a bit of information;
however I don't know about the situation with other ports, so it could
be that t
