Bluewater Systems Support Forum

Re: I2C Voltage Level Problem: < 2.0V

andre — Thu, 06 May 2010 21:36:39 -0600

Removing the audio codec would definitely solve the problem. We are doing another build of Snapper units shortly, which will be Rev 2 units, but I do not have a firm date on that.

Re: I2C Voltage Level Problem: < 2.0V

pteh — Wed, 05 May 2010 21:15:35 -0600

Hi Andre,

I'm using I2C to talk to other I2C devices off the snapper module.

When I2C level is < 2.0V, 90% of the time I received invalid message. Or no response at all which I believe because of invalid address interpretation by Slave devices.

When I2C voltage level is 3.3V, 98% of the time I received valid message.

I don't use any I2C devices on board of Snapper module. The audio codec can be removed if it can solve the problem.

Has Rev 2 released to be used? If not, when will it be available?

Regards,

Patrick

Re: I2C Voltage Level Problem: < 2.0V

andre — Wed, 05 May 2010 20:49:38 -0600

Hi,
I believe this is being caused by an issue with the audio codec being in low-power mode, which causes it to attempt to parasitically power itself off the I2C lines. This is why you see the drop there. Are you having any other I2C issues? What problems is this causing you?

In Snapper9260 rev2 modules, we have isolated the audio codec from the I2C bus when it is in low power mode, preventing this problem.

I will do some further investigation and come back with a solution.

Regards,
Andre

Re: I2C Voltage Level Problem: < 2.0V

pteh — Wed, 05 May 2010 20:41:41 -0600

In several occasion, I've seen I2C timeout during boot-up for both booting process.

Booting from NFS:

U-Boot 1.1.6 (Mar 10 2009 - 11:23:19)

Processor:        AT91SAM9xx Series
Core Speed:       180.07 MHz
Peripheral Speed: 90.03 MHz
External Crystal: 18.432 MHz
USB Speed:        48.08 MHz
Core:             ARM926EJS, version: 2
Internal SRAM:    8KB
RAM Configuration:
Bank #0: 20000000 64 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
Snapper> max7311 0 3 config 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> max7311 0 3 output 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> max7311 0 2 config 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> max7311 0 2 output 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> run nfs_boot
No FPGA on this module, or no FPGA init required

PHY Mode: Default
End of Autonegotiation
File transfer via NFS from server 192.168.25.36; our IP address is 192.168.25.24
Filename '/home/patrickst/workspace/development/odnrfog-scm/configuration/scm-s.
Load address: 0x23000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###########
done
Bytes transferred = 1720108 (1a3f2c hex)
## Booting image at 23000000 ...
   Image Name:   Linux-2.6.20-snapper 19:16:36 20
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1720044 Bytes =  1.6 MB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
Linux version 2.6.20-snapper (andre@tutira) (gcc version 4.2.1 (CodeSourcery So0
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Bluewater Systems Snapper 9260
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 180 MHz, master 90 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists.  Total pages: 16256
Kernel command line: console=ttyS0,115200 lcd= baseboard=Rig200 baseboard_rev= 4
Using rig200 Snapper Baseboard
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61184KB available (3088K code, 301K data, 316K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Atmel ISI
Atmel ISI done
snapper_power_domains: Registered 16 domains on io_expander at 0x28
AT91: Power Management (with slow clock mode)
AT91: Starting after general reset
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
Initing 'rig200' baseboard (rev: -1)
Rig200 init
snapper_power_domains: Invalid io_expander address 0x20
snapper_power_domains: Invalid io_expander address 0x27
NetWinder Floating Point Emulator V0.97 (double precision)
yaffs Mar 11 2010 19:15:28 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
i2c /dev entries driver
micron_i2c micron_i2c: Micron i2c bus driver
max7311_init: Searching for devices at: 0x28 0x58 0x59 0x5a
max7311_detect: device attached at address 0x28
snapper_power_domains: Attaching domains at i2c addresses: 0x28
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb8000 (irq = 8) is a ATMEL_SERIAL
RAMDISK driver initialized: 16 RAM disks of 8096K size 1024 blocksize
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
macb: overriding MAC address: 00:50:c2:41:ac:b8
macb macb: detected PHY at address 31 (ID 0007:c0c3)
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:50:c2:41:ac:b8)
Linux video capture interface: v2.00
mtd: extid = 95, cellinfo = 80
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Unknown NAND 256MiB 3,3V 8-b)
Scanning device for bad blocks (speed: fast page: first)
Bad eraseblock 120 at 0x00f00000
Bad eraseblock 538 at 0x04340000
2 bad blocks of 2048 total
Creating 5 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x00000000-0x00020000 : "Preboot"
0x00020000-0x00060000 : "Bootloader"
0x00060000-0x00080000 : "Environment"
0x00080000-0x00480000 : "Kernel"
0x00480000-0x10000000 : "Filesystem"
usbmon: debugfs is not available
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB m)
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB m)
usbcore: registered new interface driver sierra
drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.0.5
mice: PS/2 mouse device common for all mice
isl1208 0-006f: chip found, driver version 0.2
isl1208 0-006f: rtc core: registered isl1208 as rtc0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc1
rtc-at91sam9 at91_rtt.0: at91_rtt: SET TIME!
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Advanced Linux Sound Architecture Driver Version 1.0.14rc1 (Tue Jan 09 09:56:17.
ASoC version 0.13.1
AIC23 Audio Codec 0.1
tlv320aic23_codec_probe
asoc: tlv320aic23 <-> at91-ssc0 mapping ok
sn9260: Codec in Master Mode
ALSA device list:
  #0: sn9260_tlv320 (tlv320aic23)
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.5
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
ieee80211: 802.11 data/management/control stack, 1.2.18
ieee80211: Copyright (C) 2004-2005 Intel Corporation 
Late initing 'rig200' baseboard
Rig200 late init
isl1208 0-006f: hctosys: invalid date/time
eth0: link down
IP-Config: Complete:
      device=eth0, addr=192.168.25.234, mask=255.255.255.0, gw=192.168.25.1,
     host=snapper, domain=, nis-domain=(none),
     bootserver=192.168.25.36, rootserver=192.168.25.36, rootpath=
Looking up port of RPC 100003/3 on 192.168.25.36
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Looking up port of RPC 100005/3 on 192.168.25.36
VFS: Mounted root (nfs filesystem).
Freeing init memory: 316K
Creating necessary directories...
Mounting system filesystems...
Starting local networking...
Starting DHCP client...
Starting telnet server...
Setting up console ttyS0...
Starting Web Server...
Starting Lighttpd Web Server: 1970-01-01 00:00:05: (log.c.75) server started
lighttpd.

snapper login:

Booting from Flash:

U-Boot 1.1.6 (Mar 10 2009 - 11:23:19)

Processor:        AT91SAM9xx Series
Core Speed:       180.07 MHz
Peripheral Speed: 90.03 MHz
External Crystal: 18.432 MHz
USB Speed:        48.08 MHz
Core:             ARM926EJS, version: 2
Internal SRAM:    8KB
RAM Configuration:
Bank #0: 20000000 64 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
Snapper> max7311 0 3 config 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> max7311 0 3 output 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> max7311 0 2 config 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> max7311 0 2 output 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> boot
Initing power domains...
No FPGA on this module, or no FPGA init required
Usage:
nand    - NAND sub-system


Loading from NAND 256MiB 3,3V 8-bit, offset 0x80000
   Image Name:   Linux-2.6.20-snapper 19:16:36 20
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1720044 Bytes =  1.6 MB
   Load Address: 20008000
   Entry Point:  20008000
## Booting image at 23000000 ...
   Image Name:   Linux-2.6.20-snapper 19:16:36 20
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1720044 Bytes =  1.6 MB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux................................................................................................................... done, booting the kernel.
Linux version 2.6.20-snapper (andre@tutira) (gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)) #1 Thu Mar 11 19:16:28 NZDT 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Bluewater Systems Snapper 9260
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 180 MHz, master 90 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists.  Total pages: 16256
Kernel command line: console=ttyS0,115200 lcd= baseboard=Rig200 baseboard_rev= ethaddr=00:50:C2:41:AC:B8 root=/dev/mtdblock4 rootfstype=yaffs ip=192.168.25.234:192.168.25.36:192.168.25.1:255.255.255.0:snappf
Using rig200 Snapper Baseboard
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61184KB available (3088K code, 301K data, 316K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Atmel ISI
Atmel ISI done
snapper_power_domains: Registered 16 domains on io_expander at 0x28
AT91: Power Management (with slow clock mode)
AT91: Starting after general reset
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
Initing 'rig200' baseboard (rev: -1)
Rig200 init
snapper_power_domains: Invalid io_expander address 0x20
snapper_power_domains: Invalid io_expander address 0x27
NetWinder Floating Point Emulator V0.97 (double precision)
yaffs Mar 11 2010 19:15:28 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
i2c /dev entries driver
micron_i2c micron_i2c: Micron i2c bus driver
max7311_init: Searching for devices at: 0x28 0x58 0x59 0x5a
max7311_detect: device attached at address 0x28
snapper_power_domains: Attaching domains at i2c addresses: 0x28
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb8000 (irq = 8) is a ATMEL_SERIAL
RAMDISK driver initialized: 16 RAM disks of 8096K size 1024 blocksize
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
macb: overriding MAC address: 00:50:c2:41:ac:b8
macb macb: detected PHY at address 31 (ID 0007:c0c3)
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:50:c2:41:ac:b8)
Linux video capture interface: v2.00
mtd: extid = 95, cellinfo = 80
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Unknown NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks (speed: fast page: first)
Bad eraseblock 120 at 0x00f00000
Bad eraseblock 538 at 0x04340000
2 bad blocks of 2048 total
Creating 5 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x00000000-0x00020000 : "Preboot"
0x00020000-0x00060000 : "Bootloader"
0x00060000-0x00080000 : "Environment"
0x00080000-0x00480000 : "Kernel"
0x00480000-0x10000000 : "Filesystem"
usbmon: debugfs is not available
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem (1 port)
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem (3 port)
usbcore: registered new interface driver sierra
drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.0.5
mice: PS/2 mouse device common for all mice
isl1208 0-006f: chip found, driver version 0.2
isl1208 0-006f: rtc core: registered isl1208 as rtc0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc1
rtc-at91sam9 at91_rtt.0: at91_rtt: SET TIME!
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Advanced Linux Sound Architecture Driver Version 1.0.14rc1 (Tue Jan 09 09:56:17 2007 UTC).
ASoC version 0.13.1
AIC23 Audio Codec 0.1
tlv320aic23_codec_probe
asoc: tlv320aic23 <-> at91-ssc0 mapping ok
sn9260: Codec in Master Mode
ALSA device list:
  #0: sn9260_tlv320 (tlv320aic23)
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.5
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
ieee80211: 802.11 data/management/control stack, 1.2.18
ieee80211: Copyright (C) 2004-2005 Intel Corporation 
Late initing 'rig200' baseboard
Rig200 late init
isl1208 0-006f: hctosys: invalid date/time
eth0: link down
IP-Config: Complete:
      device=eth0, addr=192.168.25.234, mask=255.255.255.0, gw=192.168.25.1,
     host=snapper, domain=, nis-domain=(none),
     bootserver=192.168.25.36, rootserver=192.168.25.36, rootpath=
yaffs: dev is 32505860 name is "mtdblock4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.4, "mtdblock4"
yaffs: auto selecting yaffs2
block 85 is bad
block 503 is bad
2 bad blocks total
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
VFS: Mounted root (yaffs filesystem).
Freeing init memory: 316K
Creating necessary directories...
Mounting system filesystems...
Starting local networking...
Starting DHCP client...
Starting telnet server...
Setting up console ttyS0...
Starting Web Server...
Starting Lighttpd Web Server: lighttpd.
Starting odnrfog-scm application...

snapper login: 1970-01-01 00:00:05: (log.c.75) server started

snapper login:

Re: I2C Voltage Level Problem: < 2.0V

andre — Wed, 05 May 2010 20:20:44 -0600

Do you get the i2c timeouts for both? Can you send through the entire boot log, including the above commands? (from power-on, to Linux prompt).

Andre

Re: I2C Voltage Level Problem: < 2.0V

pteh — Wed, 05 May 2010 20:12:39 -0600

Hi Andre,

It doesn't help. Doing the following and booting from NFS, I2C still reads < 2.0V.
But doing the following and booting from Flash, I2C reads 3.3V.

Snapper> max7311 0 3 config 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> max7311 0 3 output 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> max7311 0 2 config 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> max7311 0 2 output 0
SR: 0xf00d, bit = 2
at91_i2c: timeout 1
Snapper> run nfs_boot

The only different I can see is booting from Flash and booting from NFS. Maybe there is something different in both booting process?

Re: I2C Voltage Level Problem: < 2.0V

andre — Wed, 05 May 2010 19:39:33 -0600

Can you try running the following from U-Boot after a power on, but before either of the two boot sequences?

max7311 0 3 config 0
max7311 0 3 output 0
max7311 0 2 config 0
max7311 0 2 output 0

This forces on some of the power domains.

Re: I2C Voltage Level Problem: < 2.0V

pteh — Wed, 05 May 2010 16:42:00 -0600

It's:

SNAPPER9260/8G20 Rev 1
17 Feb 2009

Re: I2C Voltage Level Problem: < 2.0V

andre — Wed, 05 May 2010 15:14:58 -0600

Ok, I think we're nearly there. Can you tell me the revision of the Snapper 9260 module you've got? It is written in the silk screen, close to the Sodimm connector, near the right-hand side. It will have a revision, and a build date.

Regards,
Andre

Re: I2C Voltage Level Problem: < 2.0V

pteh — Tue, 04 May 2010 23:22:58 -0600

Hi Andre,

See the following:

In Scenario 1:

root@snapper:~$ gpiotool AUD_PWR_EN_N
GPIO AUD_PWR_EN_N: output low

In Scenario 2:

root@snapper:~$ gpiotool AUD_PWR_EN_N
Polarity 1 error: Operation not permitted [1]

Re: I2C Voltage Level Problem: < 2.0V

andre — Tue, 04 May 2010 22:54:41 -0600

Can you tell me the state of AUD_PWR_EN_N using gpiotool?

Regards,
Andre

Re: I2C Voltage Level Problem: < 2.0V

pteh — Tue, 04 May 2010 22:47:24 -0600

Hi Andre,

In Scenario 2, the voltage level is still < 2.0V after changing to peripheral A.

root@snapper:~$ gpiotool A23 A
root@snapper:~$ gpiotool A24 A
root@snapper:~$ cat /proc/gpio/GPIOA23
GPIOA23 [55]: set input [periph A]
root@snapper:~$ gpiotool A23
GPIO A23: input high: periph A
root@snapper:~$ cat /proc/gpio/GPIOA24
GPIOA24 [56]: set input [periph A]
root@snapper:~$ gpiotool A24
GPIO A24: input high: periph A

Re: I2C Voltage Level Problem: < 2.0V

andre — Tue, 04 May 2010 22:40:35 -0600

Can you change them both to peripheral A using gpiotool, and then send the same output again, as well as check the voltages?

gpiotool A23 A
gpiotool A24 A

Regards,
Andre

Re: I2C Voltage Level Problem: < 2.0V

pteh — Tue, 04 May 2010 22:33:45 -0600

In Scenario 1:

root@snapper:~$ cat /proc/gpio/GPIOA24
GPIOA24 [56]: set input [GPIO]
root@snapper:~$ gpiotool A24
GPIO A24: input high: GPIO
root@snapper:~$
root@snapper:~$
root@snapper:~$ cat /proc/gpio/GPIOA23
GPIOA23 [55]: set input [GPIO]
root@snapper:~$ gpiotool A23
GPIO A23: input high: GPIO
root@snapper:~$

In Scenario 2:

root@snapper:~$ cat /proc/gpio/GPIOA24
GPIOA24 [56]: set input [GPIO]
root@snapper:~$ gpiotool A24
GPIO A24: input high: GPIO
root@snapper:~$
root@snapper:~$
root@snapper:~$ cat /proc/gpio/GPIOA23
GPIOA23 [55]: set input [GPIO]
root@snapper:~$ gpiotool A23
GPIO A23: input high: GPIO

Re: I2C Voltage Level Problem: < 2.0V

andre — Tue, 04 May 2010 22:12:25 -0600

Sorry for the delay in responding to this. Could you supply the output from /proc/gpio/GPIOA24 and /proc/gpio/GPIOA23 for the various boot circumstances?

Regards,
Andre

Re: I2C Voltage Level Problem: < 2.0V

pteh — Tue, 20 Apr 2010 17:15:00 -0600

Is there no answer to solve this problem?

Re: I2C Voltage Level Problem: < 2.0V

pteh — Wed, 07 Apr 2010 21:01:55 -0600

To add more information:

In Scenario 1:
7. When I2C Voltage Level has reached 3.3V, issuing reboot in shell login, issuing reset in u-boot prompt and pressing reset switch on QSK board, then boot from NFS Server (as in Scenario 2), I2C Voltage Level stays at 3.3V

In Scenario 2:
7. Issuing reboot in shell login, issuing reset in u-boot prompt and pressing reset switch on QSK board, then boot from NAND (as in Scenario 1), I2C Voltage Level stays below 2.0V

I2C Voltage Level Problem: < 2.0V

pteh — Wed, 07 Apr 2010 20:17:03 -0600

Hi,

I'm running into a problem with physical I2C voltage level.

See the following scenarios. I'm using QSK9260.

Scenario 1:
1. Power Cycle
2. Boot from NAND
3. I2C pins during boot-up reads < 2.0V
4. Soon, still during boot-up, it bumps back to 3.3V (NOTE: sometimes it stays < 2.0V)
5. Once it reached 3.3V, issuing reboot in shell login, issuing reset in u-boot prompt and pressing reset switch on QSK board, I2C voltage level always read 3.3V. I won't see point 3 above
6. If power cycle again, it goes back to point 3

Scenario 2:
1. Power Cycle
2. Enter U-Boot prompt
3. Boot from NFS Server
4. I2C Voltage Level always read < 2.0V
5. Issuing reboot in shell login, issuing reset in u-boot prompt and pressing reset switch on QSK board, I2C voltage level always read < 2.0V
6. Power Cycle and repeat from point 2 above doesn't help

Is there something going on during NAND boot? Can you please tell me if there is a GPIO pin/register in Snapper 9260 that needs to be set during boot-up to bring I2C voltage level to 3.3V?

There is no data transmitted on the above scenarios.

Regards,

pteh

How to enable watchdog

Stephen — Mon, 29 Mar 2010 18:31:40 -0600

Hello,

How can I enable watchdog?

In Linux, I get this:
AT91SAM9 Watchdog: sorry, watchdog is disabled

Re: X Windows and VNC Server

andre — Mon, 29 Mar 2010 18:18:00 -0600

Unfortunately, as the Snapper9260 does not have a native framebuffer, we do not have an xserver built for it.

I would recommend having a look at the kdrive xserver, using a virtual frame buffer. Try the packages from the angstrom distribution, as this is very complete and will definitely include what you're after.

Regards,
Andre

Re: Run UBI on NAND flash

andre — Mon, 29 Mar 2010 18:16:59 -0600

Stephen,
I'm not entirely sure about the relative quality of the wear levelling. I would generally still recommend YAFFS. Although it isn't in mainline, it has a very well proven history of performance in commercial quality devices, where as I don't think UBI has quite the same history.

However UBI does seem to be the way things are moving. At this stage we don't anticipate migrating it into our U-Boot image, however the board specific aspects of our U-Boot image are quite minimal for the Snapper 9260, and so porting a newer U-Boot to the unit would not be difficult if it were required.

Regards,
Andre

Re: Run UBI on NAND flash

Stephen — Mon, 29 Mar 2010 17:57:21 -0600

Thank you for your response.

I managed to get UBIFS to work now. UBIFS has better wear leveling algorithm than YAFFS and it's in mainline kernel since 2008.

Do you plan to add UBIFS support to u-boot?

X Windows and VNC Server

mylesdw — Wed, 24 Mar 2010 18:05:22 -0600

I'm trying to get a X and a VNC server running on our 9260 without much success. Do you folk have any binaries or some instructions?

Any help would be very welcome

Thanks

Re: Win CE 6.0

andre — Wed, 24 Mar 2010 14:16:06 -0600

Hi Vinoth,
Unfortunately we cannot do this driver development for you. For a general reference on doing this work have a look at the MSDN article on WinCE 6.0 driver development:
[msdn.microsoft.com]
[www.ttcx.com]

Regards,
Andre

Win CE 6.0

vinoth006 — Wed, 24 Mar 2010 06:41:13 -0600

hello sir,,

I am new to win CE i want to make a driver control in win ce 6.0 for the LCD controller.Could you please help me how to write the code in visual studio 2005.

Thank You
Vinoth.

Re: Run UBI on NAND flash

andre — Tue, 23 Mar 2010 14:28:09 -0600

Stephen,
It is possible to run UBI on its own partition. We do not use it in general, as we use YAFFS for the filesystem, and the other areas are quite simple. YAFFS does its own bad block management & wear leveling, and is generally more mature than UBI.

Can you tell me what you plan on using it for?

Regards,
Andre

Run UBI on NAND flash

Stephen — Mon, 22 Mar 2010 23:21:01 -0600

Hello,

Is it possible to run UBI on the entire NAND flash (mtd device), then have the bootloader, kernel, and root filesystem running on top of UBI?

Or even run UBI on a partition of the NAND flash?

Thanks.

Re: Updating kernel and File System

andre — Sun, 21 Mar 2010 18:57:14 -0600

The YAFFS images require the OOB data to be written as well as the standard NAND data. NAND images a little bit tricky in this way. U-Boot does not include support for writing OOB images by default. The easiest method is to use the SAMBA tool, which supports raw images using the "nand_write_raw_file" command. Alternatively you can use the mtdtool program from within Linux, using the mtdtool --write_raw option.

Regards,
Andre

Re: Updating kernel and File System

Stephen — Thu, 18 Mar 2010 23:50:03 -0600

Hi,

How do I load my filesystem into flash from u-boot?

I've set up a directory that is to be my target filesystem, with all my cross-compiled binaries there. I used Bluewater Systems mkyaffs2image to make the yaffs image.

To load my yaffs image to snapper's u-boot, I used:
tftp 0x21100000 rootfs.yaffs
nand erase 0x480000 [my rootfs partition size]
nand write 0x21100000 0x480000 [my rootfs.yaffs length]

At this point, I expect to see my filesystem in mtdblock4 from Linux, but there's nothing in mtdblock4. I booted from a ramdisk, mounted mtdblock, but don't see any file inside.

What did I do wrong and how do I correct it?

Any help is appreciated. Thanks in advance.

Stephen

Re: U-boot flash partitions

Stephen — Wed, 17 Mar 2010 21:35:03 -0600

What is the best way to load my filesystem into the split "Filesystem" partition?