On Thu, 30 Sept 2021 at 07:17, abhijeet inamdar
wrote:
>
> But this very ELF file runs on the target(real hardware) perfectly. So how
> different should it be to emulate?
Real hardware doesn't have a magic ELF file loader. The
details of what a debug environment or whatever mechanism
you're usin
Actually the ELF generates the .bin file which is being used to run on the
target (hardware). It's address starts from zero when I see the starting
frames of it. As follows:
IN:
0x0002: c0de stm r0!, {r1, r2, r3, r4, r6, r7}
0x0004: 0003 movs r3, r0
0x0006: 000
The above is when I load the .bin instead of ELF in the machine.
On Thu, Sep 30, 2021 at 1:33 PM abhijeet inamdar <
abhijeetinamdar3...@gmail.com> wrote:
> Actually the ELF generates the .bin file which is being used to run on the
> target (hardware). It's address starts from zero when I see the
On Thu, 30 Sept 2021 at 12:34, abhijeet inamdar
wrote:
> Actually the ELF generates the .bin file which is being used to run on the
> target (hardware). It's address starts from zero when I see the starting
> frames of it. As follows:
>
> IN:
> 0x0002: c0de stm r0!, {r1, r2, r3,
Hello, all
I'm install ubuntu 20.04 on an arm64 virtual machine using qemu-5.1.0. (host
is also ubuntu 20.04, am64 machine)
The final command is below. (the LD_LIBRARY_PATH setting was needed for
sudo)
sudo LD_LIBRARY_PATH=/home/ckim/prj/abdsn/ab21sim/axpusim/build
./qemu-system-aarch64 -nograph
Hi, qemu experts and users,
I tried the same install procedure below in my main ubuntu 20.04 machine
(intel).
And this time the DHCP network setting is successful. (I remember last time
it had no problem hence I'm doing experiments there..)
The dhcp setting problem during ubuntu install occu
