>>> There really doesn't seem to be much of a point; GCC's AVR support is
>>> very good these days.
>>
>> True, however sad it may be.
>
> It's sad that GCC supports AVR?
No, the first part, i.e. that that killed avr-sdcc.
What a thoroughly odd thing to say.
>> it's easier to
>> learn to l
> There really doesn't seem to be much of a point; GCC's AVR support is
>very good these days.
True, however sad it may be.
SDCC certainly has potential to support 8-bitters much better than gcc, but
it's unlikely anybody will invest into the avr branch now - it's easier to
learn to live with th
Please read chapter 3.4.1.7 of SDCC manual for the __sbit syntax in SDCC.
However, the port bits are included in the device headers, so you can do
e.g. the following:
#include <8051.h>
#define RELAY P1_4
#define K1P2_7
void main(void) {
if (!K1) RELAY = 0;
else RELAY = 1;
}
JW
>First hit on Google search:
>
>http://www.keil.com/dd/docs/datashts/philips/lpc9408_ds.pdf
That's the datasheet.
Confusingly maybe, Philips/NXP uses the two-document scheme: datasheet
(description of electrical, mechanical and sometimes part-specific
properties) + (user) manual (functional desc
"The P89LPC9408 is a multi-chip module consisting of a P89LPC938 single-chip
microcontroller combined with a PCF8576D universal LCD controller"
Can't the two respective constituents' manuals be used, then?
JW
>
>Has anybody here the usermanual for the p89lpc9408 ?
>And willing to share :-)
---
During the years I came across chips designated 65C02 which did not have the
bit manipulation etc. "new" instructions. Clearly, there were several
second-sourcing companies, some of them might have chosen to designate a
6502-like design as "C" simply to stress the CMOS technology.
Also, accordi
Isn't the HC08 be similar enough to 6502?
Also, as a remark, the 6502 has a derivative, the 65C02; of which there also
exists variants with "secret" (more or less officially supported) instructions.
It might be also interesting to find out whether WDC
(http://www.westerndesigncenter.com/wdc/ )
What I would perhaps do, rather than juggle with the names, I'd place the
binaries for every target into a separate subdirectory.
Jan
- Original Message ---
>Hi Gerard,
>
>Right, something like this (I left out packihx):
>
>
>libs = file1 file2 file3
>
>all: target1.hex target2.h
worst case execution.
Jan Waclawek
- Original Message ---
>I want to calculate the maximum execution time of a ISR and so estimate the
>minimum frequency required for the microcontroller.
>
>Does anybody know any software tool to calculate the maximum executi
While this is absolutely true, there is at least one '51 derivative - the
Ramtron Versa - which has implemented an indirect SFR addressing mechanism as a
nonstandard extension.
Jan Waclawek
- Original Message ---
>It's not a question of the compiler. It is
Have a look at sdcc.sf.net->wiki->SDCC internals and porting->compilation flow.
It's sketchy but maybe will help a bit.
Jan Waclawek
- Original Message ---
>--90e6ba53a710c75c2804a164600b
>Content-Type: text/plain; charset=ISO-8859-1
>
>Hi All,
> Yep, I remember the HITECH-C debacle all too well.
Just to remind, Keil is an ARM company for quite some time, whatever that might
mean.
JW
--
Free Software Download: Index, Search & Analyze Logs and other IT data i
What happens if you set both buffers to [1]?
JW
- Original Message ---
>I have an in- and out-buffer of 64 bytes that should fit in the near =
>ram, but it gets a linker error of:
> link-Error-Could not get 128 consecutive bytes in internal RAM =
>for area ISEG.
--
uld you want to have a C compiler for a chip which is out of fashion for
about 3 decades?
Jan Waclawek
- Original Message ---
Subject: [Sdcc-user] 8048 support ?
From: Gert van der Knokke
Date: Tue, 25 Jan 2011 18:51:16 +0100
To: sdcc-user@lists.sourceforge.net
>
It's okay now, thanks.
Jan
- Original Message ---
>Jan,
>
>Please refresh the page in your browser. There is a new
>snapshot already.
>
>Maarten
>
>> http://sdcc.sourceforge.net/snap.php appears not to be updated since Jan 10
>> (6092).
>>
>> JW
>
--
http://sdcc.sourceforge.net/snap.php appears not to be updated since Jan 10
(6092).
JW
--
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malwar
hole
chain. Okay, the usual problem: I don't have that time...
Jan Waclawek
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spe
> I would like to use SDCC in my project and the MCU of my board is
>AVR(ATmega8).
> I notice that the avr branch and z80 branch would not be maintained.
> But how is the quality of code generated by avr branch now?
Critically bad :-)
The AVR branch was abandoned before getting i
> to save spacetime, XMing may be interesting:
http://sourceforge.net/projects/xming/
Interesting indeed. Thanks.
> However, ddd does not seem to exist for mingw/msys, or I missed it :(
That's the point, unfortunately.
I am a pure dumb user and absolutely unable to build anything including ddd
o
p/down or left/right to see everything. Don't know how to redirect IO. Some
commands make the whole stuff crash; the aftermath is that you need to inspect
in TaskManager within processes if s51 (and sdcdb itself) are not still run
A minimal example demonstrating the error:
#include
void f1 (uint16_t a, __xdata uint8_t b) {
a = b;
}
volatile uint8_t p, q;
void main(void) {
f1(p + 0x1234, q);
}
JW
--
_
r in xdata, and the
mechanism for that, as you've noticed, breaks the first parameter in dptr; so
I'd say you might be able to work this around by passing the second parameter
without the __xdata qualifier (eating up potentially direct adressable __data
space, though).
Jan Waclawek
Well, I am not the most qualified to answer, but SDCC's linker is not
scriptable as you might been used to.
For code/data segments [re]location you might want to look at the hints in
http://sdcc.sourceforge.net/doc/sdccman.html/node48.html .
Jan Waclawek
>I'm working on a boot
Borut,
>Sorry for a lost day
No, that's a misunderstanding. All I wanted to say was that the testing cycle
consisted of going to the place with XP machine in the morning, spending maybe
10 minutes with compiling the patched version, then in the evening test it on
the W9x machine which I use for
Borut,
On a WXP machine, I've patched sdld.c to printf path and progname, compiled
with gcc under cygwin, and run it on the W98 (the two machines are physically
remote and this cycle takes me a whole day :-( ).
The result is:
C:\WEK\51\sbc\sdcc\snake>sdcc test.c -o test.ihx -V --verbose
sdcc:
Interestingly enough, sdcc test.c -o test.ihx compiles OK.
JW
- Original Message ---
>... but fails to build test.c (the minimal program) - you apparently have
>built in a catch to the linker, haven't you ;-)
>
>C:\>sdcc --verbose test.c
>sdcc: Calling preprocessor...
>sdcc: Gen
... but fails to build test.c (the minimal program) - you apparently have built
in a catch to the linker, haven't you ;-)
C:\>sdcc --verbose test.c
sdcc: Calling preprocessor...
sdcc: Generating code...
sdcc: Calling assembler...
sdcc: Calling linker...
Assertion failed: str != NULL, file /home/
Installed flawlessly.
Thanks
Jan
- Original Message ---
>Can you try to install sdcc-20100207-5677-setup.exe and see if it
>uncompress correctly?
>On my machine is OK.
--
The Planet: dedicated and mana
C:\>sdcc -V test.c
+ C:\PROGRA~1\SDCC\BIN\SDCPP.EXE -nostdinc -Wall -obj-ext=.rel -DSDCC_MODEL_SMAL
L -DSDCC_FLOAT_REENT -DSDCC=297 -DSDCC_REVISION=5664 -DSDCC_mcs51 -D__mcs51 -isy
stem "C:\PROGRA~1\SDCC\BIN\..\include\mcs51" -isystem "C:\PROGRA~1\SDCC\BIN\..\i
nclude" "test.c"
+ C:\PROGRA~1\SDCC\
OK, I think I spotted the problem.
In sdld.c/sdld_init(), a target autodetection is performed, relying on argv[0]
(passed from the caller, main()). Internet said, that COMMAND.COM mangles
argv[0] - I don't know the exact details but I'd say it encloses it into
double-quotes) (this might be also
So, is this (the unexpected warnings) a Win98-specific problem?
Are there any substantial system calls involved in deciphering the capabilities
of the linker (which would lead to rejection of them)? That sounds strange.
And, also, is the installer problem Win98-specific?
So far, I had no proble
:
>
>SDCC : mcs51/gbz80/z80/ds390/pic16/pic14/TININative/ds400/hc08 2.9.7
>#5672 (Feb 5 2010) (MINGW32)
>
>and it works. The .mem file is generated too.
>
>Can you please confirm it?
>
>Borut
>
>
>Jan Waclawek wrote:
>> (the subject slightly lies - as I expl
This one has consequences:
> Unkown option -y ignored
And, indeed, the .mem file is missing.
JW
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the
nybody could shed light on these messages?
Thanks
Jan Waclawek
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choo
or the previous snapshot 5672.
Snapshot 5664 installed fine. I did not try those in between.
This is a Win98SE machine.
Jan Waclawek
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online
(0xA0) contents.
Jan Waclawek
- Original Message -
>The chip has dual DPTRs but no
> P2 nor XPAGE.
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data cent
n the selected processor): [...] 'data' [...].
Compliant equivalents of these keywords are always available in a form that
begin with two underscores, f.e. '__data' instead of 'data'."
Jan Waclawek
- Original Message ---
Subject: [Sdcc-user]
Oh, the quality of NXP documentation on the '51 derivatives is decaying, to
be very polite...
You must first enable the boot ROM (which is otherwise "hidden" to allow
full 64kB of FLASH code space). Yes, NXP "forgot" to put this small piece of
information into the datasheet.
See for example http:/
t's why the syntax is quite
different from the standard Intel-like syntax as most of the '51 assemblers out
there use (in a multiple of modifications). And also that's why the
documentation mentions the '51 only in the appendix.
Jan Waclawek
---
incrementally. What we have discussed now, should maybe go under "SDCC
Tutorials" or something similar.
Feel free to contribute. Anything.
Jan Waclawek
-
This SF.Net email is sponsored by the Moblin Your Move Developer&#
ightforward and crystal clear, and which were complex and obscure - and, of
course, it's exactly the opposite of what you thought BACK THEN when the
documentation was written... :-)
Jan Waclawek
-
This SF.Net email is
Richard,
it's a switch you use when you invoke SDCC with intention to redirect its
output to a file.
If you type:
C:>sdcc blinkey.c > blinkey.out
all the output of sdcc will go to the console window, and blinkey.out will have
size of 0 bytes.
If you type
C:>sdcc --use-stdout blinkey.c > blinkey
> > Under W9x, for me it was a challenge to find the --use-stdout switch as
> > the "dosbox" there has no "scrollback" feature, and without this switch
> > it's impossible to redirect the output into a file. This is not an issue
> > under WXP as you can scroll back the "dosbox".
> >
> Couldn't y
Richard,
>Maybe a few words would be helpful about what makes one editor more
>"suitable" than another, or what might make it less-suitable. A few
>suggestions as to "convenient" features might be helpful in this context,
>too.
Well, this is not really SDCC-specific...
I don't feel competen
Richard,
Although I am not competent to decide on this either, I don't think Daniel's
simulator goes as far as peripherals timing (in ns).
And, IMHO, there is not too much "buying drive" to make such a sophisticated
simulator either. Some of the '51 simulations are done in the clock domain,
mo
Richard,
>I have a 'C' program, which I hope will work, on paper in my hand ...
Yeah, the BBC (bare-brain-computer). ;-)
>There's a computer running Windows on the desk in front of me. I want to
>compile this program for introduction by whatever means might be available
>into a system based
ment within which the simulator has to
>function. Handwaves don't help, either. Some things have to be clearly
>defined, at least in terms of inputs, outputs, and processes.
I don't quite understand what do you mean by this.
I think, a step-by-step quickstart example on a tr
Daniel,
>Anyway, I think simulator should simulate only, and GUI should provide
>easy_to_use functionality. They can and should be different tools,
>working together of course.
>
I disagree.
IMHO, they _can_ be different tools, but they _don't_need_ to be different
tools.
I, as a _user_, d
or me than the other
features which are important for you or for the SDCC developers.
Szep napot!
Jan Waclawek
>> There _is_ a '51 simulator which comes with SDCC, but it is rather
>> cumbersome to use and has a command-line interface only (read: command line,
>> no text-scre
to use and has a command-line interface only (read: command line,
no text-screen). It is not intended to be used by human, rather, in an
automated simulation setup (primarily for the regression testing after a new
build of SDCC).
Jan Waclawek
---
Reminds me of a couple of my favourite threads on 8052.com:
http://www.8052.com/forum/thread.phtml?thread=130415
http://www.8052.com/forum/thread.phtml?thread=137677
So, the conclusion is, everything clear, so it's now just simple coding,
that's all... :-)
Jan Waclawek
PS. Berwyn,
I am considering to submit a feature request for passing more parameters in
registers for the x51 target; but before I ridicule myself completely, is
there any substantial reason why not to do so?
Jan Waclawek
-
This
#define putchar PUTCHAR
You want to do it the other way round.
This line tells the preprocessor to replace all occurences of "putchar" string
in the sources by "PUTCHAR" string; but assuming you don't have linked the
SOURCES of (any)printf, (rather, you used the precompiled library) there is n
My rants have been heard... Now I can have broadband internet installed
easily even in my house!
http://www.google.com/tisp/
Happy 1st April to everybody!
Jan Waclawek
(PS. Sorry for the OT)
-
Take Surveys. Earn Cash
Bah, my bad, thinking faster than writing... Here comes the errata on my
previous mail:
> And this STUPID STUPID STUPID world, including the OS community, simply
> assumes that ...
... everybody sits on a permanent fat internet connection, being able to
download anything on demand instantaneously.
> IMO you're not supposed to do anything, but help sure is
> welcome. The SDCC manual is written using LYX. If you
> use 1.4 be sure to save as backward compatible with 1.3.
> The file to change is sdccman.lyx in the doc directory
> of the source tree. After updating you can create a
> patch file (
Maarten,
thanks a lot.
Jan
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn c
Maarten,
> > On a similar note, chapter 3.12 says on labels in inline assembler, that
"In
> > older versions of the compiler all labels defined within inline
assembler
> > code had to be of the form n$ where is a number less than 100
> > (which implies a limit of utmost 100 inline assembl
Maarten,
Thank you very much for your valuable comments. I was looking at _your_
library functions at the moment... :-)
> > - in assembler functions, either inline or externally linked, the
assumption
> > is, that no register may be trashed. Correct?
>
> This is correct for naked functions or inl
ined within inline assembler
code had to be of the form n$ where is a number less than 100
(which implies a limit of utmost 100 inline assembler labels per function)."
OK, which is "older versions of compiler" and assuming I have
> 2. warning 59 : conditional flow changed by optimizer.
What, no "said Evelyn, the modified dog"???
You have written something, which the compiler's optimizer thought does
more-less nothing and will be better to throw off. This is OK from the point of
view of compiler; but for you this may ind
Congratulations, and many many thanks!
Jan Waclawek
- Original Message -
From: Borut Razem <[EMAIL PROTECTED]>
> SDCC users and developers,
>
> 3 months after the SourceForge Compile Farm has been discontinued (see
> https://sourceforge.net/forum/forum.php?forum_id
Abishek,
I answered the same question you posted in the Open Forum.
The problem is that you need to append "0x" prefix to hexadecimal constants.
wek
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net'
And is there any "standard" way how to pass a keyword from C-source down to
the linker?
Is there *any* way to do it?
Jan Waclawek
> Hi Jan,
>
> Unfortunately that is of no use currently. As long as
> the linker does not handle .even directives there's no
> point
Oh yes, I almost forgot.
My quick fix (with zero overhead) for the problem was to include the
following line to any branch of the "if".
*px += 0;
I don't know why it works so I don't know if this is an ultimate quickfix
just tried and have seen in asm the result is OK.
JW
--
The absolute segment solution is not exactly what the .even directive does
in asm.
Would there be any problem with having an another non-standard keyword for
this in C?
I know there is none such at the moment, I am just asking...
Jan Waclawek
> Have a look in this forum thread:
>
nt "if" so that the "if" condition is false, but cannot reproduce this
behaviour in a simple program presentable here.
Jan Waclawek
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge
SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08
2.6.1 #4478 (Nov 23 2006) (MINGW32)
When compiling the following snippet for mcs51, both *px translates to
mov dptr,#_x
movx a,@dptr
i.e. *x, which may not be true.
Is this an error or just me being stupid?
Jan Waclawek
Maarten,
Actually, I sent this mail to the -devel maillist first, but it requires
confirmation which I think is far from being flexible enough... Also, the
-devel maillist is full of buglist notice, it's hard to find anything
reasonable there, especially considering the rather broken interface
stions, although I might be too
stupid to ask the right questions - please help me out if needed.
Thanks
Jan Waclawek
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'
70 matches
Mail list logo
