From: Daniel W. <wa...@mo...> - 2013-06-29 19:00:21
|
Hi, Sorry was on vacation, therefore I saw these messages a bit late. Maybe I can shed some light on the topic. On 06/23/2013 03:16 AM, Takashi Sakamoto wrote: > But actually you work with BeBoB chip. Most implementation is done by > FFADO developers (and I respect their work). So it's enough you arrange > the current codes for Firewire 1814. > > > I'm sill looking through code trying to understand how to workaround the > > problem with extended plug info command. Should I implement new plug > > class specially for m-audio bibob? > > BeBoB ;) > I know the windows driver and FW1814 don't use the "Extended Plug Info" > and "Extended Stream Format". So I think it good to implement "what to > know via these command" inner FFADO. So the FW1814 and also FW410 are based on a early version of the BeBoB firmware. Also M-Audio requested the special behaviour on the bootup you have noticed to be added to the firmware. The FW1814/FW410 will boot on default into the bootloader mode. The magic command string you need to send, is nothing else, then telling the bootloader to load the firmware stored in the flash chips. If you are able to solder a bit you can add some pins an attached them to a null modem cabel. Then you can see via the serial terminal whats happening on the device. There is even a simple shell which allows you to reconfigure etc the device. I also tried to get the FW410 working but didn't get to far. There was something going pretty wrong pretty early on. I can't remember the details and I don't have any device to play with at this point. I'll check my notes if I can find anything useful. BTW, it is really nice that someone is working on these devices! Thanks! cheers, daniel |