January 2002 - ixp1200 - lists.cs.princeton.edu

Re: Plugging ixp into Pentium's backplane
by Scott C. Karlin 08 Jan '02

08 Jan '02

On Sat, Jan 05, 2002 at 12:12:29AM +0800, Tan Chee Wei wrote: > > >The test against bit 2 of IXP1200_GPIO_DATA > >is a check on jumper J27. The README.jumpers.txt says to set > >J27 to 2-3. Is J27 set correctly? > > Yes, J27 is set correctly. In fact, there isn't any need to change > J27 since the factory's setting is similar to Vera's setting. Some more thoughts... I just opened a factory-fresh development system and the factory setting for J27 was 1-2. Be sure to verify all jumper settings to ensure they are jumpered for the Vera setting. Also, pin 1 for the jumpers is denoted by a square solder pad on the back side of the board. I hope this helps, Scott

1 0

Re: [ixp1200] Re: Plugging ixp into Pentium's backplane
by Vishal Anand 08 Jan '02

08 Jan '02

Hi, When doing th efollowing step in the installation process: cd $VERAROOT/Libsck ; make install I get the following errors: [vanand@localhost Libsck]$ make install make[1]: Entering directory `/home/vanand/study/Vera/Libsck/src' make[2]: Entering directory `/home/vanand/study/Vera/Libsck/src/i386' Updating dependency makefile strlenn.d from strlenn.c gcc: export: No such file or directory Updating dependency makefile strtoule.d from strtoule.c gcc: export: No such file or directory Updating dependency makefile strtoargs.d from strtoargs.c gcc: export: No such file or directory Updating dependency makefile stricmp.d from stricmp.c gcc: export: No such file or directory Updating dependency makefile srec.d from srec.c gcc: export: No such file or directory Updating dependency makefile rmgr.d from rmgr.c gcc: export: No such file or directory ../rmgr.c:19:38: warning: No include path in which to find bit.h ../rmgr.c:20:38: warning: No include path in which to find mem.h ../rmgr.c:21:38: warning: No include path in which to find table.h Updating dependency makefile mrm.d from mrm.c gcc: export: No such file or directory ../mrm.c:21:38: warning: No include path in which to find mem.h Updating dependency makefile lineproc.d from lineproc.c gcc: export: No such file or directory make[2]: Leaving directory `/home/vanand/study/Vera/Libsck/src/i386' make[2]: Entering directory `/home/vanand/study/Vera/Libsck/src/i386' gcc -I. -I.. -I/home/vanand/study/Vera export -IXCCROOT=/usr/xcc/Libcii/include -Wall -Wstrict-prototypes -O2 -c lineproc.c -o lineproc.o gcc: cannot specify -o with -c or -S and multiple compilations make[2]: *** [lineproc.o] Error 1 make[2]: Leaving directory `/home/vanand/study/Vera/Libsck/src/i386' make[2]: Entering directory `/home/vanand/study/Vera/Libsck/src/arm' Updating dependency makefile strlenn.d from strlenn.c arm-unknown-coff-gcc: export: No such file or directory arm-unknown-coff-gcc: export: No such file or directory Updating dependency makefile strtoule.d from strtoule.c arm-unknown-coff-gcc: export: No such file or directory arm-unknown-coff-gcc: export: No such file or directory Updating dependency makefile strtoargs.d from strtoargs.c arm-unknown-coff-gcc: export: No such file or directory arm-unknown-coff-gcc: export: No such file or directory Updating dependency makefile stricmp.d from stricmp.c arm-unknown-coff-gcc: export: No such file or directory arm-unknown-coff-gcc: export: No such file or directory Updating dependency makefile srec.d from srec.c arm-unknown-coff-gcc: export: No such file or directory arm-unknown-coff-gcc: export: No such file or directory Updating dependency makefile rmgr.d from rmgr.c arm-unknown-coff-gcc: export: No such file or directory arm-unknown-coff-gcc: export: No such file or directory ../rmgr.c:19: warning: No include path in which to find bit.h ../rmgr.c:20: warning: No include path in which to find mem.h ../rmgr.c:21: warning: No include path in which to find table.h Updating dependency makefile mrm.d from mrm.c arm-unknown-coff-gcc: export: No such file or directory arm-unknown-coff-gcc: export: No such file or directory ../mrm.c:21: warning: No include path in which to find mem.h Updating dependency makefile log2_floor.d from log2_floor.c arm-unknown-coff-gcc: export: No such file or directory arm-unknown-coff-gcc: export: No such file or directory make[2]: Leaving directory `/home/vanand/study/Vera/Libsck/src/arm' make[2]: Entering directory `/home/vanand/study/Vera/Libsck/src/arm' arm-unknown-coff-gcc -I. -I.. -I/home/vanand/study/Vera export -IXCCROOT=/usr/xcc/Libcii/include -I/home/vanand/study/Vera export -IXCCROOT=/usr/xcc/Libsck/include -nostartfiles -nodefaultlibs -fno-builtin -mcpu=strongarm110 -mapcs-32 -mno-sched-prolog -fvolatile -Wall -Wstrict-prototypes -O2 -c ../log2_floor.c -o log2_floor.o arm-unknown-coff-gcc: cannot specify -o with -c or -S and multiple compilations make[2]: *** [log2_floor.o] Error 1 make[2]: Leaving directory `/home/vanand/study/Vera/Libsck/src/arm' make[1]: *** [install] Error 2 make[1]: Leaving directory `/home/vanand/study/Vera/Libsck/src' make: *** [install] Error 2 ---------------------------------------------------------------------- I did not get any errors when installing in the Libcii, Libesc, Libesc2 dir's Any idea what I am missing in the installation steps. Regards, -Vishal _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx

2 1

Re: Plugging ixp into Pentium's backplane
by Scott C. Karlin 08 Jan '02

08 Jan '02

On Sat, Jan 05, 2002 at 12:12:29AM +0800, Tan Chee Wei wrote: > > > The test against bit 2 of IXP1200_GPIO_DATA > > is a check on jumper J27. The README.jumpers.txt says to set > > J27 to 2-3. Is J27 set correctly? > > Yes, J27 is set correctly. In fact, there isn't any need to change > J27 since the factory's setting is similar to Vera's setting. > But I used the ixp board without using the serial cable connected because > I was concerned whether Pentium will get booted up or not. In that case, > I guess, it is a must to connect up the serial port of the ixp board. At this point I cannot think of another (simple) explanation as to why you would see "16" on the leds without GPIO bit 2 (0x4) being set. There is no requirement that the serial port of the IXP1200 board be connected. However, as you can see, it's more useful to connect it to a different machine so that you can see the output messages even if the host Pentium doesn't boot for some reason. > > If J27 is set to 1-2, the board enters minimon *before* > > initializing the PCI bus. The BIOS will hang because the > > IXP1200 is not responding to the BIOS query. You can verify > > this by checking the serial port output from the ixp1200 board. > > Can I confirm that the mini-monitor in $VERAROOT/Runtime/ixp1200/sa/src/Lib/ > will work with both Window's Hyperterminal as well as linux minimon? Minimon uses no special control codes and will work with any RS-232 terminal or terminal emulator set to 9600 baud, 8 data bits, 1 stop bit, no parity. Scott

1 0

Plugging ixp into Pentium's backplane
by Tan Chee Wei 04 Jan '02

04 Jan '02

Dear Scott, Thank You very much for your prompt reply. Currently, I have successfully compiled all Vera's codes , changed the Intel's firmware to a Princeton's firmware and reset the jumpers' setting according to README.jumpers.txt. But I encountered problems when I removed the ixp board from its factory chassis and plugged it into a Pentium machine. I tried out the same ixp board on 3 different Pentiums, two P2 and one P4. The common problem is, the Pentium cannot boot up. Nothing appears on the monitor,not even BIOS messages. Judging from the initial "noise" from the CPU, the Pentium did go into initial BIOS mode of memory test but after that it simply stopped. All the ixp board's LEDs flashed once upon power up and the LED indicators showed '1' and '6'. What does '1' and '6' mean ? I swopped the PCI slot of the ixp board in the active backplane, but to no success. Using any PCI slot on the Pentium is fine, right? Initially, there was the doubt of conflict with the graphics card, but surely not after 3 different Pentium machines were tested, right ? Next, I shorted the reset pins (J21)and retried all my procedures. The Pentium booted up successfully and then the reset pins were opened. The LED indicators changed from the initial '8''8' to '1''6'. I feel that my ixp board is not yet configured properly as a PCI board, despite the fact that the jumpers setting were double-checked to be that of Vera's. What could cause the conflicts ? Why is PCI slot 4 on the factory chassis's PCI plane enabled and the rest disabled ? Thank You for reading through my problems and I really appreciate all help now ! Please hit the "reply-all" button when replying. Thank You and kind regards, cheewei

2 1

RE: [ixp1200] Query
by Heaton, Eric D 03 Jan '02

03 Jan '02

KP, A Microengine can interupt the SA Core by performing a fast_wr instruction to the IREG register. Here is some microcode to do this: Sv_Ack#: ;Calculate mailbox address immed[thread_mb_base, UTHREAD_TO_CORE_MAILBOXES] alu[to_core_mb, thread_mb_base, +, my_thread_id, <<2] ;Format a message and write to shared memory location alu[reply, reply, OR, format, <<28] ; insert format alu[$xfer0, --, B, reply] alu[indirect_wr_len, format, OR, 0x10] ; setup word count alu[indirect_wr_len, --, B, indirect_wr_len, <<16] sram[write, $xfer0, to_core_mb, 0, 1], indirect_ref, ctx_swap ;Signal Core by writing to IREG fast_wr[1, ireg] For the Core code, there is only one interrupt routine registered to the operating system. Secondary interrupt handler functions are registered with this first layer function that handle specific interrupts. The Interrupt handler demux parses the interrupt vector to determine which of the secondary functions to call to actually do something with the interrupt. In the case above, the debug interrupt handler might be called when bit 24 is set in the IREG register or the thread interrupt handler is called when one of the bits 0:23 are set in IREG. I hope this helps! Eric Heaton Technical Marketing Engineer Intel Corporation - NPBU -----Original Message----- From: paramesh [mailto:paramesh@trinc.com] Sent: Thursday, January 03, 2002 11:28 AM To: ixp1200(a)CS.Princeton.EDU Subject: [ixp1200] Query Hi, Can anyone of you make me sense on the usage of interrupt handling on StrongArm(SA) side over Vxworks with IREG for FIQ interrupts from microengine plz.. Best Regards KP

1 0

Query
by paramesh 03 Jan '02

03 Jan '02

Hi, Can anyone of you make me sense on the usage of interrupt handling on StrongArm(SA) side over Vxworks with IREG for FIQ interrupts from microengine plz.. Best Regards KP

1 0

Re: FILE.bin in Vera
by Scott C. Karlin 03 Jan '02

03 Jan '02

On Thu, Jan 03, 2002 at 05:18:24PM +0800, Tan Chee Wei wrote: > > I am trying out the Vera's installation as described in README.flash. > What puzzles me currently is this file FILE.bin which you described > under the pre-requisites of changing the Flash from Intel firmware to > Princeton firmware. I believe the Princeton firmware refers FILE.bin. > But where should I get the Princeton firmware? Is it the file > FILE.bin refering to $VERAROOT/Flash/bin/flash? I can see flash is an > executable. Is this the Princeton firmware? If not, where can I get > it? FILE.bin refers to the flash image you build when you compile the Runtime code. It is $VERAROOT/Runtime/ixp1200/sa/src/Firmware/flashImage.bin $VERAROOT/Flash/linux-i386/bin/flash is the Linux program you run to update the flash on the ixp1200 board which is already running in a Linux PC. > The next question is the use of serial to access the message from > StrongARM. Do you connect the output of the serial from the IXP1200 > directly to the serial input of the Pentium host machine? You can if you like. However, if the Linux machine crashes, you won't be able to see the last bit of output or use the minimon mode to poke around memory. I'd recommend connecting the IXP1200 serial port to a separate machine. Scott

1 0

RE: [ixp1200] How to use large Boot ramdisk?
by Naik, Uday 02 Jan '02

02 Jan '02

The ramdisk for SDK 2.0 IS 16.0 MB. But if you want to change it --- Change linux/arch/arm/kernel/arch.c. Look for CONFIG_ARCH_IXP1200. Also you need to change the way you build the ramdisk. Look in utils/ramdisk/mkramdisk -----Original Message----- From: Victor [mailto:fei.xie@asu.edu] Sent: Monday, December 31, 2001 2:00 AM To: ixp1200(a)CS.Princeton.EDU Subject: [ixp1200] How to use large Boot ramdisk? Hi, there As I know the default ramdisk size of Linux version 2.3.99-pre3-rmk3-np2 of IXASDK 2.0 is 8MB, how can we recompile the kernel to make use of the larger ramdisk? I have tried to set "CONFIG_BLK_DEV_RAM_SIZE=16384" in the .config, but it didn't work. And because the kernel is downloaded from the host, we can modify the lilo.conf to make it. If somebody have experience on it, please give some advices. Thanks Victor

1 0