[Soekris] net4801 JP5 User I/O with gpioctl

2012-03-15 Thread Ben Greenfield
Hey All,

I have a net4801running what I think is a highly modified OpenBSD 3.6. I'm 
trying to use the gpioctl and although it appears to work on the command line I 
can see no evidence of it working with my multi-meter.

I have done a lot of looking at this topic on the internet and I found various 
discussions on using gpioctl and some recommendations about configuring the 
pins prior to  entering the secure level 1.
My systems happens to have an /etc/rc.securelevel mine looks like this.


# cat /etc/rc.securelevel  
#   $FabBSD$
#   $OpenBSD: rc.securelevel,v 1.16 2004/07/06 04:05:03 deraadt Exp $
#
# site-specific startup actions, daemons, and other things which
# can be done BEFORE your system goes into securemode.  For actions
# which should be done AFTER your system has gone into securemode
# please see /etc/rc.local

# This is the desired security level
securelevel=1

echo -n 'starting pre-securelevel daemons:'

#
# Place local actions here.
#
/usr/sbin/gpioctl -c 01 out;
/usr/sbin/gpioctl -c 03 out;


echo '.'


The boot process produces this output which makes me think it is working:

starting pre-securelevel daemons:pin 1: caps: in out, flags: - out
pin 3: caps: in out, flags: - out
.
setting kernel security level: kern.securelevel: 0 - 1


Finally I think it is not working because I expect this command:

# gpioctl -d /dev/gpio0 1 0

to make either pin 1 or pin4 of JP5 low or zero voltage. 

I also expect it to hold that value until I change it with another command.

here is a transcript of me interrogating JP5 pins.

# gpioctl -d /dev/gpio0 1   
pin 1: state 1
# gpioctl -d /dev/gpio0 1 0
pin 1: state 0 - 0
# gpioctl -d /dev/gpio0 1   
pin 1: state 1
# gpioctl -d /dev/gpio0 3 
pin 3: state 1
# gpioctl -d /dev/gpio0 3 0
pin 3: state 0 - 0
# gpioctl -d /dev/gpio0 3   
pin 3: state 1

Interactively I can manually create the ports which also doesn't work.
Here is a transcript:

# gpioctl -d /dev/gpio0 -c 01 out
pin 1: caps: in out, flags: out - out
# gpioctl -d /dev/gpio0 1 
pin 1: state 1
# gpioctl -d /dev/gpio0 1 0   
pin 1: state 0 - 0
# gpioctl -d /dev/gpio0 1   
pin 1: state 1

Finally the verison of gpioctl doesn't support pp in fact it only seems to 
support in and out as flags.
# gpioctl -d /dev/gpio0 -c 01 pp  
gpioctl: GPIOPINCTL: Operation not supported by device


I know I'm not helping myself by using some strange BSD variant but I have 
heard it works. I would like any guidance on how to further investigate the 
issue. My next step will probably be to go to netbsd and see if I can get the 
custom software I need off the old machine.

Any ideas welcome.

Ben


___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech


Re: [Soekris] net6501: Timer problems with Debian, no HPET support detected

2012-03-15 Thread Chris Cappuccio
Darryl Miles [darryl-mailingli...@netbauds.net] wrote:
 Peter Neubauer wrote:
  Linux depends on an ACPI BIOS to provide configuration for the HPET. The
  net6501 does not support ACPI, so Linux does not use the HPET.
 
 Great news on the patch.
 
 
 What is the reason for not having ACPI ?
 

There is no use for it on the net6501. The BIOS implementation is a lot of work.
___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech


[Soekris] net5501 - CF and HDD

2012-03-15 Thread Greg Armer
Hey folks,

I'm having some trouble and couldn't find much info on the net regarding it, so 
I was wondering if any of you may have any ideas.

I have the net5501 with an 8GB Sandisk CF card and a WD1200BEVS 120GB SATA HDD 
running OpenBSD 4.8. The issue I'm having is that I cannot get both the CF card 
and the HDD working at the same time. The CF card is the primary boot device 
and will be read only, while the HDD will store log files and other data that 
is written to frequently.

comBIOS detects both devices without any trouble...


comBIOS ver. 1.32i 20071005  Copyright (C) 2000-2007 Soekris Engineering.

net5501

0512 Mbyte MemoryCPU Geode LX 500 Mhz 

Pri Mas  SanDisk SDCFH-008G  LBA Xlt 974-255-63  7824 Mbyte
Pri Sla  WDC WD1200BEVS-22UST0   LBA Xlt 1024-255-63  117 Gbyte

Slot   Vend Dev  ClassRev Cmd  Stat CL LT HT  Base1Base2   Int 
---
0:01:2 1022 2082 1010 0006 0220 08 00 00 A000  10
0:06:0 1106 3053 0296 0117 0210 08 40 00 E101 A0004000 11
0:07:0 1106 3053 0296 0117 0210 08 40 00 E201 A0004100 05
0:08:0 1106 3053 0296 0117 0210 08 40 00 E301 A0004200 09
0:09:0 1106 3053 0296 0117 0210 08 40 00 E401 A0004300 12
0:20:0 1022 2090 06010003 0009 02A0 08 40 80 6001 6101 
0:20:2 1022 209A 01018001 0005 02A0 08 00 00   
0:21:0 1022 2094 0C031002 0006 0230 08 00 80 A0005000  15
0:21:1 1022 2095 0C032002 0006 0230 08 00 00 A0006000  15

 1 Seconds to automatic boot.   Press Ctrl-P for entering Monitor.
Using drive 0, partition 3.
Loading...
probing: pc0 com0 com1 pci mem[639K 511M a20=on] 
disk: hd0+ hd1+*
 OpenBSD/i386 BOOT 3.15


additionally, the second stage openbsd boot loader detects both devices...


 OpenBSD/i386 BOOT 3.15
switching console to com0
  OpenBSD/i386 BOOT 3.15
boot machine diskinfo
DiskBIOS#   TypeCylsHeads   SecsFlags   Checksum
hd0 0x80label   974 255 63  0x2 0xd5189645
hd1 0x81label   1024255 63  0x2 0xd78c9677
boot 


however OpenBSD does not detect both devices during the remainder of the boot:


# dmesg
OpenBSD 4.8 (GENERIC) #136: Mon Aug 16 09:06:23 MDT 2010
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS (AuthenticAMD 586-class) 500 
MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX
real mem  = 536440832 (511MB)
avail mem = 517705728 (493MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 20/71/05, BIOS32 rev. 0 @ 0xfac40
pcibios0 at bios0: rev 2.0 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc8000/0xa800
cpu0 at mainbus0: (uniprocessor)
amdmsr0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
io address conflict 0x6100/0x100
io address conflict 0x6200/0x200
pchb0 at pci0 dev 1 function 0 AMD Geode LX rev 0x33
glxsb0 at pci0 dev 1 function 2 AMD Geode LX Crypto rev 0x00: RNG AES
vr0 at pci0 dev 6 function 0 VIA VT6105M RhineIII rev 0x96: irq 11, address 
00:00:24:cd:83:ec
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, 
model 0x0034
vr1 at pci0 dev 7 function 0 VIA VT6105M RhineIII rev 0x96: irq 5, address 
00:00:24:cd:83:ed
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, 
model 0x0034
vr2 at pci0 dev 8 function 0 VIA VT6105M RhineIII rev 0x96: irq 9, address 
00:00:24:cd:83:ee
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, 
model 0x0034
vr3 at pci0 dev 9 function 0 VIA VT6105M RhineIII rev 0x96: irq 12, address 
00:00:24:cd:83:ef
ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, 
model 0x0034
glxpcib0 at pci0 dev 20 function 0 AMD CS5536 ISA rev 0x03: rev 3, 32-bit 
3579545Hz timer, watchdog, gpio
gpio0 at glxpcib0: 32 pins
pciide0 at pci0 dev 20 function 2 AMD CS5536 IDE rev 0x01: DMA, channel 0 
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: SanDisk SDCFH-008G
wd0: 1-sector PIO, LBA48, 7641MB, 15649200 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 21 function 0 AMD CS5536 USB rev 0x02: irq 15, version 1.0, 
legacy support
ehci0 at pci0 dev 21 function 1 AMD CS5536 USB rev 0x02: irq 15
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 AMD EHCI root hub rev 2.00/1.00 addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
nsclpcsio0 at isa0 port 0x2e/2: