From: Steve Poulsen <spoulsen@css-design.us>
To: mohammed shareef <mdshareef@gmail.com>
Cc: omap <linux-omap@vger.kernel.org>
Subject: Re: undefined instruction
Date: Thu, 26 Jun 2008 11:11:55 -0500 [thread overview]
Message-ID: <4863BFCB.9040105@css-design.us> (raw)
In-Reply-To: <a1d91fa0806260829l6953e0b6o754b00b632efae47@mail.gmail.com>
Mohammed,
When you tftp the file to memory, you need to make sure the filesize
fits in the memory available. Since you have experimentally done that
and now want to flash the pieces, I suggest you look at the "split"
command under Linux. You will need to split the file into pieces that
fit into RAM and flash at the proper address. If you split the file
into two pieces, then you will need to flash the first piece at address
X and the second piece at address X + 16meg. You should make sure you
split the file on a sector boundary. If you don't want to think about
this, then you should erase/unprotect the whole area you will need
first, then transfer and flash the pieces.
You may want to look at the omapfl utility. With some modification,
you could flash your image more easily via USB.
Steve
mohammed shareef wrote:
> Hi,
>
> I tried to do the same procedure with a small filesystem image <
> 16Mb... it worked. i didnt have such problems. so could someone please
> tell me how to divide the filesystem image in to two and flash it?
> thank you,
> regards,
> shareef
>
> On Thu, Jun 26, 2008 at 4:36 PM, mohammed shareef <mdshareef@gmail.com> wrote:
>
>> Hi,
>>
>> i did the below. i got an image. but i am still having the same problem
>>
>> my file size is 23Mb
>>
>> [root@localhost tftpboot]# mkfs.jffs2 --squash -r /data/rootfs2.6
>> -e131072 > /data/rootfs-jffs2.img
>> [root@localhost tftpboot]# cp /data/rootfs-jffs2.img /tftpboot/rootfs-jffs2.img
>>
>> \0x09 #################################################################
>> \0x09 #############undefined instruction
>> pc : [<e0000004>] lr : [<00000002>]
>> sp : 1103fca4 ip : 11095dd8 fp : 00000001
>> r10: 10963410 r9 : 1103fd24 r8 : 1103ffdc
>> r7 : 270a30a1 r6 : 8695632d r5 : 08016ffa r4 : 5aebcc39
>> r3 : 00000032 r2 : 11095dd4 r1 : 000000a0 r0 : 00000000
>> Flags: nZCv IRQs off FIQs off Mode SVC_32
>> Resetting CPU ...
>>
>> could you please tell me what i should do. thank you.
>> regards,
>> Shareef
>>
>>
>>
>> On Wed, Jun 25, 2008 at 9:52 PM, Hunter, Jon <jon-hunter@ti.com> wrote:
>>
>>>> then i changed the filename and the
>>>> tftpboot transfer started. But on the mid-way it complains "undefined
>>>> instruction".
>>>>
>>>> could some one please tell me where the problem is? thank you.
>>>>
>>> How big is the file that you are attempting to download over tftp?
>>>
>>> U-boot executes in the upper part of the RAM and so if your file is too big, then there is a good chance you are overwriting u-boot which would cause u-boot to crash eventually. U-boot does not protect against this. This would be a potential cause of an undefined instruction exception.
>>>
>>> Jon
>>>
>>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2008-06-26 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 7:29 undefined instruction mohammed shareef
2008-06-25 16:22 ` Hunter, Jon
2008-06-26 11:06 ` mohammed shareef
2008-06-26 15:29 ` mohammed shareef
2008-06-26 16:11 ` Steve Poulsen [this message]
2008-06-26 16:29 ` mohammed shareef
2008-06-26 17:40 ` mohammed shareef
2008-06-26 18:33 ` Steve Poulsen
2008-06-26 19:00 ` mohammed shareef
[not found] ` <4863EB49.8050703@css-design.us>
2008-06-26 19:26 ` mohammed shareef
2008-06-26 21:00 ` Steve Poulsen
2008-06-26 20:51 ` Steve Poulsen
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=4863BFCB.9040105@css-design.us \
--to=spoulsen@css-design.us \
--cc=linux-omap@vger.kernel.org \
--cc=mdshareef@gmail.com \
/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