Yes, there are still problems on qemu 2.6.0 release candidate and 2.5.1 with same version of u-boot as mentioned and with latest stable u-boot release. When qemu has parameter -smp cores=2 or 3 or 4.
errors are:
qemu: fatal: Trying to execute code outside RAM or ROM at 0x31306c70
That adress changes but is mostly close to that example value ("8 digits" adress)
as mentioned in previous posted bugreport
Sometimes runing U-boot(?) hangs but I can exit qemu using keys Ctrl-a x
And that seems to be new behaviour.
- - - - - - - - - - - -
If someone is interested how to build u-boot for further testing of this issue on his own box
$ git clone git://git.denx.de/u-boot.git
$ cd u-boot
$ make vexpress_ca9x4_defconfig ARCH=arm CROSS_COMPILE=arm-none-eabi
$ make all_ca9x4_defconfig ARCH=arm CROSS_COMPILE=arm-none-eabi
Yes, there are still problems on qemu 2.6.0 release candidate and 2.5.1 with same version of u-boot as mentioned and with latest stable u-boot release. When qemu has parameter -smp cores=2 or 3 or 4.
errors are:
qemu: fatal: Trying to execute code outside RAM or ROM at 0x31306c70
That adress changes but is mostly close to that example value ("8 digits" adress)
as mentioned in previous posted bugreport
Sometimes runing U-boot(?) hangs but I can exit qemu using keys Ctrl-a x
And that seems to be new behaviour.
- - - - - - - - - - - -
If someone is interested how to build u-boot for further testing of this issue on his own box
$ git clone git://git. denx.de/ u-boot. git ca9x4_defconfig ARCH=arm CROSS_COMPILE= arm-none- eabi arm-none- eabi
$ cd u-boot
$ make vexpress_
$ make all_ca9x4_defconfig ARCH=arm CROSS_COMPILE=