• The Vendor's Bazaar forum is for commercial offers and transactions. Only unmoderated members can post here.

    diyAudio provides this forum for the convenience of our members, but makes no warranty nor assumes any responsibility. We do not vet any members. Use of this facility is at your own risk. Customers can post any issues in those threads as long as it is done in a civil manner. All diyAudio rules about conduct apply and will be enforced.

Reference DAC Module - Discrete R-2R Sign Magnitude 24 bit 384 KHz

Can i please learn your r core connection experiences for power supply?


I have 4 transformers in my dac as they supply separated dc voltages to different parts. No opamps. Several Salas regs. The important +5v "analogue" line is supplied from the heater output of an R-core designed for valve preamp duties. Compared at least half a dozen transformers for this spot and R-core beat them all.
 

Attachments

  • Screenshot_20211114_115923.jpg
    Screenshot_20211114_115923.jpg
    353.8 KB · Views: 367
  • Screenshot_20211114_120025.jpg
    Screenshot_20211114_120025.jpg
    284.5 KB · Views: 374
  • Screenshot_20211114_120057.jpg
    Screenshot_20211114_120057.jpg
    266.6 KB · Views: 356
  • Screenshot_20211114_120130.jpg
    Screenshot_20211114_120130.jpg
    575.7 KB · Views: 363
I have 4 transformers in my dac as they supply separated dc voltages to different parts. No opamps. Several Salas regs. The important +5v "analogue" line is supplied from the heater output of an R-core designed for valve preamp duties. Compared at least half a dozen transformers for this spot and R-core beat them all.

Thanks for your reply, i have bigger problem than transformers now. 🙂 I cant get sound from dac.
 
Hi all, i finally got my dam1021 and made all connections using 12dcv power supply, amanero i2s and raw output. I've checked j2 header, all voltages are ok. Green link is stabilised while amanero connected via pc. But unfortunately i dont get any sound from speakers.. What could be the problem? I've read old posts and made amanero firmware upgrade.. But i dont understand where to look at next.

Remove the I2S connections and try one of the Spdif module
 
Guys, I'm using DAM 1021 since April 2015, the first version, it's already upgraded with Vref mod, I'm not using the output opamps, installed polymer low ESR decoupling caps on the supply rails, recently also replaced the main DAC PSU with Salas shunt regulator.

View attachment 995491

Together with DAC, I am using Logitech Squeezebox (10+ year-old wireless Wi-Fi player) to provide the I2S signal (3.3V if I remember well) to the DAC. They sound great together, I think better than any multi-bit DAC I ever tried so far.

I use it and keep the PCBs for years on a... shelf... yeah I know 🙂 well, it's time to put it in a nice enclosure.

But before I do that... before I order a specific transformer and chassis I'm wondering if there is anything else to improve, for example in terms of the master clock/FIFO buffer - actually, a few years ago I purchased one from Ian and never used it. Squeezebox has an 11.2896MHz clock, I'm not sure if adding a low jitter clock there will change anything?

Guys, from your personal experience and successful improvements any ideas that I should definitely consider before it will be too late or difficult to implement before ordering the parts? 🙂

If it was me I would replace the 2 6800uf caps to Nichicon Super Through,
Gold Tune or Mundorf M Lytic. What's the logic, well it just sounds better
 
Hi everyone,
I’m afraid I just messed up my dam1021 rev5
It had firmware 1.19 running and I wanted to update to 1.24
I’m running raspiOS (moOde audio player) and couldn’t get the serial connection to work and sent the file. In the end I could and it seemed to work but I got a few retries until the max retries ended the update proces. uManager than hanged so I rebooted the DAC
Now when I connect to serial I get Connected but after +++ no more uManager. It also not locks to music. I rebooted several times but I’m afraid I bricked it.

Any help would be greatly appreciated. Is there a way to reset back to factory settings or anything ??

Kind regards
Maikel
 
Hi everyone,
I’m afraid I just messed up my dam1021 rev5
It had firmware 1.19 running and I wanted to update to 1.24
I’m running raspiOS (moOde audio player) and couldn’t get the serial connection to work and sent the file. In the end I could and it seemed to work but I got a few retries until the max retries ended the update proces. uManager than hanged so I rebooted the DAC
Now when I connect to serial I get Connected but after +++ no more uManager. It also not locks to music. I rebooted several times but I’m afraid I bricked it.

Any help would be greatly appreciated. Is there a way to reset back to factory settings or anything ??

Kind regards
Maikel

Why can't people read, where you get rev 1.24 firmware it says "only for dam1021 rev7"....

Try using the isolated TTL serial port on J3.
 
Last edited:
Sorry Soren. I mean 1.21
Your advise still the same?

No. rev 1.21 should work as they used to do, it's only for the rev7 board there was some change in serial port handling....

You can always force the FPGA firmware to not load by shorting pins on the serial flash shortly at power up, it's U38 pin 5 and 8. You should then enter uManager directly and you can download the firmware as normal.
 
No. rev 1.21 should work as they used to do, it's only for the rev7 board there was some change in serial port handling....

You can always force the FPGA firmware to not load by shorting pins on the serial flash shortly at power up, it's U38 pin 5 and 8. You should then enter uManager directly and you can download the firmware as normal.


Oh man. I’m so happy to read this. The dam is buildin a case on the bottom so I’ll try somewhere coming days and report back
Thanks for your quick reply!!
 
No. rev 1.21 should work as they used to do, it's only for the rev7 board there was some change in serial port handling....

You can always force the FPGA firmware to not load by shorting pins on the serial flash shortly at power up, it's U38 pin 5 and 8. You should then enter uManager directly and you can download the firmware as normal.


Soren,
Could you confirm that I have the right pins? (Before I mess up more)
IMG_5266.jpg
IMG_5271.jpg
According to data sheet wo bond w25q80
Dam1021 is rev5
Thanks a lot
 
@soekris
I tried your suggestion but cannot get it to work. Looks like the serial flashis not reset and I cannot enter uManager

I did not powerdown the board after reset but i did turned on the rapberry pi (and therefore I2S connection) after the reset. I guess that should not be a problem or is it?
What am I doing wrong?
 
@soekris
I tried your suggestion but cannot get it to work. Looks like the serial flashis not reset and I cannot enter uManager

I did not powerdown the board after reset but i did turned on the rapberry pi (and therefore I2S connection) after the reset. I guess that should not be a problem or is it?
What am I doing wrong?

Don't know exactly what you are doing.... To not load the FPGA firmware, you just short those two pins while powering up the dam1021. Then the uManager should enter directly, if not the uC firmware might have been damaged....
 
Don't know exactly what you are doing....
Me neither, the whole serial stuff is way too complicated. But I realize it's just the way it is and probably has advantages too.
Anyway I wanted to update the firmware, filters, everything in the dam1121 firmware and filters rev 1.21.skr
Somehow communication wasn't good and I got a few "Retry 0: NAK on sector" with a message maximum reties reached.
I'm honestly not sure if i updated or not but after turning off and on the DAM I could not reach it anymore. Locking led keeps flashing when feeding it music. It's connected through I2S.



To not load the FPGA firmware, you just short those two pins while powering up the dam1021. Then the uManager should enter directly, if not the uC firmware might have been damaged....
Let's at least make sure I can ever use it again...
I connected it through isolated serial J3, according to my old documentation.
This is my gpio readall;
Code:
pi@moode:~ $ sudo gpio readall
 +-----+-----+---------+------+---+---Pi 2---+---+------+---------+-----+-----+
 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 |     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |
 |   2 |   8 |   SDA.1 | ALT0 | 1 |  3 || 4  |   |      | 5v      |     |     |
 |   3 |   9 |   SCL.1 | ALT0 | 1 |  5 || 6  |   |      | 0v      |     |     |
 |   4 |   7 | GPIO. 7 |   IN | 1 |  7 || 8  | 1 | ALT0 | TxD     | 15  | 14  |
 |     |     |      0v |      |   |  9 || 10 | 0 | ALT0 | RxD     | 16  | 15  |
 |  17 |   0 | GPIO. 0 |   IN | 0 | 11 || 12 | 0 | ALT0 | GPIO. 1 | 1   | 18  |
 |  27 |   2 | GPIO. 2 |   IN | 0 | 13 || 14 |   |      | 0v      |     |     |
 |  22 |   3 | GPIO. 3 |   IN | 0 | 15 || 16 | 0 | IN   | GPIO. 4 | 4   | 23  |
 |     |     |    3.3v |      |   | 17 || 18 | 0 | IN   | GPIO. 5 | 5   | 24  |
 |  10 |  12 |    MOSI |   IN | 0 | 19 || 20 |   |      | 0v      |     |     |
 |   9 |  13 |    MISO |   IN | 0 | 21 || 22 | 0 | IN   | GPIO. 6 | 6   | 25  |
 |  11 |  14 |    SCLK |   IN | 0 | 23 || 24 | 1 | IN   | CE0     | 10  | 8   |
 |     |     |      0v |      |   | 25 || 26 | 1 | IN   | CE1     | 11  | 7   |
 |   0 |  30 |   SDA.0 |   IN | 1 | 27 || 28 | 1 | IN   | SCL.0   | 31  | 1   |
 |   5 |  21 | GPIO.21 |   IN | 1 | 29 || 30 |   |      | 0v      |     |     |
 |   6 |  22 | GPIO.22 |   IN | 1 | 31 || 32 | 0 | IN   | GPIO.26 | 26  | 12  |
 |  13 |  23 | GPIO.23 |   IN | 0 | 33 || 34 |   |      | 0v      |     |     |
 |  19 |  24 | GPIO.24 | ALT0 | 0 | 35 || 36 | 0 | IN   | GPIO.27 | 27  | 16  |
 |  26 |  25 | GPIO.25 |   IN | 0 | 37 || 38 | 0 | ALT0 | GPIO.28 | 28  | 20  |
 |     |     |      0v |      |   | 39 || 40 | 0 | ALT0 | GPIO.29 | 29  | 21  |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
 +-----+-----+---------+------+---+---Pi 2---+---+------+---------+-----+-----+


I reset the flash serial, then start up the pi and try to connect
with cu;
Code:
cu -l /dev/ttyAMA0 -s 115200
I get "Connected"

with screen;
Code:
screen /dev/ttyAMA0
I get a blank screen
It's not responding to +++ or anything else I type


Questions:

* Should I solder on a few small wires to connect to pin 5 and 8 (I assume I have the right ones?) so i can reset the U38 without disconnecting/connecting the pi?
* Can I keep those wires connected through normal use? Or are they functioning as antennas throwing noise on the serial bus?

* Is there any command that i can execute to make sure the flash serial is in the right state now?
 
Me neither, the whole serial stuff is way too complicated. But I realize it's just the way it is and probably has advantages too.
Anyway I wanted to update the firmware, filters, everything in the

.
.
.

Questions:

* Should I solder on a few small wires to connect to pin 5 and 8 (I assume I have the right ones?) so i can reset the U38 without disconnecting/connecting the pi?
* Can I keep those wires connected through normal use? Or are they functioning as antennas throwing noise on the serial bus?

* Is there any command that i can execute to make sure the flash serial is in the right state now?

You should always be able to see the output from the uC, the serial TX line is connected directly to the uC, only the RX line goes though the FPGA....

If you can't see any output, you should check your serial communication, up to putting a scope on the TX line....

If not, you might have messed up the uC firmware and need to reprogram it. That require the tools from ST Microelectronics....
 
You should always be able to see the output from the uC, the serial TX line is connected directly to the uC, only the RX line goes though the FPGA....

If you can't see any output, you should check your serial communication, up to putting a scope on the TX line....

If not, you might have messed up the uC firmware and need to reprogram it. That require the tools from ST Microelectronics....


Thanks for your reply. The ST module is on its way to me