x86 code and data location

[polarized]

Hello,

I have a question regarding the old DOS x86 Borland C compiler. Is it possible to configure the MAP file? The MAP file shows the code and data segments of the generated .EXE file. It is possible to choose the memory model tiny, compact, huge, etc... but not to configure the MAP file, as I understand it. I plan to generate a 16-bit real x86 embedded application with this compiler in a already defined memory space. Is it possible to use some kind of software which will load the .EXE file and the MAP file and produce the same program, but in a different memory space, or to configure the MAP file inside of the compiler or linker itself?


Bye.

 

[artem]

I do not know much about the content , may be can give some points :
The file Borland produces is about executable file format for DOS . It should have some tables to instruct
how the program will be loaded into the memory and how the relocateable memory will be addressed .
So you can use exe file only under DOS , or if you will design program loader which understands file format .
For embedded system design there such programs called locator which can produce binary executable in absolute adderessable format - image of the file in memory at predefined address . Most probably these programs can give you chance to configure the memory space layout and so on . Otherwise you need something like exe loader which simulates DOS .
There are some projects related to free DOS system . . Also I suppose the MAP file shold be generated by linker whichc resolves references , may be you can find something in linker settings .

 

[tom324]

I plan to generate a 16-bit real x86 embedded application with this compiler in a already defined memory space.

You need compiler and linker/locator for embedded systems to do that. The one I use is CADUL it _was_ available for x86 REAL and PROTECTED mode. Thn INTEL bought it (Cadul) and closed the project. Maybe the Cadul toolchain can be found on some FTP.

Tom

 

[bunalmis]

I live same problem for embeded system.

I solve it by my idea and i didnt see any problem.

I compile the C source using tcc and I produced asm source.
I defined the data, code and stack segment in the asm source.
I defined all segment register in the top of asm program.
I compile this asm source using tasm and produced eprom file.

 

[tom324]

bunalmis,

That is doing the job of Linker & Locator manually. The approach you suggest is a hard way to do the job. Toolchains like Cadul have IDE and Debugger what makes a life of embedded programmer easier.

Tom

 

[elcielo]

location tool for X86

CAD-UL **broken link removed** - maybe closed ???

paradigm c++ https://www.devtools.com/



free location tool

romize

**broken link removed**

 

[Lak]

Another better free rommable tool is UNILOC v2.2 ..
Supports floating point (emulation) and large data
Will create libs for small,...huge for Borland C only.
Do a google search ..german website ..186 etc

Cannot find it pm me.

..lak

 

[rtos]

check out the free version (8Kb code limit) of turbo locator for Turbo C/Pascal.

http://www.xellsoft.com/TurboLocator.html