Hello,

I have a question on output voltage ramp up time and sequence for LP3891EMR-1.2. Vin = 3.3V, VBias = 5V and Vout = 1.2V. Ramp up time for 5V Bias voltage is 5us. Ramp up time for 3.3V is 3ms. (3.3V is generated from 5V using TPS54232D to achieve slow start).

What would be the ramp up time for 1.2V output? Also what would be the sequence between 3.3V input and 1.2V output from LP3891EMR-1.2. There is no specific sequence requirement, but ramp up time should be slow (min 200us) for both 3.3V and 1.2V.

Thank you.

Regards,

Sameer.

Hi all,

          My board is DM8168 EVM.I use EZSDK.I donot know how to force IDR frame.Who can help me?Thanks.

Best wishes

hjt

embedded sync data is easy done, and discrete sync data cannot be capture properly, what timing for VSYNC/HSYNC/ACTIVD/FCLK about vip module for  discrete?

Hello!

I am working with TMS320C5515 EVM under CCSv5.3.

I would want to know how can I change the sampling Frequency of AIC3204. I was developing a program and I thought that It was configured to 48KHz sampling Frequency. However, when entering with a 1KHZ tone input, in the output I get a signal that would be of 1 Khz If the sampling frequency was 24KHz. not 48KHz.

I want to know If I have the sampling frequency of the aic3204 bad configured, or If there are another problem different by that one.

I put the configuration here:

AIC3204_rset( 0, 0x00 );

AIC3204_rset( 27, 0x00 );

AIC3204_rset( 4, 0x07 );

AIC3204_rset( 6, 0x20 );

AIC3204_rset( 7, 0 );

AIC3204_rset( 8, 0 );

AIC3204_rset( 5, 0x92 );

AIC3204_rset( 13, 0x00 );

AIC3204_rset( 14, 0x80 );

AIC3204_rset( 20, 0x80 );

AIC3204_rset( 11, 0x88 );

AIC3204_rset( 12, 0x82 );

AIC3204_rset( 18, 0x88 );

AIC3204_rset( 19, 0x82 );

and the function is:

nt16 AIC3204_rset( Uint16 regnum, Uint16 regval )

{

Uint8 cmd[2];

cmd[0] = regnum & 0x007F;

cmd[1] = regval;

return EVM5515_I2C_write( AIC3204_I2C_ADDR, cmd, 2 );

}

Hi,

I'm designing a fast continuous ADC application. I've to acquire a signal array synchronized with two digital clock: one clock for array start (trigger) and the other for single sample (sample clock). So my source generate 256 signal (one every sample clock) starting at the "array start "clock.

I'm planning to solve the problem using:

Array start trigger -> Get 256 sample sync with sample clock -> generate interrupt -> in interrupt function copy and send data -> repeat

This should avoid the use of a double buffered acquisition because the interrupt time should be fast enough to manage the buffer content.

So I need a FIFO od 256 samples. Is this possibile?

At page 683 of the spnu499 manual is written: "The ADC module can support up to 1024 buffers. The device supports a maximum of 64 buffers for both the ADC modules.". What's the difference?  Which one is the right maximum?

Can the ADC FIFO be sized to 256 (or slighlty more) samples?

If no: how to proceed to have a continuous ADC in group of 256 samples? There's something like a double buffered continuous acquisition?

In HalCoGen there are two settings for ADC memory size: one in "ADC Group" (FIFO size) and the other in "ADC Memory". The first seems to accept values hagher then 64 but the seconds seems limited to 64 bytes. Which is the difference?

Is there an example of single continous acquisition similar to the one I need?

Thank you,

Matteo

Hi all,

After researching a lot in graphic library of StarterWare, I found that there may have some problems in color order.

We can see that all color definitons (in file glib.h) are defined in R-G-B order. For example:

#define ClrBlue 0x000000FF
#define ClrLime 0x0000FF00
#define ClrRed  0x00FF0000

C image array (which are created by pnmtoc tool as instructed at http://processors.wiki.ti.com/index.php/StarterWare_Graphics#Porting_StellarisWare_graphics_application_to_StarterWare) are in R-G-B order too.

Besides that, LCD contronller desired RGB data for 12-, 16-, 24- BPP modes.(AM335x Technical Reference Manual p.1234).

However, graphic functions use B-G-R order to draw its components.

Ex: In GrOffScreen24BPPPixelDrawMultiple function (offscr24bpp.c):

...

case 16:
{
unsigned short pixColor = 0; /* 16bpp */

pucData++;
while(lCount--)
{
pixColor = *(pucData+1);
pixColor |= (*(pucData)) << 8;

*pucPtr++ = (pixColor & 0x1F) << 3; /* Blue */ 
*pucPtr++ = (pixColor & 0x07E0) >> 3; /* Green */ 
*pucPtr++ = (pixColor & 0x0000F800) >> 8; /* Red */ 
*pucPtr++ = 0x0; /* Alpha */

pucData += 2;
}
break;
}
case 32: /* 24bpp with 1-byte hole */
{
//pucData++;
while(lCount--)
{
*pucPtr++ = *(pucData+3);
*pucPtr++ = *(pucData+2);
*pucPtr++ = *(pucData+1);
*pucPtr++ = *(pucData+0);

pucData += 4;
}
break;
}

I think these code will change pixel data from RGB order to BGR order!

Let me know if I was wrong!

Best regards,

TinND

I got a Tiva (Stellaris) Launchpad a while ago, played around with it, found the chip very exciting and wanted to use it in a number of small-scale designs. But a quick check on Farnell (UK) shows that they haven't even heard of TM4C. Mouser has none, and the pricing for the only "stocked" chip that I can buy in 10 qty is 6.5EUR. That's rather disappointing given that I can get a Kinetis K10 for less than 2EUR from Farnell *today*.

Now, I do prefer TI documentation, I like the TI microcontrollers I've used so far, and I realize the basic Kinetis K10 is a 50MHz chip without an FPU. But still, it does have the DSP instructions, it has a >3x price advantage, and it is available now from Farnell!

So, while I realize that TI employees that monitor these forums aren't setting the pricing, I just wanted to get a rough feel -- is the Tiva-C family intended to be price-competitive with Freescale's Kinetis at hobby/small-scale quantities?

Should I wait?

http://processors.wiki.ti.com/index.php/DM81xx_AM38xx_PCI_Express_Root_Complex_Driver_User_Guide

I follow the manual to operate，and I used with Broadcom NetXtreme BCM5751 based Gigabit Ethernet Controller card as a PCIe Endpoint.

I bought a total of three BCM5751.

But I can't ping with pc or other devices.

here's the log,please help me,tks.

2866716 bytes read
## Booting kernel from Legacy Image at 80009000 ...
Image Name: Linux-2.6.37
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2866652 Bytes = 2.7 MiB
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.37 (root@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #13 Fri May 10 14:34:31 CST 2013
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168evm
reserved size = 52428800 at 0x0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8168 2.0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 79656
Kernel command line: console=ttyO2,115200n8 rootwait root=/dev/sdb4 rw mem=364M@0x80000000 324M@0x9F900000 notifyk.vpssm3_sva=0xBF900000 ip=off noinitrd
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 314MB = 314MB total
Memory: 312020k/312020k available, 60716k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xd7000000 - 0xf8000000 ( 528 MB)
lowmem : 0xc0000000 - 0xd6c00000 ( 364 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc003d000 ( 212 kB)
.text : 0xc003d000 - 0xc057d000 (5376 kB)
.data : 0xc057e000 - 0xc05ca8c0 ( 307 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 27000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy: 
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
_omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl
_omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda
NOR: Can't request GPMC CS
registered ti816x_gpio_vr device
registered ti816x_sr device
clk get on i2c3 fck failed
_omap_mux_get_by_name: Could not find signal dcan0_tx.dcan0_tx
_omap_mux_get_by_name: Could not find signal dcan0_rx.dcan0_rx
pm_dbg_init: only OMAP3 supported
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
registered ti81xx_vin device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xd7020000
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers disabled
pci 0000:00:00.0: BAR 8: assigned [mem 0x20000000-0x200fffff]
pci 0000:00:00.0: BAR 9: assigned [mem 0x20100000-0x201fffff pref]
pci 0000:01:00.0: BAR 0: assigned [mem 0x20000000-0x2000ffff 64bit]
pci 0000:01:00.0: BAR 0: set to [mem 0x20000000-0x2000ffff 64bit] (PCI address [0x20000000-0x2000ffff])
pci 0000:01:00.0: BAR 6: assigned [mem 0x20100000-0x2010ffff pref]
pci 0000:00:00.0: PCI bridge to [bus 01-01]
pci 0000:00:00.0: bridge window [io disabled]
pci 0000:00:00.0: bridge window [mem 0x20000000-0x200fffff]
pci 0000:00:00.0: bridge window [mem 0x20100000-0x201fffff pref]
PCI: enabling device 0000:00:00.0 (0140 -> 0143)
bio: create slab <bio-0> at 0
regulator: VFB: 800 <--> 1025 mV at 1010 mV 
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea20809
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: 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.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d701e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
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: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d7026800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
msgmni has been set to 609
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
console [ttyO2] enabled
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x3
ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc 
scsi0 : ahci_platform
scsi1 : ahci_platform
ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 16
ata2: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 16
m25p80 spi1.0: found w25q32, expected m25p80
m25p80 spi1.0: w25q32 (4096 Kbytes)
Creating 4 MTD partitions on "spi_flash":
0x000000000000-0x000000040000 : "U-Boot"
0x000000040000-0x000000042000 : "U-Boot Env"
0x000000042000-0x0000002c2000 : "Kernel"
0x0000002c2000-0x000000400000 : "File System"
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x00000cee0000 : "File System"
0x00000cee0000-0x000010000000 : "Reserved"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffff9
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
davinci_mdio davinci_mdio.0: phy[2]: device 0:02, driver unknown
e1000e: Intel(R) PRO/1000 Network Driver - 1.2.7-k2
e1000e: Copyright (c) 1999 - 2010 Intel Corporation.
tg3.c:v3.115 (October 14, 2010)
PCI: enabling device 0000:01:00.0 (0140 -> 0142)
usb 1-1: new full speed USB device using musb-hdrc and address 2
tg3 0000:01:00.0: eth0: Tigon3 [partno(BCM95751A519) rev 4001] (PCI Express) MAC address 00:10:18:0b:3b:76
tg3 0000:01:00.0: eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1])
tg3 0000:01:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
tg3 0000:01:00.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit]
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver smsc95xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbf900000
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
#0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
smartreflex smartreflex: Driver initialized
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
usb 1-1: New USB device found, idVendor=05e3, idProduct=0606
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: USB Hub 2.0
usb 1-1: Manufacturer: ALCOR
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
mmc0: new high speed SD card at address cffe
mmcblk0: mmc0:cffe SD02G 1.83 GiB 
mmcblk0: p1 p2 p3
usb 1-1.3: new low speed USB device using musb-hdrc and address 3
usb 1-1.3: New USB device found, idVendor=0425, idProduct=0001
usb 1-1.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-1.3: Product: USB OPTICAL MOUSE
input: USB OPTICAL MOUSE as /devices/platform/omap/ti81xx-usbss/musb-hdrc.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input0
generic-usb 0003:0425:0001.0001: input: USB HID v1.11 Mouse [ USB OPTICAL MOUSE] on usb-musb-hdrc.0-1.3/input0
usb 1-1.4: new low speed USB device using musb-hdrc and address 4
usb 1-1.4: New USB device found, idVendor=04d9, idProduct=1702
usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.4: Product: USB Keyboard
usb 1-1.4: Manufacturer: 
input: USB Keyboard as /devices/platform/omap/ti81xx-usbss/musb-hdrc.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input1
generic-usb 0003:04D9:1702.0002: input: USB HID v1.10 Keyboard [ USB Keyboard] on usb-musb-hdrc.0-1.4/input0
input: USB Keyboard as /devices/platform/omap/ti81xx-usbss/musb-hdrc.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input2
generic-usb 0003:04D9:1702.0003: input: USB HID v1.10 Device [ USB Keyboard] on usb-musb-hdrc.0-1.4/input1
ata2: link is slow to respond, please be patient (ready=0)
ata1: link is slow to respond, please be patient (ready=0)
ata2: softreset failed (device not ready)
ata1: softreset failed (device not ready)
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: Hitachi HTS545032B9A300, PB3OC64G, max UDMA/133
ata2.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: configured for UDMA/133
ata1.00: ATA-8: Hitachi HTS545032B9A300, PB3OC64G, max UDMA/133
ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA Hitachi HTS54503 PB3O PQ: 0 ANSI: 5
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access ATA Hitachi HTS54503 PB3O PQ: 0 ANSI: 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
sd 1:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
sdb: sdb1 sdb2 sdb3 sdb4
sd 1:0:0:0: [sdb] Attached SCSI disk
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdb4): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sdb4): using internal journal
EXT3-fs (sdb4): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 8:20.
devtmpfs: mounted
Freeing init memory: 212K
INIT: version 2.86 booting
Please wait: booting...
Error opening /dev/fb0: No such file or directory
Starting udev
udevd (90): /proc/90/oom_adj is deprecated, please use /proc/90/oom_score_adj instead.
udev: starting version 141
Remounting root file system...
Caching udev devnodes
Populating dev cacheminix: disagrees about version of symbol module_layout
modprobe: FATAL: Error inserting minix (/lib/modules/2.6.37/kernel/fs/minix/minix.ko): Invalid module format

FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda.
EXT3-fs (sda): error: can't find ext3 filesystem on dev sda.
EXT2-fs (sda): error: can't find an ext2 filesystem on dev sda.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda.
ISOFS: Unable to identify CD-ROM format.
minix: disagrees about version of symbol module_layout
modprobe: FATAL: Error inserting minix (/lib/modules/2.6.37/kernel/fs/minix/minix.ko): Invalid module format

minix: disagrees about version of symbol module_layout
modprobe: FATAL: Error inserting minix (/lib/modules/2.6.37/kernel/fs/minix/minix.ko): Invalid module format

FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
EXT3-fs (mmcblk0): error: can't find ext3 filesystem on dev mmcblk0.
EXT2-fs (mmcblk0): error: can't find an ext2 filesystem on dev mmcblk0.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
ISOFS: Unable to identify CD-ROM format.
mv: cannot rename '/tmp/devices': No such file or directory
NET: Registered protocol family 10
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda3): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sda3): using internal journal
EXT3-fs (sda3): mounted filesystem with writeback data mode
EXT3-fs (sda1): using internal journal
EXT3-fs (sda1): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sdb1): using internal journal
EXT3-fs (sdb1): mounted filesystem with writeback data mode
EXT3-fs (sda2): using internal journal
EXT3-fs (sda2): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdb3): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sdb3): using internal journal
EXT3-fs (sdb3): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdb2): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sdb2): using internal journal
EXT3-fs (sdb2): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
ALSA: Restoring mixer settings...
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
Configuring network interfaces... ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0 no wireless extensions.

/bin/sh: udhcpc: not found
done.
Setting up IP spoofing protection: rp_filter.
Thu May 9 17:21:00 CST 2013
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Starting Hardware abstraction layer hald
tg3 0000:01:00.0: eth0: Link is up at 100 Mbps, full duplex
tg3 0000:01:00.0: eth0: Flow control is on for TX and on for RX
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Starting Dropbear SSH server: dropbear.
Starting telnet daemon.
Starting network benchmark server: netserver.
Starting syslogd/klogd: done
Starting thttpd.
Starting Lighttpd Web Server: lighttpd.
2013-05-09 17:21:01: (log.c.166) server started 
/
/
Starting Matrix GUI application.
***************************************************************
***************************************************************
NOTICE: This file system contains the followin GPLv3 packages:
binutils-dev
binutils-symlinks
binutils
gdbserver

If you do not wish to distribute GPLv3 components please remove
the above packages prior to distribution. This can be done using
the opkg remove command. i.e.:
opkg remove <package>
Where <package> is the name printed in the list above

NOTE: If the package is a dependency of another package you
will be notified of the dependent packages. You should
use the --force-removal-of-dependent-packages option to
also remove the dependent packages as well
***************************************************************
*********************************************************T
_____ _____ _ _ 
| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_ 
| | _| .'| . | . | | __| _| . | | | -_| _| _|
|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_| 
|___| |___|

Arago Project http://arago-project.org luhao ttyO2

Arago 2011.09 luhao ttyO2

luhao login: root
root@luhao:~# ifconfig eth0 192.168.1.18
root@luhao:~# ping 192.168.1.59
PING 192.168.1.59 (192.168.1.59): 56 data bytes

--- 192.168.1.59 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
root@luhao:~# lspci -v
00:00.0 Class 0604: Device 104c:b800 (rev 01)
Flags: bus master, fast devsel, latency 0
Memory at <ignored> (32-bit, non-prefetchable)
Memory at <ignored> (32-bit, prefetchable)
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: 20000000-200fffff
Prefetchable memory behind bridge: 20100000-201fffff
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Port (Slot-), MSI 00
Capabilities: [100] Advanced Error Reporting

01:00.0 Class 0200: Device 14e4:1677 (rev 01)
Subsystem: Device 14e4:1677
Flags: bus master, fast devsel, latency 0, IRQ 48
Memory at 20000000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at 20100000 [disabled] [size=64K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel <?>
Kernel driver in use: tg3

root@luhao:~#

root@luhao:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:10:18:0B:3B:76 
inet addr:192.168.1.18 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::210:18ff:fe0b:3b76/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1307 errors:0 dropped:1759 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:137257 (134.0 KiB) TX bytes:321920 (314.3 KiB)
Interrupt:48

lo Link encap:Local Loopback 
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:336 (336.0 B) TX bytes:336 (336.0 B)

 Can you plug the BCM5751 on the DM8168 to test it?

Hi,

My Customer is considering TLK105 with AM3352 device.

And, They want to use WOL(Wake-On LAN).

So, Do you know TLK105 driver which supported for WOL on Linux.

Best regards
Chi

Hi,

I am working on TMS320DM355 based custom board with linux-2.6.10 MVL401 kernel.
I am able to get the entry for MMC in /proc/devices and also got a node in /dev directory with the name mmcblk0 n mmcblk0p1.The problem i am facing is that 
When I try to mount the MMC card i am geting the following error. 

# mount /dev/mmcblk0 /mnt/mmc/

FAT: invalid media value (0x00)
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
FAT: invalid media value (0x00)
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
yaffs: dev is 266338304 name is "mmcblk0"
yaffs: Attempting MTD mount on 254.0, "mmcblk0"
yaffs: dev is 266338304 name is "mmcblk0"
yaffs: Attempting MTD mount on 254.0, "mmcblk0"
mount: you must specify the filesystem type


When i try to mount /dev/mmcblk0p1 (# mount /dev/mmcblk0p1 /mnt/mmc/ ) its mounting but if i try to write or read from mmc i am getting the following error. 

FAT: Filesystem panic (dev mmcblk0p1)
fat_free: deleting beyond EOF (i_pos 131073)
File system has been set read-only
mmcblk0: error 2 transferring data
end_request: I/O error, dev mmcblk0, sector 8255
Buffer I/O error on device mmcblk0p1, logical block 8192
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 2 transferring data
end_request: I/O error, dev mmcblk0, sector 4491
Buffer I/O error on device mmcblk0p1, logical block 4428
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 2 transferring data
end_request: I/O error, dev mmcblk0, sector 727
Buffer I/O error on device mmcblk0p1, logical block 664
lost page write due to I/O error on mmcblk0p1

Anybody can suggest me what i am missing and what i should do.

Thanks

hi all,

         My board is dm8168 evm. I use ezsdk.Now i encode yuv file to h264 file.I set the I frame interval parameter  is 30.But the h264 file is only first frame is I frame.Other frame is not I frame.Why is it?Who can help me?Thanks.

Best wishes,

hjt

Hi

I am not able to run SGX enabled Android Fs in our custom board based on am335x. We are using rowboat-jb-4.1.2. Without SGX, everythin is OK, but when i enable it after showing boot logo, nothing seems on the screen. In logcat output:

Has anyone tried Remote Display on Beaglebone?

TI WinCE-BSP ARM-A8 User Guide (adeneo-embedded) says, Windows Desktop was tested using remote display. but there is no steps on how to use it.

http://processors.wiki.ti.com/index.php/WinCE-BSP_ARM-A8_User_Guide#Support_for_BeagleBone

Has any one used/tried remote display on beaglebone before?  if yes, then please share the steps to enable and use remote display.

I was able to start the cerdisp on the device and  cerhost running on the host PC was able to detect the device and connected, however there was nothing visible on the cerhost screen.

Have anyone come across similar situation, then please share experience..

Thanks in Advance

dasco

Dear All:

        As the Figure.10, we want to use GMII interface for MAC.

        But after we test, there is nothing output from the GMII_GTXCLK.

 Image may be NSFW.
Clik here to view.

Question:

        Should we have to use EMAC_TXCLK pin? (Now the EMAC_TXCLK does not connected.)

Best Regards,

Justin

hello everyone, 

I just come across one problem in my design. For some reasons, I need to change the supply voltage of MSP430  when it is working. For eg, I want to change its working voltage from 2.1V to 3.3V. Of course the voltage still keeps in the safe area. My question is that will the supply voltage's variation cause some uncertain or unknown problems in the running software in the msp430, and how many time does the pin's voltage need to change from the prior station to next one.

thanks!

Hello to everybody,

I'm new to TI products and I'm currently using CC3000EM together with MSP-EXP430FG4618 board. In the Wiki page dedicated to older service pack (http://processors.wiki.ti.com/index.php/CC3000_Wi-Fi_Downloads1.9) I've found  the useful sample application called CC3000+MSP-EXP430FG4618 Basic Wi-Fi Application and so now I'm trying to modify and adapt it to my needs. 

I've noticed (if I am not wrong) that this application has a Release Package number which is 1.7.2.2 and so the correct Service Pack Version to be burn on the CC3000 EEPROM is 1.5 . I'm quite confused about the issue of patch programming, in particular I have the following questions:

1) Which is the easiest way in order to program the EEPROM memory of CC3000 with the correct Service Pack according to the devices I'm currently using?

2)Which is the link in the TI website which provides the files (Service Pack 1.5) to burn in the CC3000 memory?

Thank you very much for your help and your support.

Best Regards,

Demaria Mario

Hello,

We're trying to build an application with the CC2540 where the accuracy of the time is very important. We're using the OSAL_ClockBLE.c functions to set and get the time. However, the difference with a reference clock get quite high over the course of 24 hours. In our case we communicate every second over BLE and in 24 hours the CC2540 time was around 10 minutes off. 

Any ideas how we can make this more reliable? We've been testing on the CC2540MINIDK_EM device and a ConnectBlue module with the CC2540 chip on board.

Thanks a lot in advance!

Tijn

SW:EZSDK5.5 OMX

HW:DM8168

OMX_INIT_PARAM (&tStaticParam);

  tStaticParam.nPortIndex = OMX_VIDENC_OUTPUT_PORT;
 
  eError = OMX_GetParameter (pHandle, OMX_TI_IndexParamVideoStaticParams,
                             &tStaticParam);
 
  tStaticParam.videoStaticParams.h264EncStaticParams.rateControlParams.HRDBufferSize = pAppData->nBitRate * 2;
  tStaticParam.videoStaticParams.h264EncStaticParams.videnc2Params.encodingPreset = XDM_USER_DEFINED;//XDM_DEFAULT;
  tStaticParam.videoStaticParams.h264EncStaticParams.videnc2Params.rateControlPreset = IVIDEO_USER_DEFINED;//IVIDEO_LOW_DELAY;

tStaticParam.videoStaticParams.h264EncStaticParams.intraCodingParams.intraCodingPreset = IH264_INTRACODING_USERDEFINED;
tStaticParam.videoStaticParams.h264EncStaticParams.intraCodingParams.lumaIntra4x4Enable = 0x1FF; //when 0x1f and 0x1ff, same results
tStaticParam.videoStaticParams.h264EncStaticParams.intraCodingParams.lumaIntra8x8Enable = 0x1FF;
tStaticParam.videoStaticParams.h264EncStaticParams.intraCodingParams.lumaIntra16x16Enable = 0xF;
tStaticParam.videoStaticParams.h264EncStaticParams.intraCodingParams.chromaIntra8x8Enable = 0xF;
tStaticParam.videoStaticParams.h264EncStaticParams.intraCodingParams.chromaComponentEnable = IH264_CHROMA_COMPONENT_CB_CR_BOTH;
tStaticParam.videoStaticParams.h264EncStaticParams.intraCodingParams.constrainedIntraPredEnable = 0;        
  eError = OMX_SetParameter (pHandle, OMX_TI_IndexParamVideoStaticParams,
                             &tStaticParam);
  }

but the  StaticParam does not take effect? the Encoded stream does not change.

I've got an application that captures and encodes video using OMX apis on a DM816x, using EZSDK 5.05.  If this app crashes or is terminated early with control-C, running it again always fails when attempting to create the capture (VFCC) object.  Looking at the debug logs, the vfcc driver can't be created because it's in use (FVID2_EDEVICE_INUSE).

With EZSDK 5.03, this same scenario would hang, with some thread (perhaps owned by OMX) using up 100% of the CPU.

It appears that the OMX stack or capture driver don't clean up properly on an unexpected application termination.  Is this a known problem?  Is there a work-around?

Thanks.

Chip : DM368

USB Mode : USB 2.0 HOST

DVSDK : DVSDK_4.00 4_00_00_22 http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/4_00_00_22/index_FDS.html

Bugs : when use a USB WiFi dongle , the USB driver hung , but when choose the PIO mode , it works fine but the CPU load is higher then DMA mode.

Questions : does this bug be fixed in higher DVSDK version such as DVSDK 4.02 ?

DVSDK_4.02 4_02_00_06 http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/4_02_00_06/index_FDS.html