From: angelo <angelo70@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mcf5307, timer 2 issue loading linux
Date: Wed, 03 Aug 2011 15:29:50 +0200 [thread overview]
Message-ID: <4E394D4E.30005@gmail.com> (raw)
In-Reply-To: <20110803130758.B4120177A7AA@gemini.denx.de>
Hi Wolfgang,
i confirm that before the patch/solution applied (i just posted it), i
also tried "bootm FLASH_ADDR". Same result, loading fail, since timer2
interrupt is not stopped and the interrupt happen just after the linux
head.S execution.
As i said, probably this issue was not visible in other coldfire models
since mcf5307 run at 90mhz only.
I have copied the "arch_preboot_os()" solution from other boards, that
was doing the same thing, disabling async interrupts before loading the os.
Regards,
angelo
On 03/08/2011 15:07, Wolfgang Denk wrote:
> Dear angelo,
>
> In message<4E390235.2090107@gmail.com> you wrote:
>
>> i am reporting the following issue, maybe related to something wrong in
>> my new mcf5307 support addition (still under testing), or maybe not:
>>
>>
>> 1. U-Boot run correctly, timer2 is enabled as a system timestamp counter.
>> 2. I load a uClinux bianry from flash to SDRAM with "cp.l FLASH_ADDR
>> SDRAM_ADDR SIZE/4
>> 3. i launch the binary with "go SDRAM_ADDR"
>>
> You must not start Linux with a "go" command. Please use "bootm" for
> this purpose (and then you also don;t have to copy the kernal
> manually).
>
> Best regards,
>
> Wolfgang Denk
>
>
--
.:.:.SYSAM.:.:.
di Angelo Dureghello
via San Nazario 149
34151, Trieste, Italy
++39 340 7631990
www.sysam.it <http://www.sysam.it>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo.png
Type: image/png
Size: 3033 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110803/187428aa/attachment.png
prev parent reply other threads:[~2011-08-03 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 8:09 [U-Boot] mcf5307, timer 2 issue loading linux angelo
2011-08-03 12:50 ` Greg Ungerer
2011-08-03 13:06 ` angelo
2011-08-03 13:07 ` Wolfgang Denk
2011-08-03 13:29 ` angelo [this message]
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=4E394D4E.30005@gmail.com \
--to=angelo70@gmail.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