October 2003 - U-Boot

[U-Boot-Users] PQ2VADS (8270) & BDI2000 - III
by Matias Sundman (AL/EAB) 21 Oct '03

21 Oct '03

Hi, I tried to flash the u-boot.bin file to 0xff900000 and 0xff800000 but I cant get anything on the console ... am I missing some steps? I made the following steps: 1. Edited the MPC8260ADS.h file in order to set CFG_PQ2FADS as the target board ... 2. make MPC8260ADS_config 3. make clean 4. make all 5. Flashed area 0xff900000 and restarted the board No output on the console ... 6. Flashed area 0xff800000 and restarted the board No output on the console ... Any ideas? Cheers // Matias =========================================================================== -----Original Message----- From: Matias Sundman (AL/EAB) Sent: den 21 oktober 2003 10:24 To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] PQ2VADS (8270) & BDI2000 - II Hello again, I have now received a BDI2000 from Abatron. There is a configuration file included with the package for my target board, which is - PQ2FADS. U-boot is compiled with the CFG_PQ2FADS define in the MPC8260ADS.h file. Can I use the configuration file as is and burn u-boot.bin to the flash, and after a restart of the board I get a working u-boot automagically? Regards // Matias ------------------------------------------------------------------------- -----Original Message----- From: Chris Simmonds [mailto:chris@2net.co.uk] Sent: den 6 oktober 2003 10:45 To: Matias Sundman (TB/EAB) Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] PQ2VADS (8270) & BDI2000 Hi, I am using BDI2000 with an 8270 right now and it works fine. Its just the standard package for ppc 6xx/7xx/82xx/7400/7410. I used the configuration file for the vads8260 and fixed it up for my board (a custom unit). I don't have a config for the pq2vads board I'm afraid. Chris. Matias Sundman (TB/EAB) wrote: >Comrades, >I have compiled uboot for the PQ2VADS Motorola >evaluation board and tried to flash it with a >JTAG probe from GreenHills. Unfortunately their >probe does not support the 8270 architecture today. > >Does BDI2000 support the ppc8270 JTAG chain architecture? > >If so , does someone have a configuration file for the >PQ2VADS Motorola evaluation board? > >Best Regards // Matias > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >U-Boot-Users mailing list >U-Boot-Users(a)lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/u-boot-users > -- Chris Simmonds 2net Limited chris(a)2net.co.uk http://www.2net.co.uk/ Tel: +44 (0)1962 869003 Fax: +44 (0)870 056 7556 "If it's not connected, it's not effective"(tm) ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

2 1

[U-Boot-Users] I have a mistake on making u-boot-0.4.0
by Dannel_Zhang 21 Oct '03

21 Oct '03

Hi all, I am working intel xscale pxa255 based board. I have a mistake on makeing u-boot-0.4.0,The erro information message as follow. who would please give me some ideas please? pt/u-boot/tools' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/tools' make[1]: Entering directory `/opt/u-boot/lib_generic' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/lib_generic' make[1]: Entering directory `/opt/u-boot/lib_arm' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/lib_arm' make[1]: Entering directory `/opt/u-boot/cpu/pxa' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/cpu/pxa' make[1]: Entering directory `/opt/u-boot/board/lubbock' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/board/lubbock' make[1]: Entering directory `/opt/u-boot/common' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/common' make[1]: Entering directory `/opt/u-boot/disk' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/disk' make[1]: Entering directory `/opt/u-boot/fs' make[2]: Entering directory `/opt/u-boot/fs/jffs2' make[2]: `.depend' is up to date. make[2]: Leaving directory `/opt/u-boot/fs/jffs2' make[2]: Entering directory `/opt/u-boot/fs/fdos' make[2]: `.depend' is up to date. make[2]: Leaving directory `/opt/u-boot/fs/fdos' make[2]: Entering directory `/opt/u-boot/fs/fat' make[2]: `.depend' is up to date. make[2]: Leaving directory `/opt/u-boot/fs/fat' make[1]: Leaving directory `/opt/u-boot/fs' make[1]: Entering directory `/opt/u-boot/net' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/net' make[1]: Entering directory `/opt/u-boot/rtc' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/rtc' make[1]: Entering directory `/opt/u-boot/dtt' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/dtt' make[1]: Entering directory `/opt/u-boot/drivers' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/drivers' make[1]: Entering directory `/opt/u-boot/post' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/post' make[1]: Entering directory `/opt/u-boot/post/cpu' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/post/cpu' make[1]: Entering directory `/opt/u-boot/examples' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/examples' make[1]: Entering directory `/opt/u-boot/tools' gcc -g -Wall -pedantic -I../include -I.. -DTEXT_BASE=0xa3000000 -DUSE_HOSTCC -O -c envcrc.c gcc -g -I../include -I.. -DTEXT_BASE=0xa3000000 -DUSE_HOSTCC -c environment.c gcc -Wall -pedantic -I../include -I.. -DTEXT_BASE=0xa3000000 -DUSE_HOSTCC -O -o envcrc envcrc.o crc32.o environment.o make[2]: Entering directory `/opt/u-boot/tools/gdb' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/opt/u-boot/tools/gdb' make[1]: Leaving directory `/opt/u-boot/tools' make[1]: Entering directory `/opt/u-boot/lib_generic' arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o crc32.o crc32.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o display_options.o display_options.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o vsprintf.o vsprintf.c arm-linux-ar crv libgeneric.a crc32.o ctype.o display_options.o ldiv.o string.o vsprintf.o zlib.o r - crc32.o r - ctype.o r - display_options.o r - ldiv.o r - string.o r - vsprintf.o r - zlib.o make[1]: Leaving directory `/opt/u-boot/lib_generic' make[1]: Entering directory `/opt/u-boot/lib_arm' arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o armlinux.o armlinux.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o board.o board.c arm-linux-ar crv libarm.a _udivsi3.o _umodsi3.o armlinux.o board.o cache.o div0. o r - _udivsi3.o r - _umodsi3.o r - armlinux.o r - board.o r - cache.o r - div0.o make[1]: Leaving directory `/opt/u-boot/lib_arm' make[1]: Entering directory `/opt/u-boot/cpu/pxa' arm-linux-gcc -Wa,-gstabs -D__ASSEMBLY__ -g -Os -fno-strict-aliasing -fno-co mmon -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000 000 -I/opt/u-boot/include -fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib /gcc-lib/arm-linux/3.2.1/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march= armv4 -mtune=strongarm1100 -c -o start.o /opt/u-boot/cpu/pxa/start.S /opt/u-boot/cpu/pxa/start.S: Assembler messages: /opt/u-boot/cpu/pxa/start.S:145: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:146: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:160: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:167: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:169: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:381: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:382: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:387: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:388: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:393: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:394: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:399: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:400: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:405: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:406: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:429: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:430: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:435: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:436: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up make[1]: *** [start.o] Error 1 make[1]: Leaving directory `/opt/u-boot/cpu/pxa' make: *** [subdirs] Error 1 Thanks & Regards, Dannel Zhang

1 0

[U-Boot-Users] Maintainer of AT91RM9200DK???
by Steven Scholz 21 Oct '03

21 Oct '03

Hi there, who considers himself as the U-Boot maintainer of the AT91RM9200 cpu and the AT91RM9200DK eval board? Rick, is that you? I just porting U-Boot to our AT91RM9200 based board and it migth be necessary to change some code in the AT91RM9200 relevant stuff. So I am looking for people to talk to before that. Thanks a million. Steven

4 6

[U-Boot-Users] PQ2VADS (8270) & BDI2000 - II
by Matias Sundman (AL/EAB) 21 Oct '03

21 Oct '03

Hello again, I have now received a BDI2000 from Abatron. There is a configuration file included with the package for my target board, which is - PQ2FADS. U-boot is compiled with the CFG_PQ2FADS define in the MPC8260ADS.h file. Can I use the configuration file as is and burn u-boot.bin to the flash, and after a restart of the board I get a working u-boot automagically? Regards // Matias ------------------------------------------------------------------------- -----Original Message----- From: Chris Simmonds [mailto:chris@2net.co.uk] Sent: den 6 oktober 2003 10:45 To: Matias Sundman (TB/EAB) Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] PQ2VADS (8270) & BDI2000 Hi, I am using BDI2000 with an 8270 right now and it works fine. Its just the standard package for ppc 6xx/7xx/82xx/7400/7410. I used the configuration file for the vads8260 and fixed it up for my board (a custom unit). I don't have a config for the pq2vads board I'm afraid. Chris. Matias Sundman (TB/EAB) wrote: >Comrades, >I have compiled uboot for the PQ2VADS Motorola >evaluation board and tried to flash it with a >JTAG probe from GreenHills. Unfortunately their >probe does not support the 8270 architecture today. > >Does BDI2000 support the ppc8270 JTAG chain architecture? > >If so , does someone have a configuration file for the >PQ2VADS Motorola evaluation board? > >Best Regards // Matias > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >U-Boot-Users mailing list >U-Boot-Users(a)lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/u-boot-users > -- Chris Simmonds 2net Limited chris(a)2net.co.uk http://www.2net.co.uk/ Tel: +44 (0)1962 869003 Fax: +44 (0)870 056 7556 "If it's not connected, it's not effective"(tm)

1 0

[U-Boot-Users] not booting
by Rakesh jagota 21 Oct '03

21 Oct '03

Hi all, I am working on mpc8245 based board. I have compiled the ppcboot with 64MB ram and its working fine and linux is ported successfully. But when I have configured the RAM to 128MB in ppcboot, I am getting the boot prompt and while loading linux its crashing . What can be the reason? Thanks & Regards, rakesh

2 1

[U-Boot-Users] Enhanced SDRAM tests with u-boot
by Thomas Schäfer 21 Oct '03

21 Oct '03

Hi all, I have problems with the Bringup of a custom MPC8280 board and I assume that SDRAM could be the reason. When performing memory tests on the complete SDRAM with the test routines included with u-boot 0.4.5, everything is working fine. Also, u-boot is running without problems. But when booting a (known to work) linux kernel (2.4.18, MontaVista 3.0), I get exceptions after decompressing the kernel (alignment, 0x600) and when executing the initial scripts (program, 0x700). So I would like to perform more sophisticated SDRAM tests with u-boot, including burst tests. Is there anybody who has done this before? Any hints are appreciated. Best regards Thomas Schäfer ____________________________________ GIGA STREAM GmbH Konrad-Zuse-Str. 7 66115 Saarbrücken Tel.: + 49 (0)681 / 95916 - 203 Fax: + 49 (0)681 / 95916 - 100 E-mail: tschaefer(a)giga-stream.de

2 1

RE: [U-Boot-Users] Any *urgent* bug fixes pending?
by Woodruff, Richard 21 Oct '03

21 Oct '03

Wolfgang, Should I wait before sending in device chaining again? There are several other patches, but I haven't had the time to clean them enough to get beyond the entrance threshold. -- the effect useful -- omap_toto # coninfo List of available devices: lcd 00000002 ..O stdout stderr keypad 00000001 .I. stdin touch 00000001 .I. stdin serial 80000003 SIO stdin stdout stderr Regards, Richard W. -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Wolfgang Denk Sent: Monday, October 20, 2003 8:07 AM To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] Any *urgent* bug fixes pending? Hi everybody, getting closer to a 1.0.0 release I would like to verify that there are no _urgent_ bug fixes left. Can you please verify that I checked in all _urgent_ patches / bug fixes sent to me, or that I acknowledged that I will postpone the modifications until after 1.0.0? Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de "The first rule of magic is simple. Don't waste your time waving your hands and hoping when a rock or a club will do." - McCloctnik the Lucid ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

2 1

[U-Boot-Users] MPC8270 Custom Board: Stack Pointer Corruption
by mss59＠att.net 20 Oct '03

20 Oct '03

I am working on an MPC8270 based custom board. u-boot is ported from EP8260 board version. RAM is 128M, flash is 16M. After u-boot relocates code in the ram, sometimes, stack pointer gets corrupted. And sometimes, I get bus fault which overwirtes all u-boot area in the RAM with some pattern like this bus fault 07f6bcd0 : 02001111 07f6be18 07f6bc68 11111111 ...........h.... 07f6bce0 : 42757320 4661756c 74204020 30782020 Bus Fault @ 0x 07f6bcf0 : 20202020 20202020 20202020 20202020 07f6bd00 : 20202020 20202020 20202020 20202020 07f6bd10 : 20202020 20202020 20202020 20202020 07f6bd20 : 20202020 20202020 20202020 20202020 07f6bd30 : 20202020 20202020 20202020 20202020 07f6bd40 : 20202020 20202020 20202020 20202020 07f6bd50 : 20202020 20202020 20202020 20202020 07f6bd60 : 20202020 20202020 20202020 20202020 07f6bd70 : 20202020 20202020 20202020 20202020 07f6bd80 : 20202020 20202020 20202020 20202020 07f6bd90 : 20202020 20202020 20202020 20202020 07f6bda0 : 20202020 20202020 20202020 20202020 07f6bdb0 : 20202020 20202020 20202020 20202020 07f6bdc0 : 20202020 20202020 20202020 20202020 ---> This patters is written till the end of ram. BDImn8270>rd GPR00: 00000000 07f6bbd0 ffdfffff 08000004 GPR04: 00000000 00000010 07f58a9d 00000007 GPR08: 00000001 00000000 00000000 00000007 GPR12: 00000020 00400000 07ffd000 080cc000 GPR16: fffdffff bffdffff ff7fffff fff7ef5f GPR20: 48000002 07f6bad0 00000000 07fcf098 GPR24: 07f6bce0 00000001 07fecdbc 07f6bfb4 GPR28: 07f6bcee 07f6bf70 07ffdcb8 07ff2ed8 CR : 48000002 MSR: 00000000 Any ideas..... Thanks Ravi.

2 1

[U-Boot-Users] 859/866 clock issues
by Nye Liu 20 Oct '03

20 Oct '03

two minor things on the 859/866 1) measure_gclk() is very inaccurate. Better to use the plprcr and CFG_8XX_XIN (which MUST BE 10MHz for that cpu) to derive the "real" bus clock. 2) the 859/866 does NOT support external speeds higher than 66MHz, so if cpu_clk is greater, EBDF01 MUST BE USED IN CFG_SCCR I have a patch for 1, but i no longer have my 859/866 eval board I have no patch for 2, but eventually we should come up with some sort of solution; the 859/866 is almost always configured to run faster than 66MHz. -- Nye Liu nliu(a)mrv.com (818) 772-6235x248 "Who would be stupid enough to quote a fictitious character?" -- Don Quixote

3 3

[U-Boot-Users] Stack Pointer Problem: MPC8270 Custom Board
by mss59＠att.net 20 Oct '03

20 Oct '03

I am working on an MPC8270 based custom board. u-boot is ported from EP8260 board version. RAM is 128M, flash is 16M. After u-boot relocates code in the ram, sometimes, stack pointer gets corrupted. And sometimes, I get bus fault which overwirtes all u-boot area in the RAM with some pattern like this bus fault 07f6bcd0 : 02001111 07f6be18 07f6bc68 11111111 ...........h.... 07f6bce0 : 42757320 4661756c 74204020 30782020 Bus Fault @ 0x 07f6bcf0 : 20202020 20202020 20202020 20202020 07f6bd00 : 20202020 20202020 20202020 20202020 07f6bd10 : 20202020 20202020 20202020 20202020 07f6bd20 : 20202020 20202020 20202020 20202020 07f6bd30 : 20202020 20202020 20202020 20202020 07f6bd40 : 20202020 20202020 20202020 20202020 07f6bd50 : 20202020 20202020 20202020 20202020 07f6bd60 : 20202020 20202020 20202020 20202020 07f6bd70 : 20202020 20202020 20202020 20202020 07f6bd80 : 20202020 20202020 20202020 20202020 07f6bd90 : 20202020 20202020 20202020 20202020 07f6bda0 : 20202020 20202020 20202020 20202020 07f6bdb0 : 20202020 20202020 20202020 20202020 07f6bdc0 : 20202020 20202020 20202020 20202020 ---> This patters is written till the end of ram. BDImn8270>rd GPR00: 00000000 07f6bbd0 ffdfffff 08000004 GPR04: 00000000 00000010 07f58a9d 00000007 GPR08: 00000001 00000000 00000000 00000007 GPR12: 00000020 00400000 07ffd000 080cc000 GPR16: fffdffff bffdffff ff7fffff fff7ef5f GPR20: 48000002 07f6bad0 00000000 07fcf098 GPR24: 07f6bce0 00000001 07fecdbc 07f6bfb4 GPR28: 07f6bcee 07f6bf70 07ffdcb8 07ff2ed8 CR : 48000002 MSR: 00000000 Any ideas..... Thanks Ravi.

2 1