u-boot mbx860
Dear Amit, in message you wrote: > > Data Size:1333838 Bytes = 1302.58 kB = 1.27 MB > => tftp 2 ppc.img 0x2 = 128 kB. There is not enough room to copy 1.27 MB. Try: => tftp 20 ppc.img Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de "Beware of programmers carrying screwdrivers." - Chip Salzenberg ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
u-boot on mbx860
Dear Amit, in message you wrote: > > I have compiled u-boot for mbx860, created uImage (using the sources from > denx site) but have > a problem when I try to run the uImge on the board, follows what I get: ... > => bootm 0x2 > ## Booting image at 0002 ... >Image Name: Linux-2.4.20 >Image Type: PowerPC Linux Kernel Image (gzip compressed) >Data Size:842305 Bytes = 822.6 kB Compressed size is 800+ kB, so uncompressed size will be around 2+ MB. >Load Address: >Entry Point: >Verifying Checksum ... OK >Uncompressing Kernel Image ... Error: inflate() returned -3 You load the image at 0x2 = 128 kB. It will overwrite itself when it starts to uncompress and load the kernel. Use a higher download address, like 0x20. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de "We don't have to protect the environment -- the Second Coming is at hand." - James Watt ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
using bdi2000 to debug ppcboot on mpc7455
In message <005e01c383f2$65430080$2a21a8c0 at qha> you wrote: > > Thanks a lot for your very informative reply; it helped me greatly and I > can finally play with breakpoints. Although I failed to set the > breakpoint at after_reloc but the point right before boart_init_r. For debugging U-Boot / PPCBoot after relocation see http://www.denx.de/twiki/bin/view/DULG/DebuggingUBoot#Section_9.1.2. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de Heavier than air flying machines are impossible. -- Lord Kelvin, President, Royal Society, c. 1895 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
using bdi2000 to debug ppcboot on mpc7455
In message <16242.64239.133401.668446 at waldo.lisle.iphase.com> you wrote: > > In addition to the issue Mark pointed out, you can't use soft > breakpoints while you are running from ROM which is the common case > for the early init parts of U-Boot. > > Also, once U-Boot has relocated itself, you need to identify the new > base address and inform gdb of the new load address. And not to forget that, in the very early startup code (like the symbol "boot_cold" mentioned by Q-ha Park), the memory controller is still running in the reset configuration, i. e. the PC will still point to the reset vector area (0x'01xx or 0xFFF0'01xx), and NOT yet to the addresses in the U-Boot symbol table. Only after "in_flash" the symbols are correct. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de "A little knowledge is a dangerous thing."- Doug Gwyn ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Operating system question
Hi All, I have a question withregards WIMG MMU settings of page tables / BATs. Is there any reason why setting the M bit (coherency) on an IO region (cache inhibited and guarded) ? Does anyone expect what is the result of doing so ? I'v seen in the Linux code for PPC that on IO region the M bit is never set - but what about firmwares ? other operating system ? Thank you, Rabeeh ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
8260 FCC enet driver problem
Hi, I use a 2.4.18 Linux kernel on my custom 8260 board with 3 FCC ports. These 3 ports work fine at 100Mbs half or full duplex. I connect 2 boards on the first port via a 10Mbs hub. The ports auto-negotiate and fall into 10Mbs half duplex mode. A board sends short udp messages as fast as possible to the other one and vice-versa. I get the following message and the two ports are locked forever : > NETDEV WATCHDOG: eth0: transmit timed out > eth0: transmit timed out. > Ring data dump: cur_tx c0164220 (full) cur_rx c01641e8. > Tx @base c0164208 : > 9c00 0048 018d1ee2 > 9c00 0048 018d15e2 > 9c00 0048 018d1ae2 The PHY devices seem to be well configured. Does anyone know what are the conditions to fall into this trap ? Is it a PHY problem, a driver configuration problem or something else ? Why does the problem not disappear when the traffic is interrupted ? Only a board reset can reactivate the ports. Thank you for your help. G?rard ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC823 and LCD?
>-- Original Message -- >Date: Mon, 29 Sep 2003 17:51:49 +0200 >From: Steven Scholz >To: Linuxppc-Embedded >Subject: MPC823 and LCD? > > > >Hi there, > >two questions about MPC823 and LCD: > >1. Has someone a working driver for linux > 2.4.20? It'm not sure if we have already ported over our LCD drivers from 2.4.4 to 2.4.20 but Wolfgang can clarify this, I think. >2. what's the difference between lcd823.c and video823.c in linux-2.4.4 from >DENX? The MPC823 has an interface for LCD displays but also for video monitors (NTSC/PAL) through a video encoder, typically a AD7176/7/9. Please have a look to the processor manual for further information. Wolfgang. Wolfgang ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC10x I2C driver update
On Tue, Sep 30, 2003 at 10:43:55AM +0100, Adrian Cox wrote: > I have released a small update to my driver for the > MPC107/MPC8240/MPC8245 I2C adapter. This corrects a bug reported by > several people: the transfer function now follows the other I2C > algorithm drivers by returning the number of elements transferred. > > http://www.humboldt.co.uk/mpc10xi2c.html > > I'd like to get this into the kernel. Which would be more useful to > people: > 1) Getting it into lm-sensors? > 2) Getting it into linuxppc-2.4-devel? 3) sending me a patch to get it into the 2.6 kernel tree. :) thanks, greg k-h ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC823 and LCD?
Steven, >> 1. Has someone a working driver for linux > 2.4.20? > check out drivers/video/rpxfb.c Thanks for that hint. Is this driver in any way special to RPX boards? Or could we make it available to other MPC823 boards as well? IIRC the lcd823.c driver in DENX kernel is quite generic. Thanks, Steven ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
can't find "init" when using 1GB ram on 7455.
I had almost the exact same problem on the ev64260 platform with 1GB of memory. Tak a look and make sure you are not doing any io_block_mapping() calls in your platform setup functions. You might have one for early serial messages. Look at the mapping and make sure it does not overlap. You might have to reduce the io_block_mapping() size. Just a thought Thanks Brian On Tuesday 30 September 2003 11:44 am, Q-ha Park wrote: > Well, actually not just init but all "start" programs such as modprobe, > bash, etc. Linux uses NFS as its filesystem, and kernel thinks NFS is > mounted correctly, but it doesn't successfully find and execute "start" > programs like sh, init, etc. The system that works well with 512MB ram. > > This is what I attempted to support two 512 MB DIMM rams: > 1. use 2 more BATs to translate up to 0x4000 (1GB) in ppcboot, > changed CFG_INIT_RAM to 0x4000 accordingly. > 2. enable high_mem support in the kernel. > > When I made the system load the kernel w/o high_mem support > intentionally, UART doens't work anymore; it doesn't generate interrups. > Any clues on what might be wrong and what idiotic things I might have > done? > > Thanks in advance! > > > Q-ha Park > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC823 and LCD?
Steven Scholz wrote: > Is this driver in any way special to RPX boards? > Or could we make it available to other MPC823 boards as well? H.interesting how the driver I wrote becomes MV copyrighted... Oh well. There isn't anything uniqe to the RPX boards in the driver, only the LCD type. The original one had some backlight/touchscreen stuff in it, but I see that is gone now. The lcd driver is for an LCD screen, the video driver is for YUV mode composite/S-Video output. -- Dan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
UART prints very slow
Interrupt problem. Double check the irq you specified in the uart setup stuff. Mark -- Yuxiao Xi wrote: >Hello,all, >I am developing my board with CPU MPC8240 and a UART ST16C2552. >I use MontaVista Linux 2.1. Now I have successfully logged in the >shell.But there is a question that I can't resolve:( I am sure that the >UART is successfully initialized except that ST16C2552 is detected as >ST16650.I debugged the UART interrupt and the printk info showed that it >was OK. > >QUESTION: when I input commands such as 'ls', 'cd /dev' on the shell, >the characters of these commands are printed very slow on the screen >and the command execution results as well. I think these commands and >their execution results are printed through UART interrupt.Is MPC8240 >interrupt ACK so slow? BTW: while system booting,the UART prints very >quickly in polling print mode. > >Yuxiao Xi >xiyuxiao at harbournetworks.com >2003-09-30 > > > > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Problem of concurrency in arch/ppc/8260_io/uart.c
Tom Rini wrote: > KGDB still works for me. Dan, happy with this? Go for it. Thanks. -- Dan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
u-boot on mbx860
Hi, I have compiled u-boot for mbx860, created uImage (using the sources from denx site) but have a problem when I try to run the uImge on the board, follows what I get: create u-boot image --- [devel at amit_lap linuxppc_2_4_devel]$ make uImage . scripts/mkversion > .tmpversion dnsdomainname: Unknown host ppc_8xx-gcc -D__KERNEL__ -I/home/devel/mbx860/linuxppc_2_4_devel/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -I/home/devel/mbx860/linuxppc_2_4_devel/arch/ppc -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -DUTS_MACHINE='"ppc"' -DKBUILD_BASENAME=version -c -o init/version.o init/version.c ... make[1]: Entering directory `/home/devel/mbx860/linuxppc_2_4_devel/arch/ppc/boot' make -C images vmlinux.gz make[2]: Entering directory `/home/devel/mbx860/linuxppc_2_4_devel/arch/ppc/boot/images' ppc_8xx-objcopy --strip-all -S -O binary /home/devel/mbx860/linuxppc_2_4_devel/vmlinux vmlinux gzip -vf9 vmlinux vmlinux: 57.0% -- replaced with vmlinux.gz make[2]: Leaving directory `/home/devel/mbx860/linuxppc_2_4_devel/arch/ppc/boot/images' ./utils/mkimage.wrapper -A ppc -O linux -T kernel -C gzip -a -e \ -n 'Linux-2.4.20' \ -d images/vmlinux.gz images/vmlinux.PPCBoot Image Name: Linux-2.4.20 Created: Tue Sep 30 11:50:22 2003 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:842305 Bytes = 822.56 kB = 0.80 MB Load Address: 0x Entry Point: 0x ln -sf vmlinux.PPCBoot images/pImage ln -sf vmlinux.PPCBoot images/uImage make[1]: Leaving directory `/home/devel/mbx860/linuxppc_2_4_devel/arch/ppc/boot' load the uImage to the mbx board => U-Boot 0.4.8 (Sep 18 2003 - 17:29:19) CPU: XPC86xxxZPnnC1 at 50 MHz: 4 kB I-Cache 4 kB D-Cache Board: MBX860-006C860EN(01-W3527F31C) *** Warning: Low Battery Status - On-Board Battery *** DRAM: 16 MB FLASH: 8 MB In:serial Out: serial Err: serial Net: SCC ETHERNET PCMCIA: No Card found => tftp 0x2 uImage TFTP from server 192.168.15.18; our IP address is 192.168.15.34 Filename 'uImage'. Load address: 0x2 Loading: # # ### done Bytes transferred = 842369 (cda81 hex) => bootm 0x2 ## Booting image at 0002 ... Image Name: Linux-2.4.20 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:842305 Bytes = 822.6 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... Error: inflate() returned -3 GUNZIP ERROR - must RESET board to recover U-Boot 0.4.8 (Sep 18 2003 - 17:29:19) CPU: XPC86xxxZPnnC1 at 50 MHz: 4 kB I-Cache 4 kB D-Cache Board: MBX860-006C860EN(01-W3527F31C) *** Warning: Low Battery Status - On-Board Battery *** DRAM: 16 MB FLASH: 8 MB In:serial Out: serial Err: serial Net: SCC ETHERNET PCMCIA: No Card found => Any idea what is wrong ? Thanks, Amit. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC10x I2C driver update
I have released a small update to my driver for the MPC107/MPC8240/MPC8245 I2C adapter. This corrects a bug reported by several people: the transfer function now follows the other I2C algorithm drivers by returning the number of elements transferred. http://www.humboldt.co.uk/mpc10xi2c.html I'd like to get this into the kernel. Which would be more useful to people: 1) Getting it into lm-sensors? 2) Getting it into linuxppc-2.4-devel? - Adrian Cox http://www.humboldt.co.uk/ ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Controlling output pin
Hi all, I once found a small example somewhere which used an output pin of the P1 connector of the EP405 board. It just outputted a square wave. Now, I don't find it anymore, and I like to get it back, because it's the perfect start for a kernel module I need to write. Perhaps anybody else have another example on how to use an output directly. The target of my module: * generate 2 PWM signals on 2 output pins. * do this all in real time (with RTAI). I rather start from an example, than start from scratch (because I never dealt with direct pin control before). So, if anybody van help me out with this, it's much appreciated. -- Toni Van Remortel Wetenschappelijk Medewerker - D-science lab Real time Linux for embedded systems: http://linemb.d-sciencelab.com Tel: +32 3 205 61 72 - Fax: +32 3 205 61 95 E-mail: t.vanremortel at ha.be ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
UART prints very slow
Hello,all, I am developing my board with CPU MPC8240 and a UART ST16C2552. I use MontaVista Linux 2.1. Now I have successfully logged in the shell.But there is a question that I can't resolve:( I am sure that the UART is successfully initialized except that ST16C2552 is detected as ST16650.I debugged the UART interrupt and the printk info showed that it was OK. QUESTION: when I input commands such as 'ls', 'cd /dev' on the shell, the characters of these commands are printed very slow on the screen and the command execution results as well. I think these commands and their execution results are printed through UART interrupt.Is MPC8240 interrupt ACK so slow? BTW: while system booting,the UART prints very quickly in polling print mode. Yuxiao Xi xiyuxiao at harbournetworks.com 2003-09-30 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
AW: AW: AW: compact flash
The IO address depends on your memory map! Please have a look @ www.denx.de ! @ denx u can download a kernel. The MPC860 is supported there. Read the manuals e.g the DULG document(they are very good!) cheers Alex -Urspr?ngliche Nachricht- Von: somshekar chandrashekar kadam [mailto:som_kadam1 at rediffmail.com] Gesendet: Dienstag, 30. September 2003 08:01 An: Graf Alex Cc: linuxppc-embedded at lists.linuxppc.org Betreff: Re: AW: AW: compact flash Hi Alex , what do get this ATTRIBUTE address , IO address DMA ADDRESS with respect to CF , where do i get this info i know the MEM_ADDR in my memory map others i dont have any idea , where should i get it from Thanks In Advance SOm On Mon, 29 Sep 2003 Graf Alex wrote : > >do i need to first detect it on my PPCBOOT , or can I make it >DETECT directly from LINUX > >> it depends on what u want. >If u want only IDE support, no hotplug, u have to setup the >PCMCIA registers >in ppcboot. The driver/pcmcia/ide-m8xx.c reads out the PCMCIA >register and >remaps the io windows for IDE access. This is the simple way and >it works >with www.denx.de ELDK. >for hotplug, the register setup (for linux) is in >driver/pcmcia/m8xx_pcmcia.c. U can set up the PCMCIA registers >for ppcboot, >but it's not necesary. Then u need the pcmcia-cs package. This is >the tricky >way and, depends on ur kernel, is not supported on all kernel >versions! > >cheers > >Alex Graf > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC823 and LCD?
It should work on all 823E boards. Specific support for your LCD may be required. -Original Message- From: Steven Scholz [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 7:18 AM To: Steven Blakeslee Cc: Linuxppc-Embedded Subject: Re: MPC823 and LCD? Steven, >> 1. Has someone a working driver for linux > 2.4.20? > check out drivers/video/rpxfb.c Thanks for that hint. Is this driver in any way special to RPX boards? Or could we make it available to other MPC823 boards as well? IIRC the lcd823.c driver in DENX kernel is quite generic. Thanks, Steven ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
AW: AW: compact flash
An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20030930/a552f0a7/attachment.txt
AW: AW: compact flash
An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20030930/26142593/attachment.txt
