techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.7K
active users

#eeprom

2 posts2 participants0 posts today
5021tips<p>Data represented as, 5D21, is not same as, $5D21 nor 5D21h or whatever, as You study the nonsense in this picture, below👇!<br> <br>Notice there's usually, some weird something🤷, that is put somewhere🫣! Niiga, <a href="https://mastodon.social/tags/HapaUjanjaTu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HapaUjanjaTu</span></a>👇</p><p>www.5021.tips/ujanja/eepromwork</p><p>☝️<br>Don't feel shy, Suzan doesn't see You learn <a href="https://mastodon.social/tags/ujanja" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ujanja</span></a>, so <a href="https://mastodon.social/tags/diy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>diy</span></a> <a href="https://mastodon.social/tags/learneverything" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>learneverything</span></a> <a href="https://mastodon.social/tags/teachyourself" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>teachyourself</span></a> <a href="https://mastodon.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a> <a href="https://mastodon.social/tags/digitalelectronics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>digitalelectronics</span></a> <a href="https://mastodon.social/tags/techtipsandtricks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>techtipsandtricks</span></a> <a href="https://mastodon.social/tags/5021tips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>5021tips</span></a> <a href="https://mastodon.social/tags/techtips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>techtips</span></a> <a href="https://mastodon.social/tags/programmingtips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programmingtips</span></a> <a href="https://mastodon.social/tags/electronicstips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>electronicstips</span></a> <a href="https://mastodon.social/tags/ECUProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ECUProgramming</span></a> <a href="https://mastodon.social/tags/autoprogramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autoprogramming</span></a> <a href="https://mastodon.social/tags/ecurepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ecurepair</span></a> <a href="https://mastodon.social/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a></p>
IT News<p>Designing a CPU with only Memory Chips - Building a simple 8-bit computer is a great way to understand computing fundament... - <a href="https://hackaday.com/2025/07/11/designing-a-cpu-with-only-memory-chips/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2025/07/11/design</span><span class="invisible">ing-a-cpu-with-only-memory-chips/</span></a> <a href="https://schleuss.online/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>retrocomputing</span></a> #8-bitcomputers <a href="https://schleuss.online/tags/cpudesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cpudesign</span></a> #8-bitcpu <a href="https://schleuss.online/tags/eeprom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eeprom</span></a> <a href="https://schleuss.online/tags/eprom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eprom</span></a> <a href="https://schleuss.online/tags/cpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cpu</span></a></p>
Simple DIY Electronic Music Projects<p><strong>Diagnosing and attempting to fix a Yamaha DX100 – Part&nbsp;4</strong></p><p>I decided to have one more look at the data pins, largely inspired by this oscilloscope trace from part 3. I figured if the address and select pins were working (yellow, cyan and purple) what could I do to try to work out what is driving the data pins (darker blue) wobbly…</p><p><strong><em>And no, after all this time, it still isn’t working…</em></strong></p><p><em><strong>Warning!</strong>&nbsp;I am not an electronics person. I strongly recommend that you don’t base your own attempts at fixing a beloved vintage synth on anything I’ve said here. I was given this synth rather than it being sent it to a recycling centre so this is a low-risk learning activity for me. I am not responsible for any damage to expensive or irreplaceable electronic musical instruments! There are plenty of places to take something for a proper repair 🙂</em></p><p>If you are new to microcontrollers and electronics, see the&nbsp;<a href="https://diyelectromusic.wordpress.com/getting-started/" rel="nofollow noopener" target="_blank">Getting Started</a> pages.</p><p><strong>Pulling D0 to LOW</strong></p><p>My first thought was to see if I could use a weak pull-down resistor on one of the data pins (I was using D0) to see if that stabilises the signal and then see what the data trace looks like as I move around monitoring the various chip select/chip enable lines.</p><p>So with the replacement LCD attached from last time, I hooked up the following:</p><ul><li>Oscilloscope GND to GND.</li><li>10K between GND and D0.</li><li>Oscilloscope tracing LCD E pin.</li><li>Oscilloscope tracing D0.</li></ul><p>Unfortunately whilst it did stabilise the data signal a little, it still wasn’t really clear what might be causes the issue.</p><p>It did give one other clue though. When testing the RAM chips, I could see the data signal was actually quite clear when the RAM /CE was active (LOW).</p><p>So I abandoned that and tried something else…</p><p><strong>Closer look at the Data Lines</strong></p><p>So given the observation about the RAM chips, I decided to take a proper look at the data lines (well D0) when the various chip enable/chip select signals are active.</p><p>Handily, as the PCB is a single sided PCB with bridging wires, it was relatively straight forward to find wire links for both GND and D0, so I used these for the oscilloscope GND and blue trace (for D0).</p><p>The two probe GNDs are pushed under the link on the bottom left and D0 is the first of those block of links after the first three top right. This leaves a free-floating probe wire for me to use to prod the various select lines and see what D0 is doing at the time.</p><p>So, starting with the two RAM chips, /CE is on pin 20 and the trace I obtained looks like this:</p><p>On the face of thigs that still looks pretty chaotic, but actually the data signal (blue) is stable for the duration of the /CE signal being low, so that is probably actually ok.</p><p>A similar pattern was observed for the other RAM chip and the Yamaha OPP’s /CS signal.</p><p>The ADC is a little more complicated as can be seen in the extract from the schematic:</p><p>There are sort of three relevant pins here: 6 (START), 9 (OE) and 22 (ALE). IC17 is acting as an inverter so that when ADDAT and RD are both LOW OE is HIGH.</p><p>/ADCH and /ADDAT come from the address decoding logic:</p><p>But the upshot of all this is that when any of these signals is active, D0 looks pretty similar to the RAM trace.</p><p>So at this point, I’m feeling a lot more confident that the two RAM chips, ADC and OPP are probably not at fault.</p><p>The ROM is next on the hit list. Now again, looking at the schematic we can see that the ROM is enabled when A15 is HIGH (address $8000-$FFFF) and this happens thanks to another gate in IC17:</p><p>So the ROM is active when /CE is LOW, meaning A15 is HIGH. But when traced on the scope, D0 is all over the place (blue), especially when /CE is low (yellow).</p><p>It is curious to see that the ROM seems active for a lot longer than any of the other accesses I’ve examined. But I guess if the CPU is running from ROM it will be continually reading instructions whilst shuffling data between the other peripherals.</p><p>But regardless, I’m now very suspicious of this ROM.</p><p>The inverter is IC17 and also drives LCD E, which also doesn’t seem to work very well.</p><p>So even though I tried a new ROM and nothing seemed to change, I replaced the ROM again and actually took a proper look at the signals on the bus.</p><p>That seems to speak for itself. Yes, /CE is still LOW for larger periods of time, but those data signals are massively improved.</p><p>Spoilers: it turns out this wasn’t what I thought was happening, but I’ll get back to that in a mo…</p><p>So this is now what the LCD E triggered trace looks like.</p><p>That looks like a massive improvement! So why isn’t this working now then?</p><p><strong>Not so fast… I messed up the ROM</strong></p><p>So now I have half the display showing blocks, a flashing power LED and still no other signs of life.</p><p>A flashing LED apparently indicates that the backup battery is low. This in and of itself is probably progress as the LED is connected to an IO pin of the CPU, so this seems to indicate the CPU is actually running code as it is making the LED flash. So why isn’t it booting?</p><p>Measuring the voltage from the test pins, it is reading 2.7V, when I think it is meant to be 3V.</p><p>I’ve not managed to get a replacement display running by plugging wires into the socket instead of the original LCD. But scanning all the data lines of the display when it is enabled, seems to show they are all working ok.</p><p>So the question is now:</p><ul><li>Has the CPU got stuck in a loop with the flashing LED? It’s certainly possible.</li><li>Or is the display not functioning properly?</li></ul><p>Well it turns out there is another condition where the LED flashes.</p><p>As I was poking around I noticed there were some fairly regular repeated patterns on the address bus, and it seemed like the RAM wasn’t being accessed anymore.</p><p>It turns out another condition where the LED flashes is if there is no code in the ROM…</p><p>Yes, I’d put in a blank ROM by mistake. Sigh.</p><p>Unfortunately when I program the ROM (and verify it) and plug that back in, the black squares on the display have now gone, but the data bus is messed up again.</p><p>I guess that probably means it isn’t the ROM that is at fault.</p><p>But that probably points to something that isn’t enabled properly until some code is running on the CPU from the ROM.</p><p>Mind you, I don’t know what allowed me to get the LCD trace if there was no code in the ROM… but I guess the CPU could have been doing anything at that point.</p><p><strong>So About that ROM</strong></p><p>At this point I wondered what it all looks like if I unplug the display. And yes, sure enough, the signal is a lot cleaner again.</p><p>So, does unplugging the display fix things because the display is causing the issue? Or does not having a display change what code is running so the problematic peripheral or mode is missed out (like it was when the ROM didn’t even have code)? It’s a little hard to say.</p><p>At this point I thought I may as well go back to the original ROM. After all it is a lot nicer to have one stamped Yamaha than one stamped 29C256. But then something else interesting happened. Here are two traces still without the LCD connected:</p><p>The one on the left is the replacement, reprogrammed 29C256 flash EEPROM and the one on the right is the original Yamaha mask ROM. In both cases the ROM is enabled when the yellow trace is LOW and the blue trace is D0. As we can see, there is still something not right about the original ROM…</p><p><strong>LCD Enable and Data</strong></p><p>Assuming that the ROM is now fixed, there is something odd about the LCD. I’m not convinced my Heath-Robinson mashup of a breadboard and 1602 LCD is giving me any results I can rely on, but I did one last experiment.</p><p>As I wasn’t sure if removing the LCD prevented the actual issue or just stopped the code from enabling a different problematic peripheral, I wondered what would happen if an LCD was connected, but I just removed its ability to drive D0 whilst I was monitoring it.</p><p>Here is the result. On the left, with D0 connected to the LCD, on the right with D0 unconnected.</p><p>It does seem to be better when D0 can’t be driven from the LCD (LCD enable, and other data lines are all functioning normally). There is a single access on power up, then another one maybe a few 100mS later, and then a burst of activity, and then nothing at all.</p><p>I wondered if maybe the logic controlling the E (enable) line for the LCD might not be working properly, so I went back to the original LCD and took at a look at LCDE.</p><p>Homing in on IC17, I should be able to see a LOW signal on pins 5 and 6 generating the HIGH E (enable) signal for the LCD, and yes, that appears to be working fine as far as I can see. This is a sample of the “busy” set of accesses just prior to everything going silent.</p><p>So going back to looking at the data lines (D0) whilst this is going on…</p><p>Sp there doesn’t seem to be an issue with the data lines whilst the LCD is being poked (left). But when the accesses to the LCD appear to stop (right), then the data line seems to be all over the place once again – it gets worse after this initial activity.</p><p>But there does seem to be some kind of pattern here, which implies to me that everything is stuck in a loop somehow. Here is the zoomed-out version of the last trace, showing the last of the LCD Enable lines and the following patterns in data (zoomed back in on the second trace).</p><p><strong>Conclusions for now…</strong></p><p>So where does this leave me? To be honest I’m not sure. Maybe back where I started.</p><p>It would appear that with the display out of the loop there was something screwy about the original Yamaha ROM. But I’m not convinced that the display isn’t causing issues too.</p><p>I’d like to take the display PCB apart and check connections and clean it, but it has one of those flexible connectors between the controller PCB and the LCD display, so I’m not sure I want to mess with that right now.</p><p>If I can find a robust way of plugging in an alternative display I might give that another go.</p><p>Either that, or I might return to the power circuit as that 5V line does seem pretty noisy to me.</p><p>When I decide on next steps, I’ll come back and add to this post again.</p><p>Kevin</p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://diyelectromusic.com/tag/dx100/" target="_blank">#dx100</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://diyelectromusic.com/tag/eeprom/" target="_blank">#eeprom</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://diyelectromusic.com/tag/lcd1602/" target="_blank">#lcd1602</a></p>
5021tips<p>Like a car involves in <a href="https://mastodon.social/tags/roadaccident" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>roadaccident</span></a>, just copy data from clean car, then paste in the <a href="https://mastodon.social/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> of the <a href="https://mastodon.social/tags/accidentcar" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>accidentcar</span></a>, <a href="https://mastodon.social/tags/hakunamatata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hakunamatata</span></a>🤷! </p><p>Just make sure do proper <a href="https://mastodon.social/tags/accidentrepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>accidentrepair</span></a>, even if not <a href="https://mastodon.social/tags/newcar" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>newcar</span></a> to steal data from, <a href="https://mastodon.social/tags/HapaUjanjaTu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HapaUjanjaTu</span></a> 👇</p><p>www.5021.tips/ujanja/airbag</p><p>👆<br>Infact there's some nonsense to sense the <a href="https://mastodon.social/tags/airbag" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>airbag</span></a> <a href="https://mastodon.social/tags/SRS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SRS</span></a> even if no <a href="https://mastodon.social/tags/caraccident" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caraccident</span></a> happened but the car is showing <a href="https://mastodon.social/tags/DashboardLights" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DashboardLights</span></a> ujinga, seen🤔?</p><p><a href="https://mastodon.social/tags/autorepairtips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autorepairtips</span></a> <a href="https://mastodon.social/tags/5021tips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>5021tips</span></a> <a href="https://mastodon.social/tags/autotips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autotips</span></a> <a href="https://mastodon.social/tags/cartips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cartips</span></a> <a href="https://mastodon.social/tags/diy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>diy</span></a> <a href="https://mastodon.social/tags/autobodyrepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autobodyrepair</span></a> <a href="https://mastodon.social/tags/carbodyrepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>carbodyrepair</span></a> <a href="https://mastodon.social/tags/Autorepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Autorepair</span></a></p>
@Rp12Biker :verified:<p>A quick question for those with experience: Can someone tell me which file in <a href="https://oldbytes.space/tags/RomWBW" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RomWBW</span></a> controls which ROMs are subsequently written to the <a href="https://oldbytes.space/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a>? I mean the ones listed with "L." I'd like to remove some operating systems and store compilers instead.<br><a href="https://oldbytes.space/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RetroComputing</span></a> <a href="https://oldbytes.space/tags/ZilogZ180" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZilogZ180</span></a></p>
5021tips<p>Usikwame na kazi ya <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a> kwasababu umekosa hiyo <a href="https://mastodon.social/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> unadhani ndo sahihi tu, yet kuna <a href="https://mastodon.social/tags/ujanja" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ujanja</span></a> kutambua jinsi zinaingiliana, yaani kufanana matumizi, <a href="https://mastodon.social/tags/HapaUjanjaTu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HapaUjanjaTu</span></a> 👇</p><p>www.5021.tips/ujanja/datasheets</p><p>👆<br>Maandishi yakiwa katika lugha ya kigeni, unatafsiri tu ili uelewe ujinga🤷‍♂️! <br><a href="https://mastodon.social/tags/programmingtips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programmingtips</span></a> <a href="https://mastodon.social/tags/5021tips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>5021tips</span></a> <a href="https://mastodon.social/tags/codingtips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>codingtips</span></a> <a href="https://mastodon.social/tags/ecu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ecu</span></a> <a href="https://mastodon.social/tags/digitalelectronics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>digitalelectronics</span></a> <a href="https://mastodon.social/tags/electroniccomponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>electroniccomponents</span></a> <a href="https://mastodon.social/tags/diy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>diy</span></a> <a href="https://mastodon.social/tags/ecurepairs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ecurepairs</span></a> <a href="https://mastodon.social/tags/autoelectronics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autoelectronics</span></a> <a href="https://mastodon.social/tags/ECUProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ECUProgramming</span></a> <a href="https://mastodon.social/tags/carkeyprogramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>carkeyprogramming</span></a> <a href="https://mastodon.social/tags/EEPROMwork" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROMwork</span></a> <a href="https://mastodon.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a></p>
Simon D.<p>Hier soir à <span class="h-card" translate="no"><a href="https://mamot.fr/@GEBULL" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GEBULL</span></a></span> : une séance presque ordinaire d'un groupe d'utilisateurs de <a href="https://piaille.fr/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> en province…</p><p>On a dessoudé un BIOS de laptop HS donné par l'hôpital de la ville d'à côté, reprogrammé cette EEPROM, ressoudé la chose et redémarré la machine ! Pas si compliquée cette réparation 🙂 </p><p>Pour remettre un système d'exploitation sur la machine on a utilisé un nouveau gadget : un stockage NVME dans un adaptateur USB.<br>En choisissant le bon port USB, la machine démarre plus vite en live que depuis son SSD SATA interne une fois l'installation terminée !! (en un temps record)</p><p>Les temps changent…</p><p><a href="https://piaille.fr/tags/LUG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LUG</span></a> <a href="https://piaille.fr/tags/Gebull" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gebull</span></a> <a href="https://piaille.fr/tags/BIOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BIOS</span></a> <a href="https://piaille.fr/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> <a href="https://piaille.fr/tags/NVME" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NVME</span></a> <a href="https://piaille.fr/tags/SSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSD</span></a> <a href="https://piaille.fr/tags/SATA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SATA</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.online/@oldperl" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>oldperl</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nixCraft</span></a></span> propably because their tech is so old that an <a href="https://infosec.space/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> may get wiped by interference?</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nixCraft</span></a></span> <a href="https://infosec.space/tags/EPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EPROM</span></a>, not <a href="https://infosec.space/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> as mamy have corrected me wisely.</p>
Ortwin Pinke<p>Hab ich jemand in meiner Bubble, die/der mir sagen kann, ob und wie ich an originale <a href="https://mastodon.online/tags/EEprom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEprom</span></a> Dateien für <a href="https://mastodon.online/tags/Motorsteuerger%C3%A4t" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Motorsteuergerät</span></a> und <a href="https://mastodon.online/tags/Kombiinstrument" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kombiinstrument</span></a> von meinem <a href="https://mastodon.online/tags/Audi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Audi</span></a> A4 B6 2.5 tdi komme?</p><p><a href="https://mastodon.online/tags/VAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VAG</span></a> <a href="https://mastodon.online/tags/Auto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Auto</span></a> <span class="h-card" translate="no"><a href="https://a.gup.pe/u/reparatur" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>reparatur</span></a></span></p>
JP Stringham 🇨🇦<p>Insomnia and other health bugs caused me to stay up late tonight and do some much overdue bug fixing on my <a href="https://mastodon.gamedev.place/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> <br><a href="https://mastodon.gamedev.place/tags/RasperryPiPico" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RasperryPiPico</span></a> <a href="https://mastodon.gamedev.place/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> emulator</p><p>Notably it runs by default at the new standard 200MHz, has a `logging` feature via `probe-rs` and `defmt`, and is a bit smarter about not letting you blow up the memory beyond the number of bits allocated to the address bus.</p><p><a href="https://github.com/super-saturn/pico-eeprom-emu" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/super-saturn/pico-e</span><span class="invisible">eprom-emu</span></a></p>
Ortwin Pinke<p><a href="https://mastodon.online/tags/Kombiinstrument" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kombiinstrument</span></a> zerlegt, um das <a href="https://mastodon.online/tags/EEProm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEProm</span></a> direkt zu programmieren.</p><p><a href="https://mastodon.online/tags/DIY" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DIY</span></a> <a href="https://mastodon.online/tags/Auto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Auto</span></a> <a href="https://mastodon.online/tags/autorepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autorepair</span></a></p>
Simple DIY Electronic Music Projects<p><strong>Diagnosing and attempting to fix a Yamaha DX100 – Part&nbsp;3</strong></p><p>At the end of <a href="https://diyelectromusic.wordpress.com/2023/12/31/diagnosing-and-attempting-to-fix-a-yamaha-dx100-part-1/" rel="nofollow noopener" target="_blank">part 1</a>, I’ve established that the basics all seem ok (PCB, interconnections, power) and that basic digital logic stuff is happening.</p><p>In <a href="https://diyelectromusic.com/2024/03/18/diagnosing-and-attempting-to-fix-a-yamaha-dx100-part-2/" rel="nofollow noopener" target="_blank">part&nbsp;2</a> I checked the ROM, reflowed a number of the solder joints, and started to look at the connectors between the main PCB and the LCD, but still with no luck.</p><p>Now I’m finally getting around to looking properly at those data signals to see what my next steps might be.</p><p><strong><em>Oh and nope, still not fixed. Sorry.</em></strong></p><p><em><strong>Warning!</strong>&nbsp;I am not an electronics person. I strongly recommend that you don’t base your own attempts at fixing a beloved vintage synth on anything I’ve said here. I was given this synth rather than it being sent it to a recycling centre so this is a low-risk learning activity for me. I am not responsible for any damage to expensive or irreplaceable electronic musical instruments! There are plenty of places to take something for a proper repair 🙂</em></p><p>If you are new to microcontrollers and electronics, see the&nbsp;<a href="https://diyelectromusic.wordpress.com/getting-started/" rel="nofollow noopener" target="_blank">Getting Started</a> pages.</p><p><strong>Replacing the LCD – Continued</strong></p><p>In <a href="https://diyelectromusic.com/2024/03/18/diagnosing-and-attempting-to-fix-a-yamaha-dx100-part-2/" rel="nofollow noopener" target="_blank">part&nbsp;2</a> I thought that it would be worth seeing if I could replace the LCD with an alternative, seeing as it appeared to be just a common HD44780 based display, but the connector used was giving me trouble.</p><p>In the end I just took the plastic shrouds off some Dupont style jumper wires and poked them directly into the connector on the PCB.</p><p>This finally gives me a way into some of the control signals and data lines on the main bus. First things first, I connected up a replacement display. Usefully the pinout of this connector matches exactly the pinout of a LCD1602 display.</p><p>The only additional connections required are an extra +5V/GND for the backlight (marked as “K” and “A” on my display). All the other connections match as shown by the schematic.</p><p>Hooking up an oscilloscope as follows:</p><ul><li>Yellow = E = LCD Enable pin (decoded from A10-15=0; A13=1)</li><li>Blue = R/W (low = write)</li><li>Purple = RS = register select (maps onto A0 on the address bus)</li><li>Darker blue = D0</li></ul><p>and triggering off the enable pin gives me the following trace:</p><p>The darker blue line is D0 and as can be seen – it is basically all over the place. It definitely looks like something is breaking the data lines, so the question now is what. I also checked D1-D7 and they all look pretty similar.</p><p>From my previous experiments the fact that I can read the ROM successfully, and now have replaced the LCD implies one of the other devices. So I think that leaves the following options:</p><ul><li>The CPU itself</li><li>RAM</li><li>A/D</li><li>OPP – the Yamaha FM tone generator itself</li></ul><p>But as all these are soldered down, it makes the next step a little tricky.</p><p>I’ve triggered the scope of the various CS/OE lines for the RAM, ADC and OPP and checked the local equivalent of D0 and the pattern seems the same everywhere.</p><p>Interestingly I don’t ever see a CS/OE line for the ADC or OPP – but then if it is failing to boot then the CPU will never get around to trying to access either of those I’d imagine.</p><p>By the way, on startup, there are there points where the LCD “E”nable pin is accessed. Two single instances, and then a large block as shown below.</p><p><strong>Removing the ROM</strong></p><p>Just out of interest I thought it was worth seeing what the signals looked like with the ROM removed (seeing as it is socketed and easy to remove). I triggered of the CE for one of the RAM chips and checked the signals.</p><p>The RAM isn’t accessed as much, but then with no ROM I don’t know what the CPU would be doing anyway…</p><p>But when it is, D0 (dark blue again in the trace below) looks a lot more like a sensible digital signal to me.</p><p>So now I’m thinking I really ought to eliminate the idea of a problem ROM chip before desoldering any of the RAM to test that…</p><p>Aside: at one point, when just monitoring the data signal, I got a much cleaner signal, but very definitely appearing to show three distinct states, which again reinforces the fact that something, somewhere is trashing over the data lines…</p><p><strong>Replacing the ROM</strong></p><p>As discussed <a href="https://diyelectromusic.com/2024/03/18/diagnosing-and-attempting-to-fix-a-yamaha-dx100-part-2/" rel="nofollow noopener" target="_blank">last time</a>, the DX100 uses a 27C256 style ROM which isn’t quite the same pinout as the more common 28C256 EEPROM that can be found relatively easily these days. However there is also a 29C256 which does have essentially the same pinout as the 27C256.</p><p>I happen to have some, but I don’t know if they are any good! I also have my <a href="https://diyelectromusic.com/2024/01/28/arduino-eeprom-reader-pcb-design/" rel="nofollow noopener" target="_blank">Arduino EEPROM Reader</a> but I’ve never tried to write with it and certainly not tried to do anything with a 29C256.</p><p>I took the plunge and bought myself an XGecu T48. Downloading and installing the software was a bit of a leap of (hopefully not misplaced) faith as some of download links went off to a media file download site which was constantly playing “download button roulette” but with a bit of care I was able to find the .rar file for the installer.</p><p>I programed an Atmel 29C256 with the binary image I found, but unfortunately it made no difference – it was still completely dead.</p><p>Just out of interest I tried to read the Yamaha ROM using the XGecu, but I couldn’t find a manufacturers 27C256 setting that worked. I kept getting a “pin 1 error” whenever I tried to read it. Funny that it worked ok with my Arduino reader though…</p><p>I tried it with the replacement LED but then plugged the real one back in – but still nothing unfortunately.</p><p><strong>One Last Probe…</strong></p><p>I thought I’d have one last poke about for continuity with a multimeter. I checked the ribbons that connected different parts of the PCB together. I checked a whole range of GND connections (the additional, unpopulated header in the top right (from the underside) for E, +5, -3 was really useful there.</p><p>One oddity I did find, is that I couldn’t find continuity between the VCC pin on one of the RAM chips – IC13. I tried tracing it through to see where things broke, and it got a bit confusing linking into some transistors and eventually the on-PCB battery.</p><p>It turns out, looking at the schematic, that this is the RAM battery-backup store:</p><p>So I guess that means that RAM1 is for voice data and RAM2 is working RAM for the CPU. Curiously, /CE2 for RAM1 is connected into the battery or reset (or both) circuit somehow too, whereas for RAM2 it is tied to GND. I must confess I’m not quite sure what is going on there.</p><p>Ah, turns out I should just RTF(service)M. Wiring /CE2 into the reset circuit like this ensures that RAM1 can’t be selected during the reset period and so inadvertently get written to, to override the stored contents. RAM1 is thus disabled until the reset is complete.</p><p>/CE1 for both chips is connected to IC14 which does the address decoding (see <a href="https://diyelectromusic.com/2023/12/31/diagnosing-and-attempting-to-fix-a-yamaha-dx100-part-1/" rel="nofollow noopener" target="_blank">Part&nbsp;1</a>).</p><p>Anyway the upshot of all this is that I powered the thing back up to check the VCC signals and yes, both pin 24s on both RAM chips are reading 4.99V and the battery itself is reading ~2.5V.</p><p><strong>Further Thoughts</strong></p><p>I feel like I’ve made a little more progress in appearing to have eliminated the LCD and probably the ROM as a source of the issue.</p><p>But I think I’m essentially out of options now. Assuming (and this might be a big assumption of course) everything I’ve said so far is true, I think this only leaves one of the soldered chips as possibly causing an issue. For that, I have the choice of:</p><ul><li>The main application processor itself.</li><li>The two RAM chips.</li><li>The Yamaha YM sound processor.</li></ul><p>I think at this point ideally I get some traces from a working synth to see how it compares before desoldering chips. But that probably isn’t going to be possible. Another option might be to look out for a “spares or repairs” DX100 so I can do some mixing and matching.</p><p>It might be worth replacing the ROM with hard-wired pull-ups/downs on the data lines to force the code for a NOP onto the bus as the CPU starts up. That at least might show that the CPU itself is still ok. But really, if something is messing with the data lines, the only option really is to remove some of the chips until they start looking sensible again.</p><p>But I’m not sure I’m confident enough in my diagnosis so far to start getting destructive so I suspect this might be the end of my journey attempting this myself and I might have to find someone who knows what they are doing.</p><p>Of course, if you spot any other options do feel free to let me know.</p><p>Kevin</p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://diyelectromusic.com/tag/dx100/" target="_blank">#dx100</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://diyelectromusic.com/tag/eeprom/" target="_blank">#eeprom</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://diyelectromusic.com/tag/lcd1602/" target="_blank">#lcd1602</a></p>
Jan Beta<p>New video! I'm taking a look inside my very inexpensive EPROM eraser and I'm making some modifications.</p><p>YouTube: <a href="https://youtu.be/BN1Y0NIqM60" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/BN1Y0NIqM60</span><span class="invisible"></span></a><br>PeerTube: <a href="https://makertube.net/w/eiXyGku3QcaifmyeUyAysg" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">makertube.net/w/eiXyGku3Qcaifm</span><span class="invisible">yeUyAysg</span></a></p><p><a href="https://chaos.social/tags/EPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EPROM</span></a> <a href="https://chaos.social/tags/EPROMeraser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EPROMeraser</span></a> <a href="https://chaos.social/tags/Mods" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mods</span></a> <a href="https://chaos.social/tags/Repair" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Repair</span></a> <a href="https://chaos.social/tags/Improvement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Improvement</span></a> <a href="https://chaos.social/tags/UVlight" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UVlight</span></a> <a href="https://chaos.social/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> <a href="https://chaos.social/tags/UVEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UVEPROM</span></a></p>
Dirk Wouters<p>EPROM emulieren statt brennen </p><p>Vor kurzem bin ich auf ein interessantes Projekt gestoßen. Es ging um einen sogenannten EPROM-Emulator. Also ein Gerät, das u.a. über USB über einen Adapter vorgibt, ein EPROM zu sein.</p><p><a href="https://mastodon.social/tags/27C512" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>27C512</span></a> <a href="https://mastodon.social/tags/27C64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>27C64</span></a> <a href="https://mastodon.social/tags/adapter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>adapter</span></a> <a href="https://mastodon.social/tags/Arduino" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Arduino</span></a> <a href="https://mastodon.social/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> <a href="https://mastodon.social/tags/Emulator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Emulator</span></a> <a href="https://mastodon.social/tags/EPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EPROM</span></a> <a href="https://mastodon.social/tags/Flash" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Flash</span></a> <a href="https://mastodon.social/tags/Projekt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Projekt</span></a> <a href="https://mastodon.social/tags/Standalone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Standalone</span></a></p><p><a href="https://dirkwouters.de/eprom-emulieren-statt-brennen/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dirkwouters.de/eprom-emulieren</span><span class="invisible">-statt-brennen/</span></a></p>
Dirk Wouters<p>Nachbau des DELA EPROMMER II für den Commodore C64 </p><p>Diesmal habe ich meinen alten DELA EPROMMER II wieder aufgebaut. Das war damals mein zweites EPROM-Programmiergerät, mit dem ich eine Menge EPROMs geschrieben habe. Und ich fand, dass sich ein Nachbau dieser Erweiterung lohnt, zumal immer noch viele die EPROMs direkt mit dem C6…</p><p><a href="https://mastodon.social/tags/c64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>c64</span></a> <a href="https://mastodon.social/tags/commodore" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>commodore</span></a> <a href="https://mastodon.social/tags/DELA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DELA</span></a> <a href="https://mastodon.social/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> <a href="https://mastodon.social/tags/EPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EPROM</span></a> <a href="https://mastodon.social/tags/Hidden" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hidden</span></a> <a href="https://mastodon.social/tags/Menu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Menu</span></a> <a href="https://mastodon.social/tags/Programmer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programmer</span></a> <a href="https://mastodon.social/tags/Replica" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Replica</span></a> <a href="https://mastodon.social/tags/Service" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Service</span></a> <a href="https://mastodon.social/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Software</span></a> <a href="https://mastodon.social/tags/Test" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Test</span></a> <a href="https://mastodon.social/tags/Userport" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Userport</span></a></p><p><a href="https://dirkwouters.de/dela-eprommer-ii/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dirkwouters.de/dela-eprommer-i</span><span class="invisible">i/</span></a></p>
Pyrzout :vm:<p>EPROM-based Enigma Machine <a href="https://hackaday.com/2025/03/12/eprom-based-enigma-machine/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2025/03/12/eprom-</span><span class="invisible">based-enigma-machine/</span></a> <a href="https://social.skynetcloud.site/tags/computerhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>computerhacks</span></a> <a href="https://social.skynetcloud.site/tags/classichacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>classichacks</span></a> <a href="https://social.skynetcloud.site/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> <a href="https://social.skynetcloud.site/tags/colossus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>colossus</span></a> <a href="https://social.skynetcloud.site/tags/Cipher" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cipher</span></a> <a href="https://social.skynetcloud.site/tags/eeprom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eeprom</span></a> <a href="https://social.skynetcloud.site/tags/enigma" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>enigma</span></a> <a href="https://social.skynetcloud.site/tags/bombe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bombe</span></a> <a href="https://social.skynetcloud.site/tags/WW2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WW2</span></a></p>
IT News<p>EPROM-based Enigma Machine - The Enigma machine is perhaps one of the most legendary devices to come out of Wor... - <a href="https://hackaday.com/2025/03/12/eprom-based-enigma-machine/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2025/03/12/eprom-</span><span class="invisible">based-enigma-machine/</span></a> <a href="https://schleuss.online/tags/computerhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>computerhacks</span></a> <a href="https://schleuss.online/tags/classichacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>classichacks</span></a> <a href="https://schleuss.online/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> <a href="https://schleuss.online/tags/colossus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>colossus</span></a> <a href="https://schleuss.online/tags/cipher" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cipher</span></a> <a href="https://schleuss.online/tags/eeprom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eeprom</span></a> <a href="https://schleuss.online/tags/enigma" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>enigma</span></a> <a href="https://schleuss.online/tags/bombe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bombe</span></a> <a href="https://schleuss.online/tags/ww2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ww2</span></a></p>
5021tips<p>Like this EDC16U31, as instructions will show, depending on <a href="https://mastodon.social/tags/ECU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ECU</span></a>, or carbrand, some <a href="https://mastodon.social/tags/immoff" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>immoff</span></a> data is written to <a href="https://mastodon.social/tags/flashmemory" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>flashmemory</span></a> those bigger <a href="https://mastodon.social/tags/EEPROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EEPROM</span></a> 👇</p><p>www.5021.tips/ujanja/immoff</p><p>☝️👆<br>This rubbish includes the already <a href="https://mastodon.social/tags/hacked" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hacked</span></a> data, just to copy &amp; paste, otherwise we give you the <a href="https://mastodon.social/tags/immooff" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>immooff</span></a> tools to obviously <a href="https://mastodon.social/tags/doityourself" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>doityourself</span></a>, <a href="https://mastodon.social/tags/HapaUjanjaTu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HapaUjanjaTu</span></a> 🤷!</p><p><a href="https://mastodon.social/tags/carkeyprogramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>carkeyprogramming</span></a> <a href="https://mastodon.social/tags/ecurepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ecurepair</span></a> <a href="https://mastodon.social/tags/lostkeys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lostkeys</span></a> <a href="https://mastodon.social/tags/sparekeys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sparekeys</span></a> <a href="https://mastodon.social/tags/usedparts" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>usedparts</span></a> <a href="https://mastodon.social/tags/5021tips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>5021tips</span></a> <a href="https://mastodon.social/tags/autorepairtips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autorepairtips</span></a> <a href="https://mastodon.social/tags/autotips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autotips</span></a> <a href="https://mastodon.social/tags/automotivetechnician" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>automotivetechnician</span></a> <a href="https://mastodon.social/tags/autoelectrical" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autoelectrical</span></a> <a href="https://mastodon.social/tags/learneverything" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>learneverything</span></a><br><a href="https://mastodon.social/tags/Keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Keys</span></a></p>
Daniele Verducci 🧉Progress!<br>I've got a basic <a class="hashtag" href="https://social.ichibi.eu/tag/emulator" rel="nofollow noopener" target="_blank">#emulator</a> working for my Pat80 <a class="hashtag" href="https://social.ichibi.eu/tag/homebrew" rel="nofollow noopener" target="_blank">#homebrew</a> <a class="hashtag" href="https://social.ichibi.eu/tag/zilog" rel="nofollow noopener" target="_blank">#zilog</a> <a class="hashtag" href="https://social.ichibi.eu/tag/z80" rel="nofollow noopener" target="_blank">#z80</a> <a class="hashtag" href="https://social.ichibi.eu/tag/computer" rel="nofollow noopener" target="_blank">#computer</a> !<br>This should ease the os development as I can test the changes without having to: remove the <a class="hashtag" href="https://social.ichibi.eu/tag/eeprom" rel="nofollow noopener" target="_blank">#eeprom</a> from the computer (without bending the pins), program it in the <a class="hashtag" href="https://social.ichibi.eu/tag/tl866" rel="nofollow noopener" target="_blank">#TL866</a> programmer, place it again on the computer (aligning pins correctly), test, notice it's not working and have no idea why, start debugging with the logic probe on the <a class="hashtag" href="https://social.ichibi.eu/tag/address" rel="nofollow noopener" target="_blank">#address</a> and <a class="hashtag" href="https://social.ichibi.eu/tag/data" rel="nofollow noopener" target="_blank">#data</a> pins, swear in arcane languages... 😅<br><br><a href="https://git.ichibi.eu/penguin86/pato-z80-home-computer/commits/branch/c-emulator" rel="nofollow noopener" target="_blank">https://git.ichibi.eu/penguin86/pato-z80-home-computer/commits/branch/c-emulator</a>