AMB Laboratories DIY Audio

[ds23man]

I just finished a similar project yesterday using an ADUM 1250 chip. This is working fine and additionally provides galvanic isolation between the 5V and 3.3V side.

Cheers

Thomas

I did it the "linux" way, two fet's. Did not have two tubes available Will check it tonight with a scope.

Regards Gerhard

[ds23man]

Strange,

In the cs3318 datasheet the chipadres is binary 1000000b where b is the read or write bit and they mention this adres is 1B in Hex????
What is the correct hex adress I have to use?

Regards Gerhard

[linux-works]

ignore the r/w bit and shift things over by 1 to the right. use that addr.

arduino i2c is like that...

[ds23man]

So it will be 0100 0000 or 40 in hex if i understand correctly, but 1b is 0001 1011????

[ds23man]

Please correct me if I am wrong:

1000 0000 = 80 hex writing adress
1000 0001 = 81 hex reading adress

Using wire:

Shift 1 to the right:

0100 0000 = 40 hex adress
So I have to use 0x40 ?

Regards Gerhard

[ds23man]

Ah nice,

Mixed up 2 wires on the breadboard: output 8 connected to ground and groundreference 8 not connected!

Yes, there was smoke and a red burning dot on the CS3318

Will order a new one with a new smartboard!

Regards Gerhard

[linux-works]

but maybe some channels can still be used, for test? or maybe the digital engine is still able to talk?

bad luck. sorry you ran into it. and when its an expensive chip, it hurts even more. and even yet more when it was an effort to hand solder it ;(

[linux-works]

Please correct me if I am wrong:

1000 0000 = 80 hex writing adress
1000 0001 = 81 hex reading adress

Using wire:

Shift 1 to the right:

0100 0000 = 40 hex adress
So I have to use 0x40 ?

Regards Gerhard

I know I was not able to use the 'normal' address in arduino; but maybe there was a bug that we all just got used to and worked around.

I used 0xA7 or A0 (if all user addr bits are 0) for the mcp23008 chip and yet its supposed to be addressed at 0x20 !

I do know that the r/w bit is not part of the *arduino* style i2c addr. they think that i2c addr is the same and r/w is just an attribute of a message (which I think does make i2c a lot easier to handle). suppose I had to have a mailing address for you when I sent to you, but when you wrote to me you used a modified form on your return address. that would confuse everyone and that's what i2c is like, its 'address' varies depending on whether you are reading or writing. that's abursd (lol) and so they drop the r/w part and you 'open' a connection to a device by its i2c base address and the r/w bit gets added based on the read/write commad you issue.

in short, people seem to try the addr or the 'addr shifted over one' until the device responds, then tell the world what the arduino uses to talk to device XYZ so that others won't have to do this experiment

[ds23man]

but maybe some channels can still be used, for test? or maybe the digital engine is still able to talk?

bad luck. sorry you ran into it. and when its an expensive chip, it hurts even more. and even yet more when it was an effort to hand solder it ;(

Well, you can fry an egg on it now with the power on.

Regards

[ds23man]

I know I was not able to use the 'normal' address in arduino; but maybe there was a bug that we all just got used to and worked around.

I used 0xA7 or A0 (if all user addr bits are 0) for the mcp23008 chip and yet its supposed to be addressed at 0x20 !

I do know that the r/w bit is not part of the *arduino* style i2c addr. they think that i2c addr is the same and r/w is just an attribute of a message (which I think does make i2c a lot easier to handle). suppose I had to have a mailing address for you when I sent to you, but when you wrote to me you used a modified form on your return address. that would confuse everyone and that's what i2c is like, its 'address' varies depending on whether you are reading or writing. that's abursd (lol) and so they drop the r/w part and you 'open' a connection to a device by its i2c base address and the r/w bit gets added based on the read/write commad you issue.

in short, people seem to try the addr or the 'addr shifted over one' until the device responds, then tell the world what the arduino uses to talk to device XYZ so that others won't have to do this experiment

So you tell me nobody knows exactly how the addressing in the wire library works????

Regards Gerhard