Hi Richard, Richard Erlacher schrieb: >>> simulator, as the company that owns/owned it no longer exists. >> Can you be more explicit? - which simulator? >> > TS Controls under the MIDE. There was a link in the SDCC context, so I > loaded it up. It works very nicely, AFAIK, but ... it only works if the > address range doesn't exceed 2048 bytes. I'd consider buying the thing, as > it supports those Maxim/Dallas parts that I like, but one can't do that. > There's a DOS-based simulator to which there's reference, also, but I've > never been able to find a working version of that. The link on SourceForge > apparently points off to nowhere (I havent looked lately ... maybe there was > just some temporary trouble).
sorry for that. > In fact, I've never been able to find a decipherable manual for SDCC and its > components. There is LOTS of info on how to install it, recompile it, etc, > but little about how to use it under Windows. There should not be much that is specific to Windows. The arguments on the command line should be pretty much the same. If you found: http://sdcc.sourceforge.net/doc/sdccman.pdf then currently that's about it. (*) SDCC's messages/warnings follow the format that GCC uses. So SDCC integrates well with editors that are meant to integrate compilers. There should be no problem to have a C file compiled by SDCC by pressing a specific function key and having it compiled by f.e. Keil by pressing another key. And in case of errors have the cursor of the editor positioned on the respective line (and eventually column). There are application notes discussing integration of SDCC with at least three editors (subsection 6.6). > Since I'm not really a big HLL fan for small (< 250kB) code bodies, this :) >> Somewhat ugly but would this do? >> > I don't follow ... The 805x versions that interest me currently are all > 1-clockers. I haven't been able to get information from Maxim/Dallas about > how timing of their UART works, considering that their parts are > one-clockers, particularly in Mode 0. I'm inclined to operate in complete > synchronization with the UART, and read/write the DBUF at the precise time My sample code clearly does not fit your needs!) > that next byte should become available in order to avoid a clock-stretch. > I'm not sure how this works out, but it takes a lot of effort to tease out > such internal details. AFAIK, no simulator gets down to the > bitwise/countwise details of the UART and timer/counters. (it might make sense to outcomment line 324 here: http://sdcc.svn.sourceforge.net/viewvc/sdcc/trunk/sdcc/sim/ucsim/s51.src/serial.cc?view=markup but it won't help you with single clockers) If you are down to single cycles on a single clocker you are most likely aware that for some of the single clockers you also have to tell the linker where to put your carefully timed code? The quicker single cycle devices may have a 16 or 32 bit wide (c8051f120 AFAIK) data path to their slow flash memory, so performance on odd/even addresses (or modulo 4 addresses) can differ. (Same might hold true for ENE kb3700 operating from slow SPI memory) Greetings, Frieder (*) There also is a wiki but so far it has seen _much_ less contributions than one could have hoped for. F.e. no tips and tricks for editors or IDEs. So no doubt everyone is happy and there are no problems. (sorry I could not resist). ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/sdcc-user
