Build Problems

[circuitcreature]

I have the synth all built and as mentioned in another issue I used the MXD1210CPA+ instead of the DS1210. I am able to flash the Atmega using an Arduino and set the fuses to E:FF, H:DF, L:E0, or E:FF, H:D9, L:E0.

The issue is when I power it up all the LEDs light up and it doesn't produce any sounds. I have also tried the init within the settings using buttons 8,9,11, and 14, but nothing appears to happen after pressing 11 and 14. Pressing 8 then 9 does cause the LEDs to brighten and a sequence starts on the screen for about a second.

I can however test the chip type correctly with a returned value of 12.

Once after powering on it did start making sounds, but I haven't been able to reproduce that.

Any troubleshooting ideas?

[Jaffe-]

It is normal for it to behave strangely at first bootup, because the RAM just contains junk. The RAM is initialized properly when going to the settings mode and using 8, 9 and 11. Next boot after this it should work more as expected.
This is one of the less finished parts of the SW, it should really just auto detect corrupt memory and initialize automatically.

If it it does not help to press, 8, 9 and 11 (when in settings mode) and power cycling, then I suspect that something might be wrong with the SRAM memories or surrounding circuitry. I would check the RAM chips (IC10, IC11) and the address latches (IC7, IC8, IC9) and the address decoder IC5 for any soldering issues. Same for the battery backup circuitry (DS1210). And of course, just to double check, you do have a battery installed?

[circuitcreature]

I put the battery in and tried the init and power cycling and everything is working. I still have the issue with the LEDs always being lit, but I can live with that. I'll have to check my BOM, but I ended up using a different LED from the committed BOM, so there might be something in there.
Great project thank you.

[Jaffe-]

That sounds strange. Are they always on, but brighter when actually supposed to be lit? Otherwise it sounds like it would be hard to use ...

I pushed some new code now, it checks whether the RAM has become corrupted. If it is, 'cr' will flash in the display at boot and the RAM will be properly initialized (same as manually performing it in the settings menu).

[circuitcreature]

Correct, they are alwasy on and sometimes get brighter, this is only noticeable when the init runs after pressing 8 => 9, but other than that there is no indication when on a specific mode. I used mouser #696-SSL-LX3054IID, but they look to be mostly the same as the OG BOM.

Thank you for the code update. I'll give that a try next time I get the flasher setup.

[Jaffe-]

Sounds like something might be wrong on the panel board. I would check the row and column latches there. Do all the LEDs do this, or just some of them? What about the 7 segment display?
The LEDs are very similar to the ones in the BOM, so I don't think they are the issue here.

[circuitcreature]

Double checked everything and it looks fine. It only happens to the LEDs, the display displays 00 when nothing has been selected.
As for the update, I get a battery warning and cr on every boot and it wipes all previous settings, like midi channels.

[beau-seidon]

There are a few items in the committed BOM which are obsolete. I had to select suitable replacements. Also @Jaffe- did mention, in a reply to one of my Issues, that the BOM is not as up-to-date as the schematic. One example I found is that the part number listed in the BOM for the bus resistor on the top board is for a 4.7k instead of the 15k from the schematic.

When I built mine, I opened the .sch file in Eagle (free version) and exported a new parts list, then carefully compared the committed BOM to the new list. I used both as a reference to build my own cart on Mouser, defaulting to the schematic when I found conflicts.

I have attached an export of my Mouser cart with all the parts I used in my build, for your reference.
Mine is working great without any electronics issues.

exported_mouser_cart_(nesizer_only).xls

[circuitcreature]

Thank you @beau-seidon I'll compare yours to mine and update as needed. I'll report back if I order any new parts.
edit:
Ordered more parts, the resistor array, clock, and diodes.

[Jaffe-]

Double checked everything and it looks fine. It only happens to the LEDs, the display displays 00 when nothing has been selected. As for the update, I get a battery warning and cr on every boot and it wipes all previous settings, like midi channels.

Does not sound good! I think the cr error should only occur once the first time (and yes, the settings will be erased too. I should have warned about this...) After it has written the expected signature to RAM, it should work fine after the next boot. If it does not, it means that the battery backup is not working and has corrupted the RAM.

I will check whether the battery fault is now always showing with a fresh battery also. It might need some more work to be reliable.

[beau-seidon]

Thank you @beau-seidon I'll compare yours to mine and update as needed. I'll report back if I order any new parts.
edit:
Ordered more parts, the resistor array, clock, and diodes.

If you are talking about the switching diodes, you can use the ones in the BOM (1N4148 are equivalent to the 1N914 diodes that I bought, and there will be no functional difference).

The clock will make an enormous difference if you got the wrong one. Particularly if it oscillates at a different frequency than the design. If the freq. is wrong though I wouldn't expect it to boot at all.

Not sure what effect the resistor array difference would make, other than potentially passing too much current through the buttons if several are pressed at once? Full disclosure: I bought the wrong one too and almost said screw it I'll install it anyway lol. In the end I decided not to and got a 15k replacement before turning it on.

I'm not implying anything here, but triple check that all your IC's are oriented correctly. I booted it up the first time with my 2A03 in backwards because I am stupid, but it didn't hurt anything as far as I can tell. It still goes beep boop.

[circuitcreature]

ICs look good. I also picked up more latches, to test out. I might have messed something up on first boot, i had the pins off by one with the mainboard and panel. As far for the cystal it is 20mhz, worse case I'll build another one.

[Jaffe-]

@circuitcreature Let me know what you find out. If you know some programming, you could try to change the update speed of the LEDs in the code. See src/task/task.c line 84 which defines the update rate for the LED refresh. If you increase this period, it should update slower and perhaps make it easier to debug. You could also try and just locally mod the code to add a mechanism to single-step the LED rows and columns from one of the buttons.

Regarding the battery level and corrupt RAM warnings, it just dawned on me that the board I currently have fully assembled is an older v0.5 board with some mods, so the battery related stuff is not the same as in the latest design. I should build a new main board based off the latest version before attempting to write any clever code, I think. I will revert the change related to battery low and memory corruption errors until I can test it on a new board.

Just out of curiosity, what do you see when you press the battery level indicator in settings? (press and hold second rightmost button on first row)
Same for you as well, @beau-seidon, what does the battery level indicator show in your case?

[circuitcreature]

@Jaffe- I've been digging around in the code, it's been a while with C. I'll look at the refresh rate.
As for the battery it displays 45. I'm pretty sure this one is new, I can dig around and see if I have another to test.

[beau-seidon]

Just out of curiosity, what do you see when you press the battery level indicator in settings? (press and hold second rightmost button on first row) Same for you as well, @beau-seidon, what does the battery level indicator show in your case?

I haven't updated my NESizer with the most recent code you pushed.
It is running a hex with my NoteOn&Vel=0 changes, and a hack to mute the output at boot, but no other mods.

When I check battery voltage by selecting Settings mode, and holding Button 7, I get 4.3 on my segment LED.
I can update the firmware with your most recent code and check again if you'd like.