Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Re: about masm 6.11
The ML.EXE itself has its command line options described at
hxxp://www.geocities.com/riskyfriends/x86/assembly/masm/Masm1.htm.
Moreover, if you are interested in MS manual itself - mainly for DOS programming -, its copy is available at...
IMHO, the cause of troubles have to be somewhere else. Just for fun I have tried to place #pragmas ASM/ENDASM with "your code" inside some C code (also I let Keil to generate and assemble SRC) and see listing:
531 ; #pragma asm
532 ; ADD A,#03h...
jhbbunch, I really do not know, why you evaluate the the intention or code instead of providing your answers. The kukurigu's question is completely legal whatever intention is behind it. By the way, offsetof() macro is a part of standard system headers of C compilers and some interesting details...
To keep it simple, I usually start from SRC compiler directive of Keil. I write a skeleton of function and let Keil help me to create a skeleton in ASM itself. Afterwards I include asm file with full instead of previous .C file and let .H as it is.
Sometimes I only write whole C function and...
It is hard ot calculate it by hand, because alingment is compiler dependent (at least in x86 world). But to make it automagically, you could use an idea from stddef.h of DJGPP:
#define offsetof(s_type, mbr) ((size_t) &((s_type *)0)->mbr).
The rest is and easy calculation.
Hope it helps,
Jan
If you need some detailed info about I2C, please, look into application notes on the Silabs (Cygnal) site. Few moths ago, I wrote some 8051F01x I2C code based on these documents.
As I remembered, l also googled some nice document made by Michrochip which includes waveforms, detailed...
Maybe simple question can give you an answer. Are you able calculate delay between code execution and real change on target pin for AVR processor? I am able to do it only in a very few moments, not in general.
Maybe it s my fault, maybe it is a pure AVR feature. But nowadays I can imagine...
This information is not valid - at least in general -, because '51 chips can be 10mA or even more (for example Cygnals or Philips LP9xx families).
From my personal experiences I would not use AVR, because I can not accept its behaviour on pins (but core itself seems fine to me). Also I could...
Not sure, whether you use evaluation or paid version of Keil, but just in case you use the evaluation version, do not be surprise, when any of your code for *2051 will not be working on real gadget.
The problem is, that the free version places generated code behind the code memory, which is...
To be more precise, voltage to frequency ratio should be kept constant for precise control. But do not forget, that all theory is not about voltage across motor terminals and for example determining of internal "resistors" in real time is almost nightmare thanks to their relation to temperature...
Their chips are fine and their JTAG system is something special. EC2 JTAG is cheap and does not disturb chips in operation. Newer USB JTAG is even cheaper. Personally, I am using the smallest ones (F304), MCU with USB (F320) and the fastest one (F122) and the only problem is a price. If I need...
8 bit declaration
As far as I know, sizeof(char) == sizeof(unsigned char) == 1 Byte. It is directly stated somewhere in C language norm, where - if I remember it correctly - char/uchar is the only type defined by its size. (Another types are defined with the help of "<=" and/or "==".)
From it...
From Keil manual about printf():
"This function is implementation-specific and is based on the operation of the _getkey and putchar functions. These functions, as provided in the standard library, read and write characters using the microcontroller's serial port. Custom functions may use other...
IMHO, "code const unsigned char sintable[0x100]" does not help you at all (but it is more appropriate C style for segment CODE) if you have "wrong intention of using the sintable[]". The problem is not in this line as long as you would try to do for example "something = sintable[0x01];" only...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
