Thanks for the report.
However, bugs posted to the mailing list have a tendency to be
forgotten, unless fixed quickly. I'd suggest to open a bug report at
https://sourceforge.net/p/sdcc/bugs/
to avoid that. Also, opening a bug report assigns a number to the bug,
which might be needed for the reg
Hello
I had this bug since 3.60, that's why I stayed back to 3.50 for a while.
I see 3.80 fixed some other bug I had, so I decided to send a report for this
one.
https://www.dropbox.com/s/zko66w2asxbboqa/test01.zip?dl=0
There is a place in my code (version that works or doesn't provided) wh
http://advantage.dramaticallycorrectdesigns.com
Michael Hawkins
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Hello SDCC friends,
Today the first Release Candidate (RC1) for SDCC 3.5.0 has been created.
As always it has been put online in our SourceForge File section.
https://sourceforge.net/projects/sdcc/files/
If you have the time, please verify it and report back with the positive
or negative results.
http://topspeedtechnology.com/wp-content/themes/TheProfessional/mylove.php?copy209.img
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security a
hello! http://208.109.196.29/bestpills.html?fyaolID=98ox
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
Sdcc-user mailing
Hi Jacques,
Jacques Pelletier schrieb:
> The crash was due to empty data record (length = 0 bytes). I´ve corrected the
> bug and made a new release of Hex2bin.
>
> Thanks!
Thanks and greetings,
Frieder
--
This SF.Net e
On December 6, 2009 07:06:33 pm Frieder Ferlemann wrote:
> Hi Caitlin,
>
> > try to run hex2bin and hex2bin crashes. The reason is that the ihx file
> > is not correct
>
> sorry I'm not aware of the context (and the subject of your mail
> seems to be lost).
>
> I tried to reproduce this with O
Thanks I will try this and see if my eeprom programmer likes the binary (or the
intel file)
Thanks again
> Date: Mon, 7 Dec 2009 01:06:33 +0100
> From: frieder.ferlem...@web.de
> To: sdcc-user@lists.sourceforge.net
> Subject: Re: [Sdcc-user] (no subject)
>
> Hi Caitlin,
&
Hi Caitlin,
caitilin lopez schrieb:
> I tried to submit a bug report and it said that I need to register. So I did.
>
>
> I did some more investigation about my issue (the compiler generates bad
> output). If I generate the assembly files then I use aslink in the assembly
> file the result i
I tried to submit a bug report and it said that I need to register. So I did.
I did some more investigation about my issue (the compiler generates bad
output). If I generate the assembly files then I use aslink in the assembly
file the result is correct. It seems is an issue with the linker.
Hi,
I'm suffering a rather strange (at least to me) error:
error: missing definition for symbol "_ADCON2", required by "main.o"
It seems to refer to the following command in the main() routine in
main.c, since when I remove this command the error is no longer
present.
ADCON2 =
George M. Gallant, Jr. wrote:
> On Wed, 2006-07-12 at 19:52 -0700, Mark Swayne wrote:
>> Try:
>>
>> #define XTAL 11059200
>> #define TICK_PERIOD20 /* 1/TIME_TICK */
>> #define RELOAD_VALUE -( XTAL/ (12 * PERIOD) )
>>
> Is this a typo ?
On Wed, 2006-07-12 at 19:52 -0700, Mark Swayne wrote:
Try:
#define XTAL 11059200
#define TICK_PERIOD20 /* 1/TIME_TICK */
#define RELOAD_VALUE -( XTAL/ (12 * PERIOD) )
Is this a typo ? ^^^
TL0
Try:
#define XTAL 11059200
#define TICK_PERIOD20 /* 1/TIME_TICK */
#define RELOAD_VALUE -( XTAL/ (12 * PERIOD) )
TL0 = ( unsigned char ) ( RELOAD_VALUE );
TH0 = ( unsigned char ) ( RELOAD_VALUE >> 8 );
or:
#define XTAL 11.0592e6
#define TIME_TICK50e-3
#def
Dear listers,
I have defined these macros:
...
#define XTAL 11.0592e6
#define TIME_TICK 50e-3
#define RELOAD_VALUE -( TIME_TICK * XTAL / 12 )
...
When I use statement like this:
...
TL0 = ( unsigned char ) ( RELOAD_VALUE );
TH0 = ( unsigned char ) ( RE
16 matches
Mail list logo
