At 48kHz, the I2S bit clock was only 32.FS, not 64.FS anymore. It looks like a feature of the driver. This needs further investigations. I might have to create a special driver, that only enables 48kHz with BCLK=64.FS. Update: I had a look in the driver code. Looks like there is a bug in the driver. 'I design robots for pharmaceutical research, and was having problems with an inter FPGA serial bus. After 35 years of hardware design, it became obvious that we must bite the bullet and splash out $10k on some Agilent or Tek kit. And then I saw Intronix on the web.
I am using the latest 2.6.18 (2.6.18-avr1) patch from avr32linux.org that I applied against the latest 2.6.18.5 kernel.
When I try to do an I2C transfer, the driver crash.
Here is the source code of my test application:
And here is the dmesg
The first ioctl to set the slave address works fine.
The second ioctl to execute a list of transfers seems to be recognized corectly by the driver, with first a write of 5 bytes then a read of 6 bytes, but when the transfer starts everthind crashes ???
Download Intronix Driver Win 10
I am using the latest 2.6.18 (2.6.18-avr1) patch from avr32linux.org that I applied against the latest 2.6.18.5 kernel.
When I try to do an I2C transfer, the driver crash.
Here is the source code of my test application:
Download Intronix Driver Pc
And here is the dmesg
Download Intronix Driverpack
The first ioctl to set the slave address works fine.
The second ioctl to execute a list of transfers seems to be recognized corectly by the driver, with first a write of 5 bytes then a read of 6 bytes, but when the transfer starts everthind crashes ???