June 2007 - U-Boot

[U-Boot-Users] [PATCH] remove warning of const casting in fpga_no_sup
by eran liberty 21 Jun '07

21 Jun '07

Signed-off-by: Eran Liberty diff -x .svn -Nuar u-boot.git-5ffa76a032279bc6d3230b703eda32d13305ba13/common/fpga.c u-boot.exsw6000/common/fpga.c --- u-boot.git-5ffa76a032279bc6d3230b703eda32d13305ba13/common/fpga.c 2007-06-18 22:38:46.000000000 +0300 +++ u-boot.exsw6000/common/fpga.c 2007-06-20 19:05:00.000000000 +0300 @@ -64,7 +64,7 @@ /* fpga_no_sup * 'no support' message function */ -static void fpga_no_sup( char *fn, char *msg ) +static void fpga_no_sup(const char *fn,const char *msg ) { if ( fn && msg ) { printf( "%s: No support for %s. CONFIG_FPGA defined as 0x%x.\n", @@ -207,10 +207,6 @@ memset( desc_table, 0, sizeof(desc_table)); PRINTF( "%s: CONFIG_FPGA = 0x%x\n", __FUNCTION__, CONFIG_FPGA ); -#if 0 - PRINTF( "%s: CFG_FPGA_XILINX = 0x%x\n", __FUNCTION__, CFG_FPGA_XILINX ); - PRINTF( "%s: CFG_FPGA_ALTERA = 0x%x\n", __FUNCTION__, CFG_FPGA_ALTERA ); -#endif } /* fpga_count

1 0

[U-Boot-Users] [PATCH] Adds rstcr to 85xx memory map
by eran liberty 21 Jun '07

21 Jun '07

Signed-off-by: Eran Liberty diff -x .svn -Nuar u-boot.git-5ffa76a032279bc6d3230b703eda32d13305ba13/include/asm-ppc/immap_85xx.h u-boot.exsw6000/include/asm-ppc/immap_85xx.h --- u-boot.git-5ffa76a032279bc6d3230b703eda32d13305ba13/include/asm-ppc/immap_85xx.h 2007-06-18 22:38:46.000000000 +0300 +++ u-boot.exsw6000/include/asm-ppc/immap_85xx.h 2007-06-20 19:04:41.000000000 +0300 @@ -1548,7 +1548,9 @@ char res9[12]; uint pvr; /* 0xe00a0 - Processor version register */ uint svr; /* 0xe00a4 - System version register */ - char res10[3416]; + char res9a[8]; + uint rstcr; /* 0xe00b0 - Reset control register */ + char res10[3404]; uint clkocr; /* 0xe0e00 - Clock out select register */ char res11[12]; uint ddrdllcr; /* 0xe0e10 - DDR DLL control register */

1 0

[U-Boot-Users] How to add new /board specific command to uboot ?
by harsh poshtiwala 21 Jun '07

21 Jun '07

Hi Friends, I tried to add a new command for my nmdk8810b6 board following README ./commands file. Uboot just hangs at the initial stage even i doesn't boot , i don't see the uboot-1.1.4 text even. I see some junk characters then it stops there. I did following things 1, created a file for my command "cmd_dvt.c" which has UBOOT_CMD( ) and parameters a function for my command 2,I included common.h command.h and dvt.h from where my command function reads the data. 3,I placed my cmd_dvt.c file in theTOPLEVEL /common directory. 4, I have included cmd_dvt.o in THE SAME Makefilewhere most common commands are compiled. Did i miss something ? or i am placing it in a wrong directory ? Do i need to place this command in the /include/configs/nmdk8810.h file ? or anything else ? I would appreciate your pointers on this 5, -- Thanks & Regards Harsh

1 0

[U-Boot-Users] [ARM] TI DaVinci support -- a conspiracy?
by ksi＠koi8.net 21 Jun '07

21 Jun '07

That's to the list maintainers... Is it some kind of conspiracy around TI and their DaVinci chips? I can't understand why my last two postings are not showing in the list archive. They were resent to me from the list as if everything was OK but they are not showing in the archive that make me think they didn't go any further so nobody saw them. All the later postings I've got from the list made it into the archive and I can see them on the web. I mean those sent AFTER my DaVinci related ones that I sent yesterday. What's going on? Is it some kind of conspiracy? Why my postings are ignored? Is it a taboo on this list and nobody is allowed to mess with it? Is it TI that has instructed to ignore them? Sorry for ranting but I can't understand WHY all my efforts to contribute to OPEN SOURCE U-Boot are totally ignored and my postings are filtered... --- ****************************************************************** * KSI@home KOI8 Net < > The impossible we do immediately. * * Las Vegas NV, USA < > Miracles require 24-hour notice. * ******************************************************************

2 3

[U-Boot-Users] Some questions about what is planned to improve U-Boot configuration...
by Carsten Schlote 21 Jun '07

21 Jun '07

Hi, as everyone knows, the current config system for U-Boot is simply PITA. I regexed all 'CONFIG_' defines from the latest sources, and I found more than 1300 unique defines. Not tested with 'CFG_' defines yet. Some defines use cannonical names, so you see what belongs together. For the rest you must dig in the sources. I also found, that you need to undef several defines to disable a sub system completely. Any single change/addition/removal to/of a CONFIG_ define might have a side-effect. And most times it has. I would like to know, if there are any plans or is on-going work to replace this hand-crafted mess with a configuration system? I'd like to use something like Kconfig. It turned out to be useful with Linux, BusyBox or ptxdist. It handles dependencies between defines, and also provides help and defaults for each. Regards Carsten ____________ Virus checked by G DATA AntiVirusKit Version: AVK 17.5384 from 14.06.2007 ____________ Virus checked by G DATA AntiVirus Version: AVK 17.5384 from 14.06.2007 Virus news: www.antiviruslab.com

7 15

[U-Boot-Users] U-Boot 1.2 - Cannot run hello_world - Coldfire
by Arun Biyani 20 Jun '07

20 Jun '07

I have a target board with a Coldfire CPU. I am unable to run the example program hello_world which comes with the distribution. Transcript of session is below. What am I missing? The cross compile tools were run on Linux (FC 7), downloaded from snapgear.org uClinux directory. I tried this with v1.1.6 also. I'll be glad to provide any additional data. I have just started with U-Boot so please be explicit. On the host, I was running Tera Term and used "send file" from the "File" menu to send the srec file. I ran the program with parameters as well with the same result. U-Boot 1.2.0 (Jun 13 2007 - 07:36:11) CPU: Freescale MCF5272 (Mask:1) Board: Telasic RLB 2.0 DRAM: 16 MB FLASH: 32 MB In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 -> -> ds Unknown command 'ds' - try 'help' -> loads ## Ready for S-Record download ... ## First Load Addr = 0x00020000 ## Last Load Addr = 0x000222F7 ## Total Size = 0x000022F8 = 8952 Bytes ## Start Addr = 0x00020000 -> go 0x00020004 ## Starting application at 0x00020004 ... *** Unexpected exception *** Vector Number: 4 Format: 04 Fault Status: 0 PC: 00ff94fc SR: 00002004 SP: 00f6db0c D0: 00000000 D1: 0000048c D2: 00000000 D3: 00ff8fac D4: 000000f3 D5: 00000000 D6: 00000000 D7: 00f7df90 A0: 00fed912 A1: 00ff94fc A2: 00020004 A3: 00f6ded8 A4: 00000002 A5: 00ff7300 A6: 00f6db8c *** Please Reset Board! ***

4 12

[U-Boot-Users] [PATCH] Add support for M41T60 serial access real-time clock
by Lawrence R. Johnson 20 Jun '07

20 Jun '07

Hi everyone, Here is a patch to add support to U-Boot for the STMicroelectronics M41T60 serial RTC. I used the driver for the M41T11 as a template. The code was tested using an AMCC Sequoia board (PPC440EPx processor) with the M41T60 connected to the board's I2C0 header. In the intended application, the RTC will be powered by a large capacitor, rather than a battery. The driver therefore checks to see whether the RTC has lost power. The chip's OUT bit is normally reset from its power-up state. If the OUT bit is read as set, or if the date and time are not valid, then the RTC is assumed to have lost power, and its date and time are reset to 1900-01-01 00:00:00. Signed-off-by: Larry Johnson <lrj(a)acm.org> diff -Naur a/rtc/m41t60.c b/rtc/m41t60.c --- a/rtc/m41t60.c 1969-12-31 19:00:00.000000000 -0500 +++ b/rtc/m41t60.c 2007-06-18 11:02:11.000000000 -0400 @@ -0,0 +1,234 @@ +/* + * (C) Copyright 2007 + * Larry Johnson, lrj(a)acm.org + * + * based on rtc/m41t11.c which is ... + * + * (C) Copyright 2002 + * Andrew May, Viasat Inc, amay(a)viasat.com + * + * This program is free software; you can redistribute it and/or + * modify it under the terms of the GNU General Public License as + * published by the Free Software Foundation; either version 2 of + * the License, or (at your option) any later version. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, + * MA 02111-1307 USA + */ + +/* + * STMicroelectronics M41T60 serial access real-time clock + */ + +/* #define DEBUG 1 */ + +#include <common.h> +#include <command.h> +#include <rtc.h> +#include <i2c.h> + +#if defined(CONFIG_RTC_M41T60) && defined(CFG_I2C_RTC_ADDR) && \ + (CONFIG_COMMANDS & CFG_CMD_DATE) + +static unsigned bcd2bin(uchar n) +{ + return ((((n >> 4) & 0x0F) * 10) + (n & 0x0F)); +} + +static unsigned char bin2bcd(unsigned int n) +{ + return (((n / 10) << 4) | (n % 10)); +} + +/* + Convert between century and "century bits" (CB1 and CB0). These + routines assume years are in the range 1900 - 2299. +*/ + +static unsigned char year2cb(unsigned const year) +{ + if (year < 1900 || year >= 2300) { + printf("M41T60 RTC: year %d out of range\n", year); + } + return (year / 100) & 0x3; +} + +static unsigned cb2year(unsigned const cb) +{ + return 1900 + 100 * ((cb + 1) & 0x3); +} + +/* + * These are simple defines for the chip local to here so they aren't too + * verbose. DAY/DATE aren't nice but that is how they are on the data sheet. + */ +#define RTC_SEC 0x0 +#define RTC_MIN 0x1 +#define RTC_HOUR 0x2 +#define RTC_DAY 0x3 +#define RTC_DATE 0x4 +#define RTC_MONTH 0x5 +#define RTC_YEARS 0x6 + +#define RTC_REG_CNT 7 + +#define RTC_CTRL 0x7 + +#if defined(DEBUG) +static void rtc_dump(char const *const label) +{ + uchar data[8]; + + if (i2c_read(CFG_I2C_RTC_ADDR, 0, 1, data, sizeof(data))) { + printf("I2C read failed in rtc_dump()\n"); + return; + } + printf("RTC dump %s: %02X-%02X-%02X-%02X-%02X-%02X-%02X-%02X\n", + label, data[0], data[1], data[2], data[3], + data[4], data[5], data[6], data[7]); +} +#else /* !defined(DEBUG) */ +#define rtc_dump(label) +#endif /* defined(DEBUG) */ + +static uchar *rtc_validate(void) +{ + static const uchar daysInMonth[0x13] = { + 0x00, 0x31, 0x29, 0x31, 0x30, 0x31, 0x30, 0x31, + 0x31, 0x30, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, + 0x31, 0x30, 0x31 + }; + static uchar data[8]; + uchar min, date, month, years; + + rtc_dump("begin validate"); + if (i2c_read(CFG_I2C_RTC_ADDR, 0, 1, data, sizeof(data))) { + printf("I2C read failed in rtc_validate()\n"); + return 0; + } + /* + * If the OUT bit is "1", there has been a loss of power, then stop the + * oscillator is it will be "kick-started". + */ + if (0x00 != (data[RTC_CTRL] & 0x80)) { + printf("M41T60 RTC clock lost power.\n"); + data[RTC_SEC] = 0x80; + if (i2c_write(CFG_I2C_RTC_ADDR, RTC_SEC, 1, data, 1)) { + printf("I2C write failed in rtc_validate()\n"); + return 0; + } + } + /* + * If the ocsillator is stopped or the date is invalid, then set the OUT + * bit to "1", reset the date registers, and start the oscillator. + */ + min = data[RTC_MIN] & 0x7F; + date = data[RTC_DATE]; + month = data[RTC_MONTH] & 0x3F; + years = data[RTC_YEARS]; + if (0x59 < data[RTC_SEC] || 0x09 < (data[RTC_SEC] & 0x0F) || + 0x59 < min || 0x09 < (min & 0x0F) || + 0x23 < data[RTC_HOUR] || 0x09 < (data[RTC_HOUR] & 0x0F) || + 0x07 < data[RTC_DAY] || 0x00 == data[RTC_DAY] || + 0x12 < month || + 0x99 < years || 0x09 < (years & 0x0F) || + daysInMonth[month] < date || 0x09 < (date & 0x0F) || 0x00 == date || + (0x29 == date && 0x02 == month && + ((0x00 != (years & 0x03)) || + (0x00 == years && 0x00 != (data[RTC_MONTH] & 0xC0))))) { + printf("Resetting M41T60 RTC clock.\n"); + /* + * Set to 00:00:00 1900-01-01 (Monday) + */ + data[RTC_SEC] = 0x00; + data[RTC_MIN] = 0x00; + data[RTC_HOUR] = 0x00; + data[RTC_DAY] = 0x02; + data[RTC_DATE] = 0x01; + data[RTC_MONTH] = 0xC1; + data[RTC_YEARS] = 0x00; + data[RTC_CTRL] &= 0x7F; + } + if (i2c_write(CFG_I2C_RTC_ADDR, 0, 1, data, sizeof(data))) { + printf("I2C write failed in rtc_validate()\n"); + return 0; + } + return data; +} + +void rtc_get(struct rtc_time *tmp) +{ + uchar const *const data = rtc_validate(); + + if (!data) { + return; + } + tmp->tm_sec = bcd2bin(data[RTC_SEC] & 0x7F); + tmp->tm_min = bcd2bin(data[RTC_MIN] & 0x7F); + tmp->tm_hour = bcd2bin(data[RTC_HOUR] & 0x3F); + tmp->tm_mday = bcd2bin(data[RTC_DATE] & 0x3F); + tmp->tm_mon = bcd2bin(data[RTC_MONTH] & 0x1F); + tmp->tm_year = cb2year(data[RTC_MONTH] >> 6) + bcd2bin(data[RTC_YEARS]); + tmp->tm_wday = bcd2bin(data[RTC_DAY] & 0x07) - 1; + tmp->tm_yday = 0; + tmp->tm_isdst = 0; + + debug("Get DATE: %4d-%02d-%02d (wday=%d) TIME: %2d:%02d:%02d\n", + tmp->tm_year, tmp->tm_mon, tmp->tm_mday, tmp->tm_wday, + tmp->tm_hour, tmp->tm_min, tmp->tm_sec); +} + +void rtc_set(struct rtc_time *tmp) +{ + uchar *const data = rtc_validate(); + + if (!data) { + return; + } + data[RTC_SEC] &= 0x80; + data[RTC_MIN] &= 0X80; + + debug("Set DATE: %4d-%02d-%02d (wday=%d) TIME: %2d:%02d:%02d\n", + tmp->tm_year, tmp->tm_mon, tmp->tm_mday, tmp->tm_wday, + tmp->tm_hour, tmp->tm_min, tmp->tm_sec); + + data[RTC_SEC] |= bin2bcd(tmp->tm_sec) & 0x7F; + data[RTC_MIN] |= bin2bcd(tmp->tm_min) & 0X7F; + data[RTC_HOUR] = bin2bcd(tmp->tm_hour) & 0x3F; + data[RTC_DATE] = bin2bcd(tmp->tm_mday) & 0x3F; + data[RTC_MONTH] = bin2bcd(tmp->tm_mon) & 0x1F; + data[RTC_YEARS] = bin2bcd(tmp->tm_year % 100); + data[RTC_MONTH] |= year2cb(tmp->tm_year) << 6; + data[RTC_DAY] = bin2bcd(tmp->tm_wday + 1) & 0x07; + if (i2c_write(CFG_I2C_RTC_ADDR, 0, 1, data, RTC_REG_CNT)) { + printf("I2C write failed in rtc_set()\n"); + return; + } +} + +void rtc_reset(void) +{ + uchar *const data = rtc_validate(); + + if (!data) { + return; + } + rtc_dump("begin reset"); + /* + * Turn off frequency test. + */ + data[RTC_CTRL] &= 0xBF; + if (i2c_write(CFG_I2C_RTC_ADDR, RTC_CTRL, 1, data + RTC_CTRL, 1)) { + printf("I2C write failed in rtc_reset()\n"); + return; + } + rtc_dump("end reset"); +} +#endif /* CONFIG_RTC_M41T60 && CFG_I2C_RTC_ADDR && CFG_CMD_DATE */ diff -Naur a/rtc/Makefile b/rtc/Makefile --- a/rtc/Makefile 2007-06-12 08:23:00.000000000 -0400 +++ b/rtc/Makefile 2007-06-16 11:46:11.000000000 -0400 @@ -31,7 +31,8 @@ bf5xx_rtc.o ds12887.o ds1302.o ds1306.o ds1307.o \ ds1337.o ds1374.o ds1556.o ds164x.o ds174x.o ds3231.o \ m41t11.o max6900.o m48t35ax.o mc146818.o mk48t59.o \ - mpc5xxx.o mpc8xx.o pcf8563.o s3c24x0_rtc.o rs5c372.o + mpc5xxx.o mpc8xx.o pcf8563.o s3c24x0_rtc.o rs5c372.o \ + m41t60.o SRCS := $(COBJS:.o=.c) OBJS := $(addprefix $(obj),$(COBJS))

2 2

[U-Boot-Users] [PATCH] First draft of an kconfig based configuration system.
by Carsten Schlote 20 Jun '07

20 Jun '07

Hallo, While waiting for my computers to compile stuff, I added a first draft of an kconfig based config system to U-Boot and created some dummy Config.in files, so everyone can get an impression how things could look like. I cloned kconfig from BusyBox. Most changes were done to the makefiles. Feedback is welcomed. The provided configuration dummies are just an example. How should a real-life kconfig configuration look like? How should it be structured? The git patch is about 680kB and available on http://www.vahanus.net/~csc/0001-kconfig-Add-first-draft-framework-for-a -kconfig-ba.patch Regards Carsten ____________ Virus checked by G DATA AntiVirusKit Version: AVKA 17.248 from 15.06.2007 ____________ Virus checked by G DATA AntiVirus Version: AVKB 17.268 from 20.06.2007 Virus news: www.antiviruslab.com

1 0

[U-Boot-Users] What is x-loader?
by arun c 20 Jun '07

20 Jun '07

Hi all, My aim is to port linux to omap2430SDP with pop memory processor board.I want to use U-boot as my bootloader. But i came to know that it requires one more thing called X-loader. I don't understand why it need X-loader other than U-boot. My board is having pop memory thats why X-loader is needed? Does anybody here know the answer please help me. It will be a great help to me if somebody is giving me a brief idea about "how to port U-boot to a omap2430 processor with pop memory?". Thanks in advance arun

2 1

[U-Boot-Users] a problem of rtl8019.c
by buaafree 20 Jun '07

20 Jun '07

Hi,all I have a board with cpu-s3c2410,eth controller-realtek8019as.I found the function nic_to_pc() in ~/u-boot-1.2.0/drivers/rtl8019.c with a mistake.If using the following way rec_head_status = get_reg (RTL8019_DMA_DATA); next_packet_pointer = get_reg (RTL8019_DMA_DATA); packet_length0 = get_reg (RTL8019_DMA_DATA); packet_length1 = get_reg (RTL8019_DMA_DATA); for reading receive buffer,the four variable of "rec_head_status next_packet_pointer packet_length0 packet_length1" can't get correct value.But if reading the four bytes by using one array to store,it's ok.In other words,it's wrong,if storing every byte in an individual variable. Who can tell me why? Thanks! Darren buaafree 2007-06-20

1 0