Re: fwcontrol: unknown format 0x1e

2005-09-30 Thread Lowell Gilbert
Erik Nørgaard [EMAIL PROTECTED] writes:

 Lowell Gilbert wrote:
 
  I don't know anything about Firewire, and can't seem to get through to
  the specs, but a look at the code tells me that the only format that
  receive routine knows is CIP_FMT_DVCR (which happens to be zero).
  You'll need someone who can figure out what the format you're getting
  means, and how to handle it.  The recent comitters to the fwcontrol
  utility would be a good place to start.
 
 Just when you wrote it occured to me that I should try downgrading
 since I'm on 6.0-BETA4. I looked at the time stamps of the code and it
 appears that changes has been applied to fwdev.c in august.

Do you have reason to think it worked in the past?  It doesn't look
like anything changed that would affect the format check.

 I hope that works, otherwise I'd try going futher back in time,
 changes were applied to fwcontrol.c and fwohci_pci.c in may. And if I
 still have no luck, back to march.
 
 I'm a bit currious: Looking at 5.4 STABLE all files in sys/dev/firewire
 have timestamp 2005/01/30 but in 6.0-BETA4 files have timestamp
 2005/01/06 or some other date... Any explanation for this?

MFC on 30 January.  
http://be-well.ilk.org/FreeBSD/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: fwcontrol: unknown format 0x1e

2005-09-29 Thread Lowell Gilbert
Erik Nørgaard [EMAIL PROTECTED] writes:

 I'm a newbie when it comes to firewire, in fact I have never had it
 working because I never had a device to connect. Then recently I
 bought a Canon MVX200 (PAL) video cam. But when trying to transfer the
 video using fwcontrol as described in the man page I get:
 
 charm# fwcontrol -R test.dv
 (EAGAIN)
 (EAGAIN)
 fwcontrol: unknown format 0x1e

I don't know anything about Firewire, and can't seem to get through to
the specs, but a look at the code tells me that the only format that
receive routine knows is CIP_FMT_DVCR (which happens to be zero).  

You'll need someone who can figure out what the format you're getting
means, and how to handle it.  The recent comitters to the fwcontrol
utility would be a good place to start.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: fwcontrol: unknown format 0x1e

2005-09-29 Thread Erik Nørgaard

Lowell Gilbert wrote:


I don't know anything about Firewire, and can't seem to get through to
the specs, but a look at the code tells me that the only format that
receive routine knows is CIP_FMT_DVCR (which happens to be zero).  


You'll need someone who can figure out what the format you're getting
means, and how to handle it.  The recent comitters to the fwcontrol
utility would be a good place to start.


Just when you wrote it occured to me that I should try downgrading since 
I'm on 6.0-BETA4. I looked at the time stamps of the code and it appears 
that changes has been applied to fwdev.c in august.


I hope that works, otherwise I'd try going futher back in time, changes 
were applied to fwcontrol.c and fwohci_pci.c in may. And if I still have 
no luck, back to march.


I'm a bit currious: Looking at 5.4 STABLE all files in sys/dev/firewire
have timestamp 2005/01/30 but in 6.0-BETA4 files have timestamp 
2005/01/06 or some other date... Any explanation for this?


Well, going back in time on this will be my weekend project...

Thanks for replying!

Cheers, Erik

--
Ph: +34.666334818   web: http://www.locolomo.org
S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt
Subject ID:  A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9
Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


fwcontrol: unknown format 0x1e

2005-09-28 Thread Erik Nørgaard

Hi,

I'm a newbie when it comes to firewire, in fact I have never had it 
working because I never had a device to connect. Then recently I bought 
a Canon MVX200 (PAL) video cam. But when trying to transfer the video 
using fwcontrol as described in the man page I get:


charm# fwcontrol -R test.dv
(EAGAIN)
(EAGAIN)
fwcontrol: unknown format 0x1e

I have asked on the list before, and on other lists as well as searched 
google with little luck. Eventually some indicated it may be the brand 
since he had had bad experiences with other Canon hardware. The cam was 
returned within the 15 trial period I had.


I then bought a Sony HC39E but get the exact same error suggesting that 
the problem is in the other end. According to the hardware list my 
firewire chipset is supported.


Please, any hints on how to solve this will be highly appreciated.

Thanks, Erik

Debug stuff follows:

System:

FreeBSD charm 6.0-BETA4 FreeBSD 6.0-BETA4 #0:
Tue Sep  6 21:16:56 CEST 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

dmesg:
fwohci0: Ricoh R5C552 mem 0xe580-0xe58007ff irq 11 at device 10.2 
on pci0

fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:e0:18:00:03:09:43:39
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: IEEE1394(FireWire) bus on fwohci0
sbp0: SBP-2/SCSI over FireWire on firewire0
fwohci0: Initiate bus reset
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)

Connecting the firewire device creates the following output (from
/var/log/messages):

fwohci0: BUS reset
fwohci0: node_id=0x8800ffc0, gen=11, non CYCLEMAST ER mode
firewire0: 2 nodes, maxhop = 1, cable IRM = 0 (me)
fwohci0: txd err= 3 miss Ack err
firewire0: bus_explore node=1 addr=0x400 resp=22 retry=1
fwohci0: txd err= 3 miss Ack err
firewire0: bus_explore node=1 addr=0x400 resp=22 retry=2
fwohci0: txd err= 3 miss Ack err
firewire0: bus_explore node=1 addr=0x400 resp=22 retry=3
fwohci0: txd err= 3 miss Ack err
firewire0: bus_explore node=1 addr=0x400 resp=22 retry=4
firewire0: bus_explore failed for 1 nodes
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc0, gen=12, CYCLEMASTER mode
firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me)
fwohci0: BUS reset
fwohci0: node_id=0x8800ffc0, gen=13, non CYCLEMASTER mode
firewire0: 2 nodes, maxhop = 1, cable IRM = 1

There is no /dev/firewire0

Output from fwcontrol and dvrecv tools:

Script started on Tue Sep  6 23:00:04 2005
charm# fwcontrol -r

charm# fwcontrol -t
crc_len: 4 generation:7 node_count:2 sid_count:2
id link gap_cnt speed delay cIRM power port0 port1 port2 ini more
001   5  S400 01   -1W P - 10
011   5  S100 010W C - -   00

charm# fwcontrol -p
=== base register ===
0x01 0x3f 0xe2 0x41 0xcc 0x03 0x00 0x20
Physical_ID:0  R:0  CPS:1
RHB:0  IBR:0  Gap_Count:63
Extended:7 Num_Ports:2
PHY_Speed:2 Delay:1
LCtrl:1 C:1 Jitter:1 Pwr_Class:4
WDIE:0 ISBR:0 CTOI:0 CPSI:0 STOI:0 PEI:0 EAA:1 EMC:1
Max_Legacy_SPD:0 BLINK:0 Bridge:0
Page_Select:1 Port_Select0

=== page 0 port 0 ===
0xf6 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Astat:3 BStat:3 Ch:0 Con:1 RXOK:1 Dis:0
Negotiated_speed:0 PIE:0 Fault:0 Stanby_fault:0 Disscrm:0 B_Only:0
DC_connected:0 Max_port_speed:0 LPP:0 Cable_speed:0
Connection_unreliable:0 Beta_mode:0
Port_error:0x0
Loop_disable:0 In_standby:0 Hard_disable:0

=== page 0 port 1 ===
0xf8 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Astat:3 BStat:3 Ch:1 Con:0 RXOK:0 Dis:0
Negotiated_speed:0 PIE:0 Fault:0 Stanby_fault:0 Disscrm:0 B_Only:0
DC_connected:0 Max_port_speed:0 LPP:0 Cable_speed:0
Connection_unreliable:0 Beta_mode:0
Port_error:0x0
Loop_disable:0 In_standby:0 Hard_disable:0

=== page 1 ===
0x01 0x00 0x00 0x00 0x74 0x00 0x55 0x20
Compliance:1
Vendor_ID:0x74
Product_ID:0x005520
charm# fwcontrol -c 0
first quad: 0x041ceb3e info_len=4 crc_len=28 crc=0xeb3e(OK)
bus_name: 0x31333934
irmc:1 cmc:1 isc:1 bmc:1 pmc:0
cyc_clk_acc:100 max_rec:10 max_rom:0
generation:3 link_spd:2
EUI64: 00-e0-18-00-03-09-43-39
root_directory: len=0x0005(5) crc=0x8a4a(OK)
0c(I:0c) 0083c0 node_capabilities:
03(I:03) acde48 module_vendor_ID:
81(L:01) 03 text_leaf: len=7 crc=0x82ed(OK) FreeBSD Project
04(I:04) 0927e2 hardware_version:
81(L:01) 09 text_leaf: len=9 crc=0x0412(OK) charm

charm# fwcontrol -R test.dv
(EAGAIN)
(EAGAIN)
fwcontrol: unknown format 0x1e

charm# fwcontrol -R test.dv
PAL
0fwcontrol: unknown format 0x1e

charm# fwcontrol -R test.dv
PAL
0fwcontrol: unknown format 0x1e

charm# sysctl hw.firewire.try_bmr=0
hw.firewire.try_bmr: 1 - 0
charm# fwcontrol -r
charm# fwcontrol -R test.dv
PAL
0fwcontrol: unknown format 0x1e

charm# fwcontrol -R test.dv
(EAGAIN)
(EAGAIN)
fwcontrol: unknown format 0x1e

charm# fwcontrol -u 0 -R test.dv
(EAGAIN)
(EAGAIN)
fwcontrol: unknown format 0x1e

charm# dvrecv test.dv
Found AV/C device
Vendor: Canon
Model: MVX200
waiting

fwcontrol: unknown format 0x1e

2005-09-09 Thread Erik Nørgaard

Hi,

I am trying to transfer digital video over firewire from my camera
(Canon MXV200, PAL) to my laptop using fwcontrol, but whenever I try I 
get something like this:


# fwcontrol -R tmp/test.dv
(EAGAIN)
(EAGAIN)
fwcontrol: unknown format 0x1e

If I first press play then run the command I get:

# fwcontrol -R tmp/test.dv
PAL
0fwcontrol: unknown format 0x1e

The format code sometimes varies, and I have also got input/output 
error. Repeating can cause system to crash! or other applications to 
coredump.


Trying with sysctl hw.firewire.try_bmr=0 as suggested in the man-page 
does not change anything.


I have tried to use dvrecv and it correctly identifies the camera/model 
but fails to read a single frame.


What am I missing?

Thanks, Erik

System:

FreeBSD 6.0-BETA4 #0: Tue Sep  6 21:16:56 CEST 2005
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC

Turning on the device results in the following in /var/log/messages:

kernel: fwohci0: BUS reset
kernel: fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode
kernel: firewire0: 2 nodes, maxhop = 1, cable IRM = 1 (me)
kernel: firewire0: bus manager 1 (me)
kernel: fwohci0: txd err= 3 miss Ack err
kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=1
kernel: fwohci0: txd err= 3 miss Ack err
kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=2
kernel: fwohci0: txd err= 3 miss Ack err
kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=3
kernel: fwohci0: txd err= 3 miss Ack err
kernel: firewire0: bus_explore node=0 addr=0x400 resp=22 retry=4
kernel: firewire0: bus_explore failed for 1 nodes
kernel: fwohci0: BUS reset
kernel: fwohci0: node_id=0xc800ffc0, gen=3, CYCLEMASTER mode
kernel: firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me)
kernel: firewire0: bus manager 0 (me)
kernel: fwohci0: BUS reset
kernel: fwohci0: node_id=0x8800ffc0, gen=4, non CYCLEMASTER mode
kernel: firewire0: 2 nodes, maxhop = 1, cable IRM = 1
kernel: firewire0: bus manager 0 (me)
kernel: firewire0: New S100 device ID:859e1a7e


--
Ph: +34.666334818   web: http://www.locolomo.org
S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt
Subject ID:  A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9
Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]