From: U.Mutlu <for-gmane@mutluit.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] standalone app hello_world.bin crashes
Date: Thu, 11 Apr 2019 10:45:46 +0200 [thread overview]
Message-ID: <5CAEFEBA.1040408@mutluit.com> (raw)
# CC W.D., T.R.
I tried to run hello_world.bin (in examples/standalone)
on the target device, but it crashes with "undefined instruction".
I followed the steps in the doc at
https://www.denx.de/wiki/view/DULG/UBootStandalone.
The said example is generated together with u-boot itself;
u-boot works ok, but the example crashes:
=> fatload mmc 0 0x42000000 hello_world.bin ; go 0x42000000 a b c d
570 bytes read in 2 ms (278.3 KiB/s)
## Starting application at 0x42000000 ...
undefined instruction
pc : [<42000718>] lr : [<7ef7c633>]
reloc pc : [<0d086718>] lr : [<4a002633>]
sp : 7af51eb8 ip : 0000000c fp : 00000006
r10: 7af68c28 r9 : 7af59ed8 r8 : 7efd5154
r7 : 7ef8fa25 r6 : 00000006 r5 : 42000000 r4 : 7af68c2c
r3 : 42000000 r2 : 7af68c2c r1 : 7af68c2c r0 : 00000005
Flags: nzCv IRQs off FIQs off Mode SVC_32
Code: 35303753 30303234 31303030 0a0d3742 (ffffffff)
Resetting CPU ...
resetting ...
=> version
U-Boot 2019.04-00077-g48ff1bc4f0 (Apr 11 2019 - 07:40:39 +0200) Allwinner
Technology
arm-linux-gnueabihf-gcc (GCC) 9.0.1 20190326 (experimental) [trunk revision
269955]
GNU ld (GNU Binutils) 2.32.51.20190326
=> bdi
arch_number = 0x100010bb
boot_params = 0x40000100
DRAM bank = 0x00000000
-> start = 0x40000000
-> size = 0x40000000
baudrate = 115200 bps
TLB addr = 0x7eff0000
relocaddr = 0x7ef7a000
reloc off = 0x34f7a000
irq_sp = 0x7af52000
sp start = 0x7af51ff0
FB base = 0x7fb00000
Early malloc usage: 134 / 400
fdt_blob = 0x7af52018
root at xy:/.../u-boot/examples/standalone#
../../../TOOLCHAIN/bin/arm-linux-gnueabihf-nm -n hello_world
42000000 T hello_world
42000090 T dummy
42000090 T get_version
42000098 T getc
420000a0 T tstc
420000a8 T putc
420000b0 T puts
420000b8 T printf
420000c0 T install_hdlr
420000c8 T free_hdlr
420000d0 T malloc
420000d8 T free
420000e0 T udelay
420000e8 T get_timer
420000f0 T vprintf
420000f8 T do_reset
42000100 T env_get
42000108 T env_set
42000110 T simple_strtoul
42000118 T strict_strtoul
42000120 T simple_strtol
42000128 T strcmp
42000130 T i2c_write
42000138 T i2c_read
42000140 T spi_setup_slave
42000148 T spi_free_slave
42000150 T spi_claim_bus
42000158 T spi_release_bus
42000160 T spi_xfer
42000168 T ustrtoul
42000170 T ustrtoull
42000178 T strcpy
42000180 T mdelay
42000188 T memset
42000194 T app_startup
4201023a R __bss_end__
4201023a R _bss_end__
4201023a R __bss_start
4201023a R __bss_start__
4201023a R _edata
4201023c R _end
4201023c R __end__
--
U.Mutlu
reply other threads:[~2019-04-11 8:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5CAEFEBA.1040408@mutluit.com \
--to=for-gmane@mutluit.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.