niles

Yes-I replaced RN1. When I say I hold my hand on the back I mean that it's just very sensitive to touch. It's not like that with the other switches, just sw2,7,9,11,12,13 - they all act like one switch, one led. The only ones that are working as intended are sw3,4,5,6. The rest are dead switch/dead led. I usually solder THT components from the bottom out of habit. Attached a picture below of back. using MIOS studio as you suggested, I get some LEDs to light up. I can't follow which DOUT 1-7 and DOUT 10-15 correspond to which LED, it seems random. I tried reading the http://ucapps.de/midibox_ng_manual_ngc.html page about LEDs so I see that different combinations=different patterns, though unclear if that applies to this or the little matrix on the top of the board. Don't suppose there is a test script that would light up LEDs in sequence? One question I have is how does the chaining work with J89 and J89A? I see I have to connect the Left Lemec board into J89A on the JA board, would I be able to test the lemec boards if I just plugged the left board directly into the J8/9 on the core board? I am not sure if they are a direct connection or somehow buffered/filtered through the JA board first. I ask this because I just want to move ahead at this point (and see what else I screw up lol) and some of the pins aren't connected between J89 and J89A, which could be normal or not.

Well I replaced all the ICs on the JA board and the problem is less but still there. Now if I hold my finger on some of the pads on the back, the leds light up. I tried my other waveshare board and it's the same behavior. Attached a picture. Maybe I just order a new PCB and the specialized parts. Fingers crossed I didn't damage the main uCore board

Ah ha - I must have just seen the '4816P' and so grabbed the bag with the wrong one. I installed the 1-103 in that location not the 2-103. I'll make that switch, hopefully I can salvage the one from the board, looks like I need it later on. Thank you again, I'll give this a shot and report back.

Quick followup on my SD Card not reading problem - Success! I was able to get the SD card to work :) It was something with the core board. No idea what it could be and not spending anymore time fixing it. Just redid the boards using new PCBs. The MCU was fine after all so now I have an extra for future projects. However....- I hooked up the JA board and loaded 'seq_l' program successfully in MIOS studio. However the LEDs and button activations are going haywire. I realized with slight horror that I used an older cable that I had made that was basically backwards. I have some extra HC595's from original mouser shipment and replaced the IC1 (directly under the SRIO IN shrouded header), but still getting the crazy led action. Good news is all the LEDs are lighting up and they are registering on MIOS studio, the encoder is as well. Bad news is they are just randomly flashing and activating on their own. Is there a schematic or pinout for this board so I know what I may damaged with incorrect cable? Could a bad cable have damaged the RN1, IC2 or IC3? Thanks!

Hi - very new to the forums and building a kit for the seq v4+, I have received some great help from Andy and Peter over on the seq v4+ troubleshooting thread but I have a more general SD card handling question. Background: I'm having a hard time getting the SD card to be 'found' so I can load a test program, and have not had success at all with that. Just keeps saying SD card not found. I've tried many variations of cards, my latest is a brand new 4GB sandisk SDHC microsd with adapter formatted FAT32. I have NG 1.036 installed and everything seems to be good so far...MIOS studio recognizes it no problem but just no SD card is found. I can confirm the cable is fine, no shorts between pins, I have continuity from card socket (a SD-RSMT-2-MQ) to the MCU board and even tried the 'simple SD card cable' from TK's website. Nothing so far has worked getting the SD card found. I'm on Win10 but same happens on Mac laptop. I think I had the cable backwards the first time on power up but I don't see how that could have fried anything, besides it still runs in MIOS studio. How does the SD card get detected in the STM32F4? Is it the mechanical switch on the side where the 'write protect' and 'card insert detection' are both tied to ground? Or is it one of the pins like CS? (I've read there are a few ways possible).CS (SD socket pin 1, J16 pin 10, RC1) is tied to GND. Is that right? Is there any type of way to 'fake' SD card detected because maybe it can read/write it ok but thinks it's not in there? Or perhaps a MIOS studio diagnostic? I see there is some commands via the 'help' command but not sure if any apply to SD card testing. I appreciate any insight anyone has into this, Thank you!

Well there's no shorts and I don't know what to do with that schematic anyway. I've built plenty of synth-related items but none that rely on SD cards. I'm at a total loss. It's too bad there's no way to just run some kind of diagnostic program that would tell me there's no input or output received or something. I don't know enough about how this MIOS studio works to debug errors.

quick question related to the pins. I am trying to trace shorts even further and RC1 (pin 10 on the J16), which goes to CS/SS (Pin 1 on SD socket). It's is the PB2 also called "BOOT1" on the MCU board. Disconnecting the MCU board it's shorted to ground, is that intended or accidental short? Thanks I fear I may just have to shell out for a new MCU board, not sure what else to try. Perhaps I can use the original board in another Midibox project in the future without an SD card lol.

I checked continuity and everything seems fine. The cable is something I did have wrong at first, so perhaps I fried a MCU pin or two. Is there a diagnostic program or command I could run in MIOS Studio that would confirm the pins are 100%? I'm using shrouded cable sockets and they are oriented correctly I think (please see photos though). I did order a few more SD sockets (arrow has free one day shipping today :) so I'll replace that just in case. It was simple enough to remove. The SD cards I've tested all format correctly under windows. I found a 32MB one (canon SDC-32M) that is formatted FAT, and a newer 8GB Kingston SDHC (SD4/8GB) that is formatted FAT32. They only contain SEQ_L.NGC , the file from the first post in the seq v4+ thread. Both have the same result. The schematic helped, thank you for posting that. Tricky that they put pin 9 out at the end of the SD socket Again, thank you for your help with this. I'm obviously hoping it's not the MCU but I'm not sure what else it could be at this point. Hopefully there's some kind of test I can run.

Thanks for the ongoing help. Do you know how to format FAT8 on a windows 10 machine? I have been googling but can't find any program. I did find an older post by TK that says formatting via MIOS Studio is the best method by doing sdcard_format, but it fails with this: If I type just 'sdcard' it says Reading CID and CSD failed with status 256. I'm at a loss, I've tried multiple cards and the one I'm currently working with is only 8GB and formatted FAT. The other high capacity ones only let me go as low as FAT32. Maybe I have a bad component but it is recognizing a card is in there. If I had the cable backwards on one end by accident at some point would that have done some damage somewhere? If I lay the cable down flat, with the connector holes pointing up, the notches are on the same side of each connector. I assume that's the right orientation. Edit - Also just in case it helps, only the green LED has been lighting up.

Having issue with the SD card - I have Midibox NG v1.036 loaded, it shows up in MIOS Studio. I have an SD card with SEQ_L.NGC inserted but when I try the 'load seq_l' command I get this: If I restart the core and MIOS studio without an SD card it says SD Card Not Found, so I assume it's not the cable? I'll admit the polarity of these IDC cables are giving me confusion for some reason, despite the videos haha. But I think I got that ok. I've tried a bunch of different cards, not sure what to do next. Any idea what I should try next?

Thank you, @Hawkeye! @gotkovsky I know you got it running (awesome) but in case anyone else has a 'not found' issue in MIOS studio, I had the really large USB switch set wrong - the one between OTG and regular USB mode. Once I switched that it showed up fine. On a side note, I definitely appreciate the multiple, smaller PCBs vs one or two huge ones. I did a NAVA build a year ago and that took seemingly forever and was just too unwieldy. Lastly, I was able to load the project.hex file posted from Hawkeye in an earlier post, but is there a newer, official build by TK for this? I have been looking and only found the SVN, no idea how to compile..was hoping the latest firmware binary would just be able to download somewhere obvious. I have a ways to go in this build and can only work a little bit at a time so I'm not too worried right now. However, if there is a seq v4+ firmware version specific to this kit, might be helpful if it's available on the midiphy page. Just a suggestion.

Thank you - I wasn't sure how much of that cable I'd need for this kit and was hesitant to tear it apart.

Still building the first few boards...probably a dumb question but what is the mouser part number for the grey IDC cable that connects the SD pcb to the core? I have the 34wire one (517-3365/34FT) but can't seem to find the smaller size on the BOM or my stash of componets. Looks like I'll need a lot. Thanks!

PM sent, thank you for managing the bulk order!