Thanks, Maarten, that's good to know.  I've been using a macro assembler 
that came with an earlier version of SDCC, or, perhaps (I don't recall), was 
simply pointed to by one of the related sites.  It has a good help file 
which has saved me many an error, and it's part of the "MIDE" package, which 
includes a simulator and claims to hook up in some way to SDCC.  That may be 
why I made some possibly unwarranted assumptions about its relationship to 
SDCC.

regards,

Richard Erlacher

----- Original Message ----- 
From: "Maarten Brock" <[EMAIL PROTECTED]>
To: <sdcc-user@lists.sourceforge.net>
Sent: Thursday, August 28, 2008 12:15 PM
Subject: Re: [Sdcc-user] Virus in SDCC-2.8.0-setup.exe - MD5 etc tutorial


> Hi Richard,
>
>> Now, SDCC is a great concept if, for example, it's easy to integrate with 
>> an
>> assembler, a linker, a simulator, a librarian, and all the other 
>> utilities
>> that are helpful in developing code.
>
> SDCC for the 8051 only works with the assembler and linker that come
> with it, sorry. It needs a separate assembler and linker and AFAIK
> there is no other free/open source option available.
>
>> I just learned that the SiLabs
>> environment (IDE) without which it's apparently a pain to use their 
>> MCU's,
>> relies upon OMF files produced by SDCC tools, among others.  That's why 
>> I'm
>> taking another look.  The small bits of code I usually prepare for the
>> 805x-series (up to, say, 12k-15k lines of ASM) are generally monolithic,
>> hence, don't require the linker, etc.  Up to now, I've written code 
>> segments
>> and de-loused them separately, since the things I do, though sometimes
>> bigger than 8kB of object code, are seldom terribly complex.  After that, 
>> I
>> simply combine those portions of code as macros or as subroutines.
>
> Unfortunately the assembler that comes with SDCC does not support
> macros.

That's not a big deal, since the macros can be substituted/pasted into the 
code using an editor command, if necessary.

>But the assembler/linker combination can also output OMF
> files without being called by SDCC, and the SiLabs IDE can thus
> download and debug the output. The SiLabs IDE can download only HEX-
> files (which have no debug information) and OMF-files (which do). If
> your favourite assembler (with or without linker) can generate OMF
> files, the IDE should be able to load and debug them. The only real
> issue I can think of would be the endianness for displaying
> multibyte variables. Both big-endian and little-endian are supported
> so choose a compiler setting with compatible endianness.
>
> Hope this helps,
> Maarten Brock
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's 
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great 
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the 
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Sdcc-user mailing list
> Sdcc-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sdcc-user 


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user

Reply via email to