From: Junior <ejr@inbox.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] undefined instruction during bootp
Date: Tue, 15 May 2007 13:32:16 -0800 [thread overview]
Message-ID: <50C96E42594.00000616ejr@inbox.com> (raw)
In-Reply-To: <20070515211216.9A1F7353428@atlas.denx.de>
> -----Original Message-----
> From: wd at denx.de
> Sent: Tue, 15 May 2007 23:12:16 +0200
> To: ejr at inbox.com
> Subject: Re: [U-Boot-Users] undefined instruction during bootp
>
> In message <50699DE79EE.000005B9ejr@inbox.com> you wrote:
>>
>> I'm getting an undefined instruction error at the end of the bootp
>> command:
> ...
>> Does anyone know how to solve this problem?
>
> What does your memory map look like? Maybe you are overwriting data or
> code needed by U-Boot?
>
> Also, consider problem number 1: memory errors dues to incorrect RAM
> initialization.
I've considered that but unless I'm missing some config item, that looks good.
I've got 32MB ram:
arch_number = 0x00000186
env_t = 0x00000000
boot_params = 0xC0000100
DRAM bank = 0x00000000
-> start = 0xC0000000
-> size = 0x02000000
ethaddr = 00:08:EE:00:63:B2
ip_addr = 192.168.0.13
baudrate = 115200 bps
My TEXT_BASE starts at 0xc1fc0000 and I'm loading at 0xc0f00000 (~1.2M)
cpu/mya404/start.o(.text)
.text 0xc1fc0000 0x420 cpu/mya404/start.o
0xc1fc0048 _bss_start
0xc1fc004c _bss_end
0xc1fc0044 _armboot_start
0xc1fc0000 _start
0xc1fc03e0 reset_cpu
*(.text)
.text 0xc1fc0420 0xec board/mia404/libmia404.a(lowlevel_init.o)
0xc1fc0424 lowlevel_init
.text 0xc1fc050c 0x4d0 cpu/mya404/libmya404.a(interrupts.o)
0xc1fc088c set_timer
0xc1fc0804 reset_timer
0xc1fc0724 do_fiq
0xc1fc076c interrupt_init
0xc1fc0670 do_undefined_instruction
0xc1fc0534 show_regs
0xc1fc0748 do_irq
0xc1fc09c0 get_tbclk
0xc1fc0878 get_timer
0xc1fc07d0 reset_timer_masked
0xc1fc0518 bad_mode
0xc1fc0808 get_timer_masked
0xc1fc089c udelay
0xc1fc0928 udelay_masked
0xc1fc06b8 do_prefetch_abort
0xc1fc09ac get_ticks
0xc1fc0510 disable_interrupts
0xc1fc0700 do_not_used
0xc1fc06dc do_data_abort
0xc1fc0694 do_software_interrupt
0xc1fc050c enable_interrupts
.text 0xc1fc09dc 0x98 lib_arm/libarm.a(_udivsi3.o)
0xc1fc09dc __udivsi3
.text 0xc1fc0a74 0x2f0 lib_arm/libarm.a(board.o)
0xc1fc0b5c hang
0xc1fc0b6c start_armboot
0xc1fc0a74 sbrk
.text 0xc1fc0d64 0x4 lib_arm/libarm.a(div0.o)
0xc1fc0d64 __div0
.text 0xc1fc0d68 0x14f8 net/libnet.a(net.o)
0xc1fc1d18 getenv_IPaddr
0xc1fc15b8 NetCksumOk
0xc1fc0f80 NetSetTimeout
0xc1fc1620 copy_filename
0xc1fc15dc NetEthHdrSize
0xc1fc1674 ip_to_string
0xc1fc104c ArpTimeoutCheck
0xc1fc16f0 NetReceive
0xc1fc1c98 string_to_ip
0xc1fc1264 NetSendUDPPacket
0xc1fc16cc print_IPaddr
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> No, I'm not going to explain it. If you can't figure it out, you
> didn't want to know anyway... :-)
> - Larry Wall in <1991Aug7.180856.2854@netlabs.com>
next prev parent reply other threads:[~2007-05-15 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 20:49 [U-Boot-Users] undefined instruction during bootp Junior
2007-05-15 21:12 ` Wolfgang Denk
2007-05-15 21:32 ` Junior [this message]
2007-05-15 21:42 ` Wolfgang Denk
2007-05-15 21:51 ` Junior
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=50C96E42594.00000616ejr@inbox.com \
--to=ejr@inbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox