Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
(27) |
Apr
(107) |
May
(32) |
Jun
(45) |
Jul
(79) |
Aug
(61) |
Sep
(94) |
Oct
(89) |
Nov
(133) |
Dec
(45) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(81) |
Feb
(57) |
Mar
(85) |
Apr
(80) |
May
(79) |
Jun
(85) |
Jul
(97) |
Aug
(104) |
Sep
(60) |
Oct
(82) |
Nov
(49) |
Dec
(57) |
2002 |
Jan
(46) |
Feb
(80) |
Mar
(112) |
Apr
(93) |
May
(72) |
Jun
(89) |
Jul
(118) |
Aug
(130) |
Sep
(67) |
Oct
(49) |
Nov
(58) |
Dec
(99) |
2003 |
Jan
(281) |
Feb
(141) |
Mar
(231) |
Apr
(109) |
May
(128) |
Jun
(166) |
Jul
(243) |
Aug
(64) |
Sep
(44) |
Oct
(67) |
Nov
(70) |
Dec
(68) |
2004 |
Jan
(71) |
Feb
(88) |
Mar
(60) |
Apr
(84) |
May
(79) |
Jun
(168) |
Jul
(92) |
Aug
(72) |
Sep
(51) |
Oct
(102) |
Nov
(35) |
Dec
(73) |
2005 |
Jan
(65) |
Feb
(48) |
Mar
(86) |
Apr
(64) |
May
(107) |
Jun
(93) |
Jul
(40) |
Aug
(117) |
Sep
(82) |
Oct
(65) |
Nov
(63) |
Dec
(85) |
2006 |
Jan
(36) |
Feb
(81) |
Mar
(74) |
Apr
(131) |
May
(92) |
Jun
(71) |
Jul
(71) |
Aug
(54) |
Sep
(26) |
Oct
(77) |
Nov
(55) |
Dec
(55) |
2007 |
Jan
(112) |
Feb
(88) |
Mar
(105) |
Apr
(46) |
May
(28) |
Jun
(53) |
Jul
(29) |
Aug
(34) |
Sep
(74) |
Oct
(83) |
Nov
(67) |
Dec
(39) |
2008 |
Jan
(40) |
Feb
(105) |
Mar
(42) |
Apr
(25) |
May
(91) |
Jun
(32) |
Jul
(47) |
Aug
(128) |
Sep
(188) |
Oct
(54) |
Nov
(19) |
Dec
(41) |
2009 |
Jan
(145) |
Feb
(88) |
Mar
(117) |
Apr
(38) |
May
(53) |
Jun
(9) |
Jul
(47) |
Aug
(10) |
Sep
(28) |
Oct
(65) |
Nov
(97) |
Dec
(36) |
2010 |
Jan
(55) |
Feb
(87) |
Mar
(81) |
Apr
(30) |
May
(37) |
Jun
(15) |
Jul
(85) |
Aug
(31) |
Sep
(1) |
Oct
(69) |
Nov
(69) |
Dec
(32) |
2011 |
Jan
(37) |
Feb
(49) |
Mar
(55) |
Apr
(27) |
May
(67) |
Jun
(30) |
Jul
(43) |
Aug
(73) |
Sep
(65) |
Oct
(89) |
Nov
(59) |
Dec
(15) |
2012 |
Jan
(27) |
Feb
(48) |
Mar
(14) |
Apr
(18) |
May
(38) |
Jun
(59) |
Jul
(46) |
Aug
(11) |
Sep
(21) |
Oct
(28) |
Nov
(18) |
Dec
(51) |
2013 |
Jan
(35) |
Feb
(68) |
Mar
(56) |
Apr
(21) |
May
(62) |
Jun
(43) |
Jul
(12) |
Aug
(34) |
Sep
(28) |
Oct
|
Nov
(11) |
Dec
(33) |
2014 |
Jan
(15) |
Feb
(36) |
Mar
(33) |
Apr
(45) |
May
(8) |
Jun
(52) |
Jul
(30) |
Aug
(7) |
Sep
(38) |
Oct
(76) |
Nov
(19) |
Dec
(26) |
2015 |
Jan
(67) |
Feb
(42) |
Mar
(6) |
Apr
(12) |
May
(13) |
Jun
(17) |
Jul
(10) |
Aug
(9) |
Sep
(26) |
Oct
(24) |
Nov
(8) |
Dec
(2) |
2016 |
Jan
(19) |
Feb
(2) |
Mar
(33) |
Apr
(56) |
May
(10) |
Jun
(12) |
Jul
(38) |
Aug
(69) |
Sep
(10) |
Oct
(7) |
Nov
(20) |
Dec
(26) |
2017 |
Jan
(10) |
Feb
(10) |
Mar
(4) |
Apr
(4) |
May
(16) |
Jun
(13) |
Jul
(16) |
Aug
(25) |
Sep
|
Oct
(28) |
Nov
|
Dec
(1) |
2018 |
Jan
(31) |
Feb
(24) |
Mar
(38) |
Apr
(18) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
|
|
1
|
2
(1) |
3
(5) |
4
(4) |
5
|
6
(5) |
7
(3) |
8
(1) |
9
(1) |
10
(4) |
11
(5) |
12
|
13
(1) |
14
(1) |
15
(1) |
16
(1) |
17
(5) |
18
(13) |
19
(11) |
20
(2) |
21
|
22
(12) |
23
(1) |
24
(2) |
25
(3) |
26
(1) |
27
(2) |
28
(4) |
29
(1) |
30
(1) |
31
|
From: Maarten Brock <sourceforge.brock@ds...> - 2008-05-17 13:46:47
|
You need to recompile the library, esp. printf_large.c with -DUSE_FLOAT=1, not your own code. One option is to only recompile printf_large.c and explicitly link it. > Hi, > > I have tried some Google magic and read related webpages; still it's not > clear to me if SDCC support floating point variables for DS89C450 . > In my code I try to use sprintf() and atof(), both compiles fine. Still > when I run it, I get 'NO FLOAT' messages. I even tried -DUSE_FLOAT=1 for > compiling my code. What do I miss? How can I turn on floating point > variable handling in SDCC for DS89C450? > > Thanks for any pointers, > Laszlo/GCS > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sdcc-user mailing list > Sdcc-user@... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > |
From: Philippe Latu <philippe.latu@li...> - 2008-05-17 13:44:18
|
Hello, Le samedi 17 mai 2008, Laszlo Boszormenyi a écrit : > Hi, > > I have tried some Google magic and read related webpages; still it's not > clear to me if SDCC support floating point variables for DS89C450 . > In my code I try to use sprintf() and atof(), both compiles fine. Still > when I run it, I get 'NO FLOAT' messages. I even tried -DUSE_FLOAT=1 for > compiling my code. What do I miss? How can I turn on floating point > variable handling in SDCC for DS89C450? As I am not using the same device, I may be wrong, but for MSC1210 I usually edit the source file 'device/lib/printf_large.c' and comment out the SDCC_ds390 definition to force USE_FLOATS in any case. #if defined (SDCC_ds390) #define USE_FLOATS 1 #endif HTH, > > Thanks for any pointers, > Laszlo/GCS > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sdcc-user mailing list > Sdcc-user@... > https://lists.sourceforge.net/lists/listinfo/sdcc-user -- - Philippe Latu philippe.latu(at)linux-france.org http://www.linux-france.org/~platu (GPG|PGP) KeyId 0x742A6424 - http://www.linux-france.org/~platu/key.asc |
From: Laszlo Boszormenyi <gcs@ro...> - 2008-05-17 13:32:55
|
Hi, I have tried some Google magic and read related webpages; still it's not clear to me if SDCC support floating point variables for DS89C450 . In my code I try to use sprintf() and atof(), both compiles fine. Still when I run it, I get 'NO FLOAT' messages. I even tried -DUSE_FLOAT=1 for compiling my code. What do I miss? How can I turn on floating point variable handling in SDCC for DS89C450? Thanks for any pointers, Laszlo/GCS |
From: Maarten Brock <sourceforge.brock@ds...> - 2008-05-17 07:56:47
|
Hi Stephan, Once your application starts, does the pre-existing firmware still need some control too or is the whole device yours? In other words would it be ok if all memory got erased or not? Because that is basically what the startup code does: erase and initialize the memory and setup the stackpointer. All startup code can be seen in the manual btw. (3.11). And most of it can be skipped by returning nonzero from YOUR implementation of _sdcc_external_startup(). You'll probably need some assembly to set the bootvector at 0x8006. HTH, Maarten > I'm working on a project where I have a device based on an Atmel AT89C51 > > The device is set up as follows: > > 448K Flash, 512K SRAM > > The ram is divided into pages, 16kb each. > > In addition to all of this, there is already pre-existing firmware > running on the device. So not all internal / external ram is available > for my usage. > > Now at address 0x8000 they have something that resembles an interrupt > vector table, but the vectors are specific to the firmware already > running on the device. > > The vector at 0x8006 is the one primarily of interest to me as I need to > set that as my jump to my application code which can start at offset > 0x802F. > > Now I suppose I can just have sdcc compile with setting my code location > at 0x802F but I'm worried about all the SDCC specific startup code > conflicting with whatever the existing firmware on the device has done. > > Can anyone give me any advice on how to proceed here? I can try and give > more information if necessary. > > Thanks, > > Stephan > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sdcc-user mailing list > Sdcc-user@... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > |
From: Stephan Rose <stephan@ec...> - 2008-05-17 03:41:42
|
I'm working on a project where I have a device based on an Atmel AT89C51 The device is set up as follows: 448K Flash, 512K SRAM The ram is divided into pages, 16kb each. In addition to all of this, there is already pre-existing firmware running on the device. So not all internal / external ram is available for my usage. Now at address 0x8000 they have something that resembles an interrupt vector table, but the vectors are specific to the firmware already running on the device. The vector at 0x8006 is the one primarily of interest to me as I need to set that as my jump to my application code which can start at offset 0x802F. Now I suppose I can just have sdcc compile with setting my code location at 0x802F but I'm worried about all the SDCC specific startup code conflicting with whatever the existing firmware on the device has done. Can anyone give me any advice on how to proceed here? I can try and give more information if necessary. Thanks, Stephan |