[U-Boot] Pull request - ColdFire
Wolfgang, The following changes since commit 0b692dcb190655c7eb96b6b8003bee163e3b58dd: Wolfgang Denk (1): Merge branch 'master' of git://git.denx.de/u-boot-net are available in the git repository at: git://www.denx.de/git/u-boot-coldfire.git master TsiChung Liew (1): MCF5271-only: Added a weak board_reset function to allow custom reset Wolfgang Wegner (3): add include/asm-m68k/unaligned.h allow MCF532x to use CONFIG_MONITOR_IS_IN_RAM MCF532x: make icache_enable use CONFIG_SYS_SDRAM_SIZE cpu/mcf52x2/cpu.c|6 ++ cpu/mcf52x2/cpu.h| 33 + cpu/mcf532x/speed.c |3 +++ cpu/mcf532x/start.S |6 +- drivers/mtd/cfi_flash.c |2 +- include/asm-m68k/unaligned.h | 15 +++ 6 files changed, 63 insertions(+), 2 deletions(-) create mode 100644 cpu/mcf52x2/cpu.h create mode 100644 include/asm-m68k/unaligned.h Thanks! Regards, TsiChung ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] coldfire support
Thirumalai, These ColdFire processors (MCF52277, MCF5235, MCF5249, MCF5253, MCF5271, MCF5272, MCF5275, MCF5282, MCF5329, MCF5373, MCF5445x, and MCF547x_8x) are supported by u-boot. Like Wolfgang Wegner mentioned, you can download the ToolChain at http://www.codesourcery.com/sgpp/lite/coldfire. As for the Linux, we use different repository site. http://www.bitshrine.org/gpp/ Regards, TsiChung On Mon, Feb 22, 2010 at 5:00 AM, Thirumalai wrote: > Hi denx, > I just want to know whether the coldfire processor is supported by > u-boot and what toolchains need to be used for compilation. Whether ELDK > will support or not ? > > Thank you > Thirumalai > > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] u-boot coldfire linux and fdt
Hi Philippe, ColdFire Linux does use the MAC address, the issue is that the kernel does not pass the MAC address properly to the FEC driver. I will pass up this issue to the Linux team to have it fix soon. The bd_info struct is still there and has not removed from u-boot source. There is a plan of implementing fdt. Regards, TsiChung On Sun, Feb 21, 2010 at 6:31 AM, Philippe De Muyter wrote: > Hello Tsi Chung Liew, > > I have installed u-boot and linux on a in-house-made coldfire mcf5484 based > board. As u-boot currently supports mcf5484-based development boards, I used > that as a starting point for the u-boot port for our in-house board. > > For linux unfortunately I needed to stick with the ltib-based version of > linux-2.6.25 for mcf5484-based development boards distributed by freescale. > > I have discovered the hard way that that version of linux does not use > the mac addresses for the ethernet ports as known by u-boot under the > names "ethaddr" and "eth1addr", but uses the same wrong mac-address for all > the boards. > > Now it seems that the old way to communicate the mac addresses from u-boot > to linux using the struct bd_info has been deprecated and removed from > u-boot sources. I see some fdt-related functions in the u-boot sources, > but I am not sure that the fdt blob is given to linux, or that linux > for coldfire expects to get and use a fdt blob. > > Can you enlighten me regarding that point, especially for mcf5484 boards ? > > Thanks in advance > > Philippe > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Pull request - ColdFire
Wolfgang, Please pull. Thanks! Regards, TsiChung The following changes since commit f3651764e57e353251695691677bd95ba5a420bc: Frans Meulenbroeks (1): cmd_itest.c: fix pointer dereferencing are available in the git repository at: git://git.denx.de/u-boot-coldfire.git next Richard Retanubun (1): MCF5271-only: Added a weak board_reset function to allow custom reset Wolfgang Wegner (3): add include/asm-m68k/unaligned.h MCF532x: make icache_enable use CONFIG_SYS_SDRAM_SIZE allow MCF532x to use CONFIG_MONITOR_IS_IN_RAM cpu/mcf52x2/cpu.c|6 ++ cpu/mcf52x2/cpu.h| 33 + cpu/mcf532x/speed.c |3 +++ cpu/mcf532x/start.S |6 +- include/asm-m68k/unaligned.h | 15 +++ 5 files changed, 62 insertions(+), 1 deletions(-) create mode 100644 cpu/mcf52x2/cpu.h create mode 100644 include/asm-m68k/unaligned.h ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Please pull u-boot-coldfire
Hi Wolfgang, Please pull this change for u-boot-coldfire/next into your branch: The following changes since commit 7d4450a9773673052fcd7fdf0a4a88c089126ac1: Wolfgang Denk (1): mpc5121ads: add JFFS2 and MTDPARTS support; adjust flash map are available in the git repository at: git://www.denx.de/git/u-boot-coldfire.git next TsiChung Liew (9): ColdFire: Update configuration file to use flash buffer write ColdFire: Update for M54451EVB ColdFire: Add M5208EVB and MCF520x CPU support ColdFire: Fix M53017EVB flash size ColdFire: Remove compiler warning messages Coldfire: Consolidate DSPI driver ColdFire: Add DSPI support for MCF5227x and MCF5445x Command for accessing serial flash update ColdFire: Update bootargs MAKEALL |1 + Makefile | 12 +- board/freescale/m5208evbe/Makefile| 44 board/freescale/m5208evbe/config.mk | 25 +++ board/freescale/m5208evbe/m5208evbe.c | 94 + board/freescale/m5208evbe/u-boot.lds | 142 + board/freescale/m54451evb/u-boot.spa |9 +- common/cmd_sf.c |2 +- cpu/mcf5227x/Makefile |2 +- cpu/mcf5227x/cpu_init.c | 53 + cpu/mcf5227x/dspi.c | 261 cpu/mcf52x2/config.mk |4 + cpu/mcf52x2/cpu.c | 66 ++ cpu/mcf52x2/cpu_init.c| 89 cpu/mcf52x2/interrupts.c |8 +- cpu/mcf52x2/speed.c | 13 +- cpu/mcf52x2/start.S | 33 +++- cpu/mcf5445x/Makefile |2 +- cpu/mcf5445x/cpu_init.c | 66 ++ cpu/mcf5445x/dspi.c | 239 -- cpu/mcf5445x/start.S | 81 +--- drivers/spi/Makefile |1 + drivers/spi/cf_spi.c | 357 include/asm-m68k/coldfire/dspi.h | 229 ++--- include/asm-m68k/immap.h | 29 +++ include/asm-m68k/immap_520x.h | 212 +++ include/asm-m68k/m520x.h | 358 + include/configs/M5208EVBE.h | 223 include/configs/M52277EVB.h | 26 +-- include/configs/M53017EVB.h |7 +- include/configs/M54451EVB.h | 73 +++ include/configs/M54455EVB.h | 27 +-- lib_m68k/board.c |2 +- 33 files changed, 2039 insertions(+), 751 deletions(-) create mode 100644 board/freescale/m5208evbe/Makefile create mode 100644 board/freescale/m5208evbe/config.mk create mode 100644 board/freescale/m5208evbe/m5208evbe.c create mode 100644 board/freescale/m5208evbe/u-boot.lds delete mode 100644 cpu/mcf5227x/dspi.c delete mode 100644 cpu/mcf5445x/dspi.c create mode 100644 drivers/spi/cf_spi.c create mode 100644 include/asm-m68k/immap_520x.h create mode 100644 include/asm-m68k/m520x.h create mode 100644 include/configs/M5208EVBE.h Thanks! Regards, TsiChung ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot doesn't compile for M54455EVB_intel_config
Matt, In asm-m68k/io.h, please add #ifndef _IO_BASE #define _IO_BASE 0 #endif Regards, TsiChung On Wed, Jul 15, 2009 at 9:43 AM, Matthew Lear wrote: > Hi TsiChung / Wolfgang, > > I just pulled u-boot.git to re-sync and tried to configure and build it > for M54455EVB_intel_config but the compilation failed. I tried a fresh > clone just to be sure and it was the same. > > [snip] > > m68k-linux-gnu-gcc -g -Os -ffixed-d7 -msep-data -D__KERNEL__ > -DTEXT_BASE=0x -I/home/matt/nht/git-uboot-master/u-boot/include > -fno-builtin -ffreestanding -nostdinc -isystem > /opt/freescale/usr/local/gcc-4.2.35-eglibc-2.5.35/m68k-linux/lib/gcc/m68k-linux-gnu/4.2.0/include > -pipe -DCONFIG_M68K -D__M68K__ -mcpu=54455 -fPIC -DTEXT_BASE=0x > -Wall -Wstrict-prototypes -fno-stack-protector -o cmd_ide.o cmd_ide.c -c > cmd_ide.c: In function '__ide_outb': > cmd_ide.c:529: error: '_IO_BASE' undeclared (first use in this function) > cmd_ide.c:529: error: (Each undeclared identifier is reported only once > cmd_ide.c:529: error: for each function it appears in.) > cmd_ide.c: In function '__ide_inb': > cmd_ide.c:538: error: '_IO_BASE' undeclared (first use in this function) > cmd_ide.c: In function 'output_data': > cmd_ide.c:942: error: '_IO_BASE' undeclared (first use in this function) > cmd_ide.c: In function 'input_data': > cmd_ide.c:1000: error: '_IO_BASE' undeclared (first use in this function) > cmd_ide.c: In function 'output_data_shorts': > cmd_ide.c:1705: error: '_IO_BASE' undeclared (first use in this function) > cmd_ide.c: In function 'input_data_shorts': > cmd_ide.c:1711: error: '_IO_BASE' undeclared (first use in this function) > make[1]: *** [cmd_ide.o] Error 1 > make[1]: Leaving directory `/home/matt/nht/git-uboot-master/u-boot/common' > make: *** [common/libcommon.a] Error 2 > > > Is this expected at the current time? > > Rgds, > -- Matt > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Axiom MCF5282 help
Mark, There could be a hardware issue. Is the phy crystal on the board is F25.00 or F25.00P? Regards, TsiChung On Mon, May 25, 2009 at 3:15 PM, Mark Giacobbe wrote: > Hi All - > > I'm new to u-boot and I am running into some issues. I an using the > Axiom 5282lite board and I cannot get the ethernet working. > > I have u-boot flashed onto the board, and when I connect the board > to my Linksys WRT54G router, the Link LED on the board constantly > flashes, as does the LED for that port on the router. > > I assigned an IP to the board, outside the DHCP range, but I cannot > ping the board, and the board cannot ping anything, including the router. > > Any ideas? > > Speaking of DHCP, does the code support DHCP for the 5282? > > Any help you be appreciated. > Thanks > Mark > > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [mcf532x] dependency of start.S not correct
Wolfgang, Have you checked your board/Your_platform/u-boot.lds? Regards, TsiChung On Thu, Jun 4, 2009 at 10:06 AM, Wolfgang Wegner wrote: > Hi, > > sorry I can not provide a solution, but when trying to migrate my > board to newer U-Boot I realised that the dependency calculation > is not correct for cpu/mcf532x/start.S > > start.S references several CONFIG_SYS_ macros and thus should be > re-compiled when the board configuration header file changes (like > all the .c files in this directory are), but is not. > > I have to admit I do not really understand how dependencies are > calculated in U-Boot build system, so forgive me that this is > merely a bug report than a patch. > > Regards, > Wolfgag > > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] MCF5271: Added #defines for Edge Port Module (EPORT)
Richard, Nack. It is already existed in asm-m68k/coldfire/eport.h Regards, TsiChung On Fri, Jun 5, 2009 at 4:12 PM, Richard Retanubun wrote: > From edb2947e95dc8dc1c91bc952002304267d02639f Mon Sep 17 00:00:00 2001 > From: Richard Retanubun > Date: Fri, 5 Jun 2009 15:54:56 -0400 > Subject: [PATCH] MCF5271: Added #defines for Edge Port Module (EPORT) > > This patch adds #defines of EPORT registers as offsets from IPSBAR (MBAR) > --- > include/asm-m68k/m5271.h | 8 > 1 files changed, 8 insertions(+), 0 deletions(-) > > diff --git a/include/asm-m68k/m5271.h b/include/asm-m68k/m5271.h > index d25261b..8bcf6d6 100644 > --- a/include/asm-m68k/m5271.h > +++ b/include/asm-m68k/m5271.h > @@ -261,4 +261,12 @@ > #define INT0_HI_CAN1_BOFFINT (60) > /* 60-63 Reserved */ > > +/* Edge Port Module (EPORT) Register offser from CONFIG_SYS_MBAR */ > +#define MCF_EPORT_EPPAR 0x13 > +#define MCF_EPORT_EPPDDR 0x130002 > +#define MCF_EPORT_EPIER 0x130003 > +#define MCF_EPORT_EPDR 0x130004 > +#define MCF_EPORT_EPPDR 0x130005 > +#define MCF_EPORT_EPFR 0x130006 > + > #endif /* _MCF5271_H_ */ > -- > 1.6.2.4 > > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] coldfire M5329EVB demo problem
Carlos,
Compile the hello_world and stubs without the -msep-data and -fPIC options,
then linking with -Ttext 0x4002. Or, make change to the cpu/mcf532x/
config.mk.
Regards,
TsiChung
On Wed, Feb 4, 2009 at 3:43 AM, kescuin wrote:
> Hi, everyone
>
> I'm working wint an u-boot 2008.10 version over a Coldfire M5329EVB Board.
> Every thing goes well on u-boot working. But when I try to execute
> standalone applications i've got problems.
>
> I've been trying with the hello_world example as it is on the manual. First
> time I tryed I used the standard (on the make file ) address 0x2 for
> m68k board, loading it to the board with tftp 0x2 hello_world.bin
> I've also changed other address but when I do the go {addr} I always get an
> *** Unexpected exception ***
> Vector Number: 4 Format: 04 Fault Status: 0
>
> Any one have executed stand alone applications on this board? What should
> be
> happening?
> Thanks for your help.
>
> Carlos Kescuin
>
> ___
> U-Boot mailing list
> U-Boot@lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Coldfire: bootm: How does bootm pass bootargs to linux?
Richard,
> /*
> * Linux Kernel Parameters (passing board info data):
> * r3: ptr to board info data
> * r4: initrd_start or 0 if no initrd
> * r5: initrd_end - unused if r4 is 0
> * r6: Start of command line string
> * r7: End of command line string
> */
Above is the copy and paste from PPC.
> My question is, how does bootm passes arguments to the kernel for the
coldfire
In ColdFire, the Linux Kernel Parameters is located at u-boot's stack.
> (M5271 specifically)? And what is the recommended way to capture and
process the info
> in the kernel?
In kernel/head.S,
Save the location of u-boot info - cmd line, bd_info, etc
movel %a7, uboot_info_stk /* save uboot info to variable */
In kernel/setup.c,
unsigned long uboot_info_stk;
EXPORT_SYMBOL(uboot_info_stk);
static struct uboot_record uboot_info;
int __init uboot_comandline(char *bootargs)
{
...
uboot_info.bd_info = (*(u32 *)(uboot_info_stk));
uboot_info.initrd_start = (*(u32 *)(uboot_info_stk+4);
...
}
Regards,
TsiChung
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Status open patches: ColdFire
Wolfgang, We will include in the coming RC release. Thanks! Regards, TsiChung On Sat, Feb 21, 2009 at 6:00 PM, Wolfgang Denk wrote: > Dear John & Tsi Chung, > > I have the following patches still marked as open in my list. Could > you please have a look... > > ColdFire: > 12/04 "arun c" [U-Boot] [PATCH] Coldfire: XL Bus minor fixes > > > Thanks in advance. > > 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: w...@denx.de > It is wrong always, everywhere and for everyone to believe anything > upon insufficient evidence. - W. K. Clifford, British philosopher, > circa 1876 > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Coldfire: MCF5271: Periodic HW watchdog petting and sleep function does not work.
Richard, Can you be more specific on how the MAX6369 WDO and WDI connects to MCF5271's signal? Is it GPIO? ResetIn? Others? Regards, TsiChung On Mon, Mar 2, 2009 at 3:05 PM, Richard Retanubun < richardretanu...@ruggedcom.com> wrote: > Hi Guys, > > I am using u-boot 2009.03-rc1 and a board based on Coldfire MC5271EVB eval > platform. > Our external watchdog is a MAX6369. > > I have #define CONFIG_HW_WATCHDOG and #undef CONFIG_WATCHDOG in our board's > config file and > have created the hw_watchdog_reset function to toggle the WDI line to pet > the watchdog. > > However, my board keeps resetting at the watchdog timeout. Upon probing, I > found out that > the watchdog toggle line in not being toggled periodically by u-boot. Which > means a regular call > to WATCHDOG_RESET() is not happening. If I execute commands, the WDI will > get toggled and the watchdog > will not timeout, which means that the WATCHDOG_RESET() mapping to > hw_watchdog_reset function is working, it is > just not being called periodically. > > I am looking at the programmable interrupt timer that the get_timer() > function uses, and so far everything checks out. > > I'm also stuck at using u-boot's sleep command, e.g. "sleep 1" will never > return. Which I suspect may be the same root cause. > (this can also be observed on the M5271EVB board). > > What am I missing here? > > Thank you for all your time. > > Regards, > > - Richard Retanubun. > > > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] Coldfire: I2C: Update I2CFDR frequency divider 0x0E value from 192 to 204
Richard,
Nak.
The divider and fdr value are predefined in the 5271 reference manual.
The bus clock is 50Mhz and the CONFIG_SYS_I2C_SPEED is set to 8.
divider = min(i2c_clk / speed, (unsigned short) -1);
divider = 5000 / 8;
= 625
if (fsl_i2c_speed_map[i].divider >= divider), here is looking for any
divider that is larger or equal to 625.
{640, 21} is the closer match.
Regards,
TsiChung
On Thu, Mar 19, 2009 at 2:47 AM, Heiko Schocher wrote:
>
> Hello Richard,
>
> Richard Retanubun wrote:
> > From 9a7a9dfb1ed367b275bc19f7c40c98b63de75fb2 Mon Sep 17 00:00:00 2001
> > From: Richard Retanubun
> > Date: Wed, 18 Mar 2009 12:52:35 -0400
> > Subject: [PATCH] Update I2CFDR frequency divider 0x0E value from 192 to 204.
> >
> > This patch changes the divider factor of 14 for I2CFDR.
> > Through empirical experiments on a M5271EVB with a 25MHz osc,
> > multiplied to 75MHz system frequency, the divider 0x0E that is
> > supposed to be div-by-192, results in i2c clock of ~376 KHz
> > (which is ~div-by-204). Using the alternate divider for div-by-192
> > (49) results in an i2c clock of ~390 KHz, a better clock approximation.
> >
> > Signed-off-by: Richard Retanubun
> > ---
> > drivers/i2c/fsl_i2c.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/i2c/fsl_i2c.c b/drivers/i2c/fsl_i2c.c
> > index ce646fd..c61bf84 100644
> > --- a/drivers/i2c/fsl_i2c.c
> > +++ b/drivers/i2c/fsl_i2c.c
> > @@ -113,8 +113,8 @@ static const struct {
> > {56, 41}, {64, 42}, {68, 7}, {72, 43},
> > {80, 8}, {80, 44}, {88, 9}, {96, 41},
> > {104, 10}, {112, 42}, {128, 11}, {128, 43},
> > - {144, 12}, {160, 13}, {160, 48}, {192, 14},
> > - {192, 49}, {224, 50}, {240, 15}, {256, 51},
> > + {144, 12}, {160, 13}, {160, 48}, {192, 49},
> > + {204, 14}, {224, 50}, {240, 15}, {256, 51},
> > {288, 16}, {320, 17}, {320, 52}, {384, 18},
> > {384, 53}, {448, 54}, {480, 19}, {512, 55},
> > {576, 20}, {640, 21}, {640, 56}, {768, 22},
> >
>
> Because I think this will go through the coldfire tree, you have my:
>
> Acked-by: Heiko Schocher
>
> bye
> Heiko
>
> --
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>
> ___
> U-Boot mailing list
> U-Boot@lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Coldfire: MCF5271: Periodic HW watchdog petting and sleep function does not work.
Richard, I used 6 for most platforms. 1 is lowest priority - 7 - is the highest. Regards, TsiChung On Thu, Mar 19, 2009 at 4:15 PM, Richard Retanubun wrote: > Richard Retanubun wrote: >> >> Hi TC, >> >> TC Liew wrote: >>> >>> Richard, >>> Is there a purpose that you used DTIMER 3 but not 1 or 2? FYI: DTIMER3 >>> is currently used for system time, DTIMER0 is currently used for udelay() in >>> u-boot. >>> You can change the u-boot 5271's system timer in >>> include/asm-m68k/immap.h. >>> #define CONFIG_SYS_TMR_BASE (MMAP_DTMR1) >>> #define CONFIG_SYS_TMRINTR_NO (INT0_LO_DTMR1) >>> #define CONFIG_SYS_TMRINTR_MASK (INTC_IPRL_INT20) >>> Regards, >>> TsiChung >> > Hi TC, > > Sorry for the long-delay on this issue, I got tasked with other stuff, > but thanks to your hint from the last e-mail, > I think I might have found the root-cause to the problem. > > In include/asm-m68k/immap.h. > > #ifdef CONFIG_M5271 > #include > #include > > #define CONFIG_SYS_FEC0_IOBASE (MMAP_FEC) > #define CONFIG_SYS_UART_BASE (MMAP_UART0 + (CONFIG_SYS_UART_PORT > * 0x40)) > > /* Timer */ > #ifdef CONFIG_MCFTMR > #define CONFIG_SYS_UDELAY_BASE (MMAP_DTMR0) > #define CONFIG_SYS_TMR_BASE (MMAP_DTMR3) > #define CONFIG_SYS_TMRPND_REG (((volatile int0_t > *)(CONFIG_SYS_INTR_BASE))->iprl0) > #define CONFIG_SYS_TMRINTR_NO (INT0_LO_DTMR3) > #define CONFIG_SYS_TMRINTR_MASK (INTC_IPRL_INT22) > #define CONFIG_SYS_TMRINTR_PEND (CONFIG_SYS_TMRINTR_MASK) > > #define CONFIG_SYS_TMRINTR_PRI (0) /* Level must > include inorder to work */ > ^ > #define CONFIG_SYS_TIMER_PRESCALER (((gd->bus_clk / 100) - 1) << 8) > #endif > > According to MCF5271 RefMan Rev 2 (07/2006) page 13-12, > I think this means that the interrupt, although unmasked, have a level 0, > priority 0, > which essentially disables it. > > What should be the proper value? (0x09) will make it level 1, priority 1, is > this ok? > Or am I chasing the wrong rabbit? > > Thanks for your time > > - Richard > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
