Introducing the Buffalo III-SE-Pro 9028/9038

[Russ White]

Yeah - you should not get any pops etc as long as your source is not sending any. 🙂

As to your DSD512 playback funkiness - I would look at the source since I have had no issues playing DSD512 from BBB in pure sync mode - though Amanero is more problematic (I suspect that's down to it's own slave mode firmware needing some work)

Thanks for the report!

Cheers!
Russ

 

[Paul M]

I'm currently on firmware 2003be_71A for the Amanero, but not in slave mode since I feed it to the FIFO. I'll try some of the earlier ones and see how it affects the noise.

Thanks Russ!

Paul

 

[twluke]

-snip- Sounds very good! The only issue I have is that with DSD512 I get a high pitched constant noise superimposed on the music, and only in the right channel. Changing back to DSD256 the noise completely disappears.

I think this high pitched noise, if it is heard like a chirpy sound, should be the issue of Amanero firmware. Anyway congratulations for your modified B3SEpro firmware well working.

 

[ichiban]

Does this Sync mode also have the same positive effect for CD sample rate audio, or only the high rates i.e. DSD ?

 

[twluke]

Does this Sync mode also have the same positive effect for CD sample rate audio, or only the high rates i.e. DSD ?

Applicable to everything. 🙂

 

[sbelyo]

Here is experimental (I have no need for it myself) Dual-Mono firmware for the B3SE-Pro. <snip>

I'm planning on experimenting with this once I get a regular stereo 9028 running.

I'd need one of those Tiny AVR programmers to burn the hex file to the controller chip correct?

Is it ok to use another 9028 and IVY III?

 

[francolargo]

Quick Q as I update my old I2C for the new boards:

B latch_vol :1;
B use_only_ch1_vol :1;
B stereo_mode :1;

Confirming - the stock firmware enables each of these three functions from register 15?

 

[Russ White]

This is what I did:

Buffalo-III-SE-Pro-On-Board-Firmware/Buffalo.c at 8c1b8a98a44933f9738452c19afcb6468af41bd8 * twistedpearaudio/Buffalo-III-SE-Pro-On-Board-Firmware * GitHub

Cheers!
Russ

 

[francolargo]

Awesome. Thanks Russ! I didn't see this file earlier. Will start by (hopefully) implementing your stock settings. Then, I can hardly wait to experiment and will add filter options, etc. as time and experimentation allow.

My Python interface uses an asyncore server, adapted from NetIO. I just noticed the TPA logo at the bottom of this page - though the picture rotates... 🙂 [I use NetIO to easily create I2C control pages on all my iOS devices.]

Cheers!
Frank

 

[AndriyOL]

Hi Russ.

When 8ch. version will be available? I don't need 8ch I\V stage. Going to use voltage out mode.

Thanks.

 

[francolargo]

I seem to have hit a snag and could use any suggestions. When using the new Pro boards with the firmware chip removed, is there any reason that the I2C busses would not initialize correctly for 3-wire (including ground) transfer? My I2C multiplexer doesn’t seem to find the DACs. The older 9018s worked fine in the exact same setup - I simply swapped them out.

TIA,

Frank

 

[Dimdim]

You need to take care of the RESET line..

 

[francolargo]

They don’t reset on power on???

You need to take care of the RESET line..

Edit: Reset the multiplexer or the 9028? I thought, from previous experience, that both reset at power on...

 

[BrianDonegan]

// Main
int main(int argc, char **argv) {
	// keep DAC in reset
	sbi(DDRB, PIN1);
	cbi(PORTB, PIN1);
	_delay_ms(1500);
	// bring DAC out of reset
	sbi(PORTB, PIN1);
	initialize();
	.
	.
	.

 

[francolargo]

Apologies, Brian & Dimdim! My hobbyist's brain has been in 'medicine mode' for too long...

Backing up: Will I need on-board firmware simply to change the power-on state and thereby initialize/activate the I2C bus? [There's a "learning opportunity"! ] Or is there an easier way?

F.

 

[Dimdim]

The 9028's reset pin is brought out to one of the Buffalo's I/O pins, so you just need to control that pin with your uC.

 

[francolargo]

The 9028's reset pin is brought out to one of the Buffalo's I/O pins, so you just need to control that pin with your uC.

Thanks! So double checking... The reset is accomplished with that pin low, after which running requires it to be held high? That’s what I surmise from your “9028 on a B3” blog from a year ago... That will be easy to manage.

Frank

 

[Dimdim]

Exactly. Just keep the pin low for a couple of seconds, while everything powers-up, and then pull it up. You should then be able to access the registers.

 

[francolargo]

One last question for anybody... How much current would you guess is required to hold pin 8 of the DAC high? What is typical 'these days'? [I'm considering an analog solution here - an RC pair that charges in 2 seconds...]

 

[Claire Fox]

Hopefully a simple question. I have built a IIIse based dac using a Raspberry Pi using i2c and a Kali Reclocker as a dedicated input I would also like to add some spdif inputs to the IIIse (CD Transport, another Pi for video streaming and an ADC — all via coaxial spdif ) and I am a little bit confused about what is needed to add three spdif inputs and switch between the i2c and the spdif inputs.

Can someone explain what is needed, I assume the 4:1 Muxer and how to switch between the i2c input and the Spdif Muxer

Also how is switching between the built in spdif and i2c input managed?

I am sorry if this is explained clearly somewhere I have looked but I cannot see it.