From: thaoth <thaoth@cybersoft-vn.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [T-Engine] UBoot configuration for T-Engine/SH7727 MS7727CP02 DevKit
Date: Tue, 19 Aug 2008 21:02:33 -0700 (PDT) [thread overview]
Message-ID: <19062634.post@talk.nabble.com> (raw)
In-Reply-To: <bc6f41e00808080159y3d846b02v3f55931875515ce4@mail.gmail.com>
Hi Nobuhiro Iwamatsu,
1. Clock frequency of board.
#define CONFIG_SYS_CLK_FREQ 33333333
#define TMU_CLK_DIVIDER 4 /* 4 (default), 16, 64, 256 or 1024 */
#define CFG_HZ (CONFIG_SYS_CLK_FREQ / TMU_CLK_DIVIDER)
I don't understand how to set CONFIG_SYS_CLK_FREQ value. From T-Engine
support, they said clock frequency of board is 144MHz.
CPU: SH7727 144 MHz
Flash ROM: 80000000 - 807FFFFF : 8 MB (64 KB blk x 128)
80000000 - 8000FFFF : Monitor Area (64 KB)
80010000 - 8001007F : RomInfo Area (128 B)
SDRAM: 8C000000 - 8DFFFFFF : 32 MB
8C000000 - 8C001FFF : Monitor & System Area (8 KB)
Could I set CFG_HZ to 144?
#define CFG_HZ 144
2. Cross compiler tool chain : GCC vs T-Engine toolchain
There are two tool chains
-
http://www.superh-linux.org/archive/bsp/sh7721_se/toolchain_sh3_gcc4.2.tar.gz
support elf32-sh-linux target.
- Tool chain from T-Engine forum support elf32-sh-tkernel
Using both cross compilers, we could turn on LED on debug board by setting
correct value LED_A and LED_B value.
3. ICE or JTAG debugger and LED debugging.
I don't have these debug tools, and so hard for debugging. T-Engine/SH7727
DevKit has debug board with 8 LEDs. I could turn on/off these LEDs by
setting correct value to 0xA1600000 memory. But C function turn on/off LED
cannot work. For example
int cpu_init(void)
{
// Turn off LED 1 to notify cpu_init is called.
outw(0x00 & 0xFF, 0xa1600000);
return 0;
}
I don't know why it isn't called?
Would you please give me your ideas? Thank you a lot.
Regards,
--
View this message in context: http://www.nabble.com/-T-Engine--UBoot-configuration-for-T-Engine-SH7727-MS7727CP02-DevKit-tp18868090p19062634.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-08-20 4:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 11:03 [U-Boot-Users] [T-Engine] UBoot configuration for T-Engine/SH7727 MS7727CP02 DevKit thaoth
2008-08-08 1:35 ` Nobuhiro Iwamatsu
2008-08-08 7:51 ` thaoth
2008-08-08 8:59 ` Nobuhiro Iwamatsu
2008-08-20 4:02 ` thaoth [this message]
2008-08-20 7:40 ` [U-Boot] " Nobuhiro Iwamatsu
2008-08-21 7:26 ` thaoth
2008-08-21 9:54 ` thaoth
2008-08-21 11:27 ` thaoth
2008-09-03 3:48 ` thaoth
2008-09-10 11:51 ` thaoth
2008-09-10 12:13 ` Nobuhiro Iwamatsu
2008-09-11 2:17 ` Yoshihiro Shimoda
2008-09-11 7:41 ` thaoth
2008-09-11 12:00 ` Yoshihiro Shimoda
2008-09-12 5:46 ` thaoth
2008-09-12 6:44 ` Yoshihiro Shimoda
2008-09-12 10:05 ` thaoth
2008-09-12 10:53 ` Yoshihiro Shimoda
2008-09-12 10:58 ` thaoth
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=19062634.post@talk.nabble.com \
--to=thaoth@cybersoft-vn.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