Steve & All,
Firstly some updates when I tested yesterday I tested 3-boards the one working board and 2 non-working boards. Today before sending any boards back I have tested all 10 of our boards and discovered that using this new X-Loader/u-boot/Linux kernel image that USB host would work on 6 out of the 10 non-boarding boards. This is good news for us and I have started a new tool chain build from today, following the instructions here http://www.gumstix.net/Software/view/Software-Overo/Setting-up-a-build-environment/111.html
Thank you to Steve & everybody for you help.
Out of our 4 non-working boards I have inspected R26 under our rework microscope and found that on 3 boards the resistor looks to have been pulled off with tweezers or some other instrument with damage to the PCB. On the other board the resistor was desoldered on one side only and the other side looks to have been levered off.
Our SD card format is as follows:
[rboyce@... gumstix]$ sudo fdisk /dev/mmcblk0 -l
Disk /dev/mmcblk0: 2002 MB, 2002780160 bytes
4 heads, 16 sectors/track, 61120 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 1 16002 512045 c W95 FAT32 (LBA)
/dev/mmcblk0p2 16002 61119 1443750 83 Linux
The only difference between this card and the web instructions is that I have designated a 500MB FAT partition instead of a 50MB (I have tried both and they were marked bootable as above). I have also retried today by recopying u-boot all lowercase to the uSD card, still no joy. This is a lower priority issue for me as I can move forward from this.
Once again thank you to Steve and everybody else for you help I have been contacted by Dan from Gunstix with an RMA number so I will complete that off line. You all have been proactive and made support for this issue very easy, this has made my recommendation of Gumstix an easy one and one I would have no hesitation in doing again.
Regards,
Rod Boyce
-----Original Message-----
From: Steve Sakoman [mailto:sakoman@...]
Sent: 08 June 2009 18:53
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] Overo Earth USB host
On Mon, Jun 8, 2009 at 9:08 AM, Rod
Boyce<rboyce@...> wrote:
> Steve,
>
> I had already deleted the u-boot environment variables from all 11 COM boards. See this message in the boot log ' *** Warning - bad CRC or NAND, using default environment'. I did this to eliminate exactly this kind of inconsistency (I have worked on u-boot before).
>
> I have not yet been able to get the X-loader to load u-boot from the uSD card no matter what combination of upper case or lower case filenames I have tried.
The following boot message means something is borked on your FAT
partition. Did you do the step that marks the partition as bootable?
> Reading boot sector
> Error: reading boot sector
The filename should be u-boot.bin, all lower case.
> But I can boot the X-Loader from the uSD card, u-boot from NAND, and uImage from uSD. So I have upgraded u-boot on my NAND to the image dated 200906040838, deleted again the environment and updated MLO & uImage on the uSD card.
>
> But I still do not have a working USB host port on the 10 Gumstix COM boards and my one working board still works.
>
> If you have any more suggestions I am open to trying them out but this is looking to us like a HW issue on these COM boards.
I agree. I think you have pretty much eliminated any software issues.
The symptom you see is much like the R26 behavior, but you've already
eliminated that possibility. I would ask for an RMA.
Steve
> I will paste the boot log here so you can see what we have done and have done a u-boot printenv at the bottom of the log so you can see the u-boot environment variables.
>
> Regards,
> Rod Boyce
>
>
>
> =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2009.06.08 16:36:54 =~=~=~=~=~=~=~=~=~=~=~=
> £tµb$U @ @ @D¨±` @ @à
>
> Texas Instruments X-Loader 1.4.2 (Jun 4 2009 - 09:37:25)
> Reading boot sector
> Error: reading boot sector
> Loading u-boot.bin from nand
>
>
> U-Boot 2009.06-rc2 (Jun 04 2009 - 09:40:18)
>
> OMAP3503-GP ES2.1, CPU-OPP2 L3-165MHz
> Gumstix Overo board + LPDDR/NAND
> DRAM: 256 MB
> NAND: 256 MiB
> *** Warning - bad CRC or NAND, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Die ID #05bc00020000000004031c130101000a
> Hit any key to stop autoboot: 5 4 3 2 1 0
> mmc1 is available
> reading boot.scr
>
> ** Unable to read "boot.scr" from mmc 0:1 **
> reading uImage
>
> 2725308 bytes read
> Booting from mmc ...
> ## Booting kernel from Legacy Image at 82000000 ...
> Image Name: Angstrom/2.6.29/overo
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 2725244 Bytes = 2.6 MB
> Load Address: 80008000
> Entry Point: 80008000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing Linux.................................................................................................................................................................................... done, booting the kernel.
> Linux version 2.6.29-omap1 (sakoman@...) (gcc version 4.3.3 (GCC) ) #1 Thu Jun 4 09:45:58 PDT 2009
> CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=10c5387f
> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
> Machine: Gumstix Overo
> omapfb_early_vram, 12582912, 0x0
> Memory policy: ECC disabled, Data cache writeback
> OMAP3430 ES2.1
> SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
> Reserving 12582912 bytes SDRAM for VRAM
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
> Kernel command line: console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@... omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
> Clocking rate (Crystal/DPLL/ARM core): 26.0/331/500 MHz
> GPMC revision 5.0
> IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
> Total of 96 interrupts on 1 active controller
> OMAP34xx GPIO hardware version 2.5
> PID hash table entries: 1024 (order: 10, 4096 bytes)
> OMAP clockevent source: GPTIMER1 at 32768 Hz
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 128MB 128MB = 256MB total
> Memory: 241408KB available (4472K code, 532K data, 940K init)
> Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> net_namespace: 764 bytes
> regulator: core version 0.5
> NET: Registered protocol family 16
> Found NAND on CS0
> Registering NAND on CS0
> OMAP DMA hardware revision 4.0
> bio: create slab <bio-0> at 0
> OMAP DSS rev 2.0
> OMAP DISPC rev 3.0
> OMAP VENC rev 2
> i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
> twl4030: PIH (irq 7) chaining IRQs 368..375
> twl4030: power (irq 373) chaining IRQs 376..383
> twl4030: gpio (irq 368) chaining IRQs 384..401
> regulator: VMMC1: 1850 <--> 3150 mV normal standby
> regulator: VUSB1V5: 1500 <--> 0 mV normal standby
> regulator: VUSB1V8: 1800 <--> 0 mV normal standby
> regulator: VUSB3V1: 3100 <--> 0 mV normal standby
> i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
> SCSI subsystem initialized
> twl4030_usb twl4030_usb: Initialized TWL4030 USB module
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> Bluetooth: Core ver 2.14
> NET: Registered protocol family 31
> Bluetooth: HCI device and connection manager initialized
> Bluetooth: HCI socket layer initialized
> cfg80211: Using static regulatory domain info
> cfg80211: Regulatory domain: US
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
> (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
> cfg80211: Calling CRDA for country: US
> musb_hdrc: version 6.0, musb-dma, host, debug=0
> musb_hdrc: USB Host mode controller at d80ab000 using DMA, IRQ 92
> musb_hdrc musb_hdrc: MUSB HDRC host driver
> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
> usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb1: Product: MUSB HDRC host driver
> usb usb1: Manufacturer: Linux 2.6.29-omap1 musb-hcd
> usb usb1: SerialNumber: musb_hdrc
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 1 port detected
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> NET: Registered protocol family 1
> VFS: Disk quotas dquot_6.5.2
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
> msgmni has been set to 471
> alg: No test for stdrng (krng)
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
> serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
> serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
> console [ttyS2] enabled
> brd: module loaded
> loop: module loaded
> usbcore: registered new interface driver asix
> usbcore: registered new interface driver cdc_ether
> i2c /dev entries driver
> Driver 'sd' needs updating - please use bus_type methods
> omap2-nand driver initializing
> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)
> cmdlinepart partition parsing not available
> Creating 5 MTD partitions on "omap2-nand":
> 0x000000000000-0x000000080000 : "xloader"
> 0x000000080000-0x000000240000 : "uboot"
> 0x000000240000-0x000000280000 : "uboot environment"
> 0x000000280000-0x000000680000 : "linux"
> 0x000000680000-0x000010000000 : "rootfs"
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
> ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2
> ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
> ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
> usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
> usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb2: Product: OMAP-EHCI Host Controller
> usb usb2: Manufacturer: Linux 2.6.29-omap1 ehci_hcd
> usb usb2: SerialNumber: ehci-omap.0
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 3 ports detected
> Initializing USB Mass Storage driver...
> usbcore: registered new interface driver usb-storage
> USB Mass Storage support registered.
> udc: OMAP UDC driver, version: 4 October 2004 (iso) (dma)
> mice: PS/2 mouse device common for all mice
> twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
> twl4030_rtc twl4030_rtc: Power up reset detected.
> twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
> OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
> Bluetooth: HCI UART driver ver 2.2
> Bluetooth: HCI H4 protocol initialized
> Bluetooth: HCI BCSP protocol initialized
> Bluetooth: Broadcom Blutonium firmware driver ver 1.2
> usbcore: registered new interface driver bcm203x
> Bluetooth: Digianswer Bluetooth USB driver ver 0.10
> usbcore: registered new interface driver bpa10x
> mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
> regulator: Unable to get requested regulator: vmmc_aux
> mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
> regulator: Unable to get requested regulator: vmmc
> usbcore: registered new interface driver usbhid
> usbhid: v2.6:USB HID core driver
> Advanced Linux Sound Architecture Driver Version 1.0.18a.
> usbcore: registered new interface driver snd-usb-audio
> No device for DAI twl4030
> No device for DAI omap-mcbsp-dai-0
> No device for DAI omap-mcbsp-dai-1
> No device for DAI omap-mcbsp-dai-2
> No device for DAI omap-mcbsp-dai-3
> No device for DAI omap-mcbsp-dai-4
> overo SoC init
> TWL4030 Audio Codec init
> asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
> ALSA device list:
> #0: overo (twl4030)
> oprofile: using arm/armv7
> TCP cubic registered
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> Bluetooth: L2CAP ver 2.11
> Bluetooth: L2CAP socket layer initialized
> Bluetooth: SCO (Voice Link) ver 0.6
> Bluetooth: SCO socket layer initialized
> Bluetooth: RFCOMM socket layer initialized
> Bluetooth: RFCOMM TTY layer initialized
> Bluetooth: RFCOMM ver 1.10
> Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> Bluetooth: BNEP filters: protocol multicast
> Bluetooth: HIDP (Human Interface Emulation) ver 1.2
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> ThumbEE CPU extension supported.
> Power Management for TI OMAP3.
> SmartReflex driver initialized
> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
> mmc0: mmc_rescan - card ocr from io_op=0x00000000, err = -110
> fbcvt: 1024x768@...: CVT Name - .786M3-R
> Console: switching to colour frame buffer device 128x48
> clock: clksel_round_rate_div: dpll4_m4_ck target_rate 86400000
> clock: new_div = 5, new_rate = 86400000
> twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
> Waiting for root device /dev/mmcblk0p2...
> mmc0: host does not support reading read-only switch. assuming write-enable.
> mmc0: new high speed SD card at address 0007
> mmcblk0: mmc0:0007 SD02G 1.86 GiB
> mmcblk0: p1 p2
> mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on mmcblk0p2, internal journal
> EXT3-fs: recovery complete.
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> Freeing init memory: 940K
>
> INIT: version 2.86 booting
>
> Please wait: booting...
> Starting udevads7846 spi1.0: touchscreen, irq 274
> ads7846 spi1.0: no device detected, test read result was 0x00000000
> and populating dev cache
> Remounting root file system...
> NET: Registered protocol family 10
> ALSA: Restoring mixer settings...
> Configuring network interfaces... done.
> Starting portmap daemon: portmap.
> net.ipv4.conf.default.rp_filter = 1
> net.ipv4.conf.all.rp_filter = 1
> Thu Jun 4 15:48:00 BST 2009
> Turning echo off on /dev/ttyS1
>
> INIT: Entering runlevel: 5
>
> Starting system message bus: dbus.
> Starting Hardware abstraction layer hald
> Starting Connection Manager
> Starting Dropbear SSH server: dropbear.
> Starting advanced power management daemon: No APM support in kernel
> (failed.)
> Starting Samba: smbd nmbd.
> Starting syslogd/klogd: done
> * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
> [ ok ]
> Starting Bluetooth subsystem:
> Initialization timed out.
> Running ntpdate to synchronize clockError : Temporary failure in name resolution
> .
> /etc/rc5.d/S81cups: line 232: echo_success: not found
> cups: started scheduler.
> Starting GPE display manager: gpe-dm
>
> .-------.
> | | .-.
> | | |-----.-----.-----.| | .----..-----.-----.
> | | | __ | ---'| '--.| .-'| | |
> | | | | | |--- || --'| | | ' | | | |
> '---'---'--'--'--. |-----''----''--' '-----'-'-'-'
> -' |
> '---'
>
> The Angstrom Distribution overo ttyS2
>
> Angstrom 2009.X-test-20090604 overo ttyS2
>
> overo login: root
> Welcome to Gumstix Overo
> For more information visit:
> http://www.gumstix.net/Overo/115.html
> root@...:~# cat /proc/version
> Linux version 2.6.29-omap1 (sakoman@...) (gcc version 4.3.3 (GCC) ) #1 Thu Jun 4 09:45:58 PDT 2009
> root@...:~# £tµb$U @ @_H¨HU¯¬.HR·.]®][Y·ºs X-Loader 1.4.2 (Jun 4 2009 - 09:37:25)
> Reading boot sector
> Error: reading boot sector
> Loading u-boot.bin from nand
>
>
> U-Boot 2009.06-rc2 (Jun 04 2009 - 09:40:18)
>
> OMAP3503-GP ES2.1, CPU-OPP2 L3-165MHz
> Gumstix Overo board + LPDDR/NAND
> DRAM: 256 MB
> NAND: 256 MiB
> *** Warning - bad CRC or NAND, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Die ID #05bc00020000000004031c130101000a
> Hit any key to stop autoboot: 5 0
> Overo # printenv
>
> bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi
> bootdelay=5
> baudrate=115200
> loadaddr=0x82000000
> console=ttyS2,115200n8
> vram=12M
> dvimode=1024x768MR-16@...
> defaultdisplay=dvi
> mmcargs=setenv bootargs console=${console} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
> nandargs=setenv bootargs console=${console} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} root=/dev/mtdblock4 rw rootfstype=jffs2
> loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
> bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
> loaduimage=fatload mmc 0 ${loadaddr} uImage
> mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
> nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr}
> stdin=serial
> stdout=serial
> stderr=serial
> dieid#=05bc00020000000004031c130101000a
>
> Environment size: 1055/131068 bytes
> Overo #
>
>
>
>
> -----Original Message-----
> From: Steve Sakoman [mailto:sakoman@...]
> Sent: 08 June 2009 15:15
> To: General mailing list for gumstix users.
> Subject: Re: [Gumstix-users] Overo Earth USB host
>
> On Mon, Jun 8, 2009 at 12:04 AM, Rod
> Boyce<rboyce@...> wrote:
>> Steve & All,
>>
>> I have confirm that the issue is with the COM board as I can plug my one working COM board into any summit board and it works fine. Sorry if that was not clear enough from my original e-mail.
>
> OK, that is good to know.
>
> You aren't necessarily running exactly the same bits since you are
> executing u-boot from the COM nand memory, and in addition the
> environment setup in each COM's environment nand partition might also
> be sightly different.
>
> Would you mind performing one more test?
>
> Prepare a bootable microSD card that also includes u-boot. Wipe the
> u-boot environment on each COM so that u-boot will use the default
> environment:
>
> nand erase 40000 20000
>
> Now retry your USB test using this same microSD card on both good and bad COMs.
>
> To rule out any strangeness that may have crept into your builds, you
> might also want to try this with one of my pre-built images from the
> latest top of tree:
>
> http://www.sakoman.com/feeds/omap3/glibc/images/overo/200906040838/
>
> I just verified that I was able to do streaming video from a webcam
> over USB EHCI using this image set.
>
> Steve
>
>
>> -----Original Message-----
>> From: Steve Sakoman [mailto:sakoman@...]
>> Sent: 05 June 2009 17:27
>> To: General mailing list for gumstix users.
>> Subject: Re: [Gumstix-users] Overo Earth USB host
>>
>> On Fri, Jun 5, 2009 at 7:54 AM, Rod
>> Boyce<rboyce@...> wrote:
>>> All,
>>>
>>> I am the new owner of 11 Overo Earth boards with Summit base boards. The first board we purchased about 1-month ago for evaluation of the USB host performance this went well and I recommended that we buy 10 more boards. We received these 10-more boards and I went to installing the SW on these boards. But I have discovered that while the USB host port works fine on my original board the USB host interface does not work on the other 10 Overo Earth boards.
>>
>> The next step would be to isolate whether the issue is with the COM
>> modules or with the Summit boards. Have you tried testing the working
>> COM module with one of the new Summit boards (and vise-versa)?
>>
>> Steve
>>
>>>
>>> I am running exactly the same SW on all boards
>>> Xloader is 'Texas Instruments X-Loader 1.4.2 (Nov 14 2008 - 13:21:49)'
>>> u-boot is 'U-Boot 2008.10 (Nov 15 2008 - 22:55:43)'
>>> Linux kernel is 'Linux overo 2.6.29-omap1 #1 Fri May 29 17:58:22 BST 2009 armv7l GNU/Linux'
>>>
>>> U-boot and Linux kernel are build from my tool chain and X-Loader is from the v0.92 SW release. My boot procedure is a little weird as it goes:
>>> * X-Loader from SD
>>> * u-boot from NAND
>>> * uImage (Linux kernel) from SD
>>>
>>>
>>> Anyway this is all fine as the USB host code works on my one working board but not on the other 10 boards. I have checked that R26 is not present on all boards but the USB host interface still does not work. Is there anything else I can check on the Earth boards or is there some SW (other HW) change I need to make somewhere to get this working?
>>>
>>> I will paste below here a boot log from a failing board it is connected to a 4-port belkin hub with power supply. There is a keyboard and a mouse connected to the hub. I am using the default u-boot environment on all boards.
>>>
>>> Regards,
>>> Rod Boyce
>>>
>>>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users
|