Hi
I have started on my arm32 emulator. Since I had problems with calling outside world from assembler, I start with pure c/c++. It is dead slow , but one thing is really promising. The code runs twice as fast on hw than on linux (same cpu) and in hw case the cpu is running on half speed.
Now on to my question: I need to get my executable (32 bit binary) into a ds. Do I need to do read() / copy everything in or is there some magic bits I can use?
Michael
On Thu, 12 Nov 2020 at 12:10, Michael Grunditz michael.grunditz@gmail.com wrote:
Hi
I have started on my arm32 emulator. Since I had problems with calling outside world from assembler, I start with pure c/c++. It is dead slow , but one thing is really promising. The code runs twice as fast on hw than on linux (same cpu) and in hw case the cpu is running on half speed.
Now on to my question: I need to get my executable (32 bit binary) into a ds. Do I need to do read() / copy everything in or is there some magic bits I can use?
Code actually runs 5x speed on hw, typo in mail.
Hi Michael,
On 12.11.20 13:10, Michael Grunditz wrote:
Now on to my question: I need to get my executable (32 bit binary) into a ds. Do I need to do read() / copy everything in or is there some magic bits I can use?
we usually use ROM modules for that, which can either be provided as boot modules or by a ROM server.
Given the 32-bit binary supplied as boot module, your program would request a ROM session with the name of the boot module as label and obtain the dataspace with the content via 'Rom_session::dataspace'. You may also have a look at 'Attached_rom_dataspace', which is a convenient wrapper around the lower-level mechanisms.
Cheers Norman
-
Michael Grunditz -
Norman Feske