Rio

I want to update openhantek (software for certain DCOs) before doing some tests. It seems that the last official version supports the dds120 ... Update: I got the last openhantek 6022 variant running with dds120. It is not possible to record directly inside, but I can configure following params: I could export a CSV or save it as PDF. Additionally I can zoom and measure (as tools).

with "Ground connected" do you mean that I should connect both "Probe ground clip" to the ground of the SEQ, right?

I will test later. j16E is from the LPC17 core board, right?

I can do that. do I have to pay attention to DCO connections? I have a dds120 here: https://sigrok.org/wiki/SainSmart_DDS120 the probes can be switched 1:1, 1:10. The software is a modified openhantek variant ... however, what is completely unclear, why is the failure rate dependent on the amount of devices connected and powered on the midiports?

it goes through this loop: https://github.com/midibox/mios32/blob/3cb2f368e39a686451ce2759966530251f455681/mios32/common/mios32_sdcard.c#L181 and ends up here: https://github.com/midibox/mios32/blob/3cb2f368e39a686451ce2759966530251f455681/mios32/common/mios32_sdcard.c#L190 and MIOS32_SDCARD_PowerOn is repeated thereafter (after a while)

a delay - based on? The startup is already delayed enough by the logo display (about 3 sec)

I need an accurate timing, especially when reading data. where did you get the SPI speed information from?

I would like to find out why there is a problem with the cards or if there is a common problem with the massive port connections of external devices in conjunction with the SD cards and if there is a possibility to solve it via a hardware or software solution (for stable boot/detection)

The Sandisk Extreme 4GB is a SDHC. The other slow card has a writing speed of 2 MB / s - so i would like use the extreme. 

A slow card (1Gb) always seems to be running. This has FAT as file system and I can override it via sdcard_format in terminal. For the Sandisk 4GB Extreme: the SEQ will usually hang there (as well as when booting). I have a second Extreme Card. It shows the same behavior... So the card ist NOT defect. After successful formatting with SdCardFormatter for that card, nothing has changed.

I could try it, but I do not think it changes anything. it seems to me that the mass of the devices that hang up is decisive. Can this possibly be fixed by sourcecode? (possibly for the loop when initializing, because then it runs constantly, as soon as the card recognized...) @gerald.wertI have a USB dco at hand, I'm not sure how I can meaningfully measure what.

I have replaced the cable with a thicker and kept the cable as short as possible. but unfortunately it did not improve. Does somebody still have an idea?

I had thought so synonymous and turned off one by one (for each boot process), but in the end, no statement can be made, which device is the cause, but it depends only on the amount of devices which are connected and turned on.

Hey, thanks for the first hints. I have now tested the following: if I provide no power to all my devices, which are connected from SEQ through several ports (INs, OUTs,IICs) , then the SEQ boots always fine with detected SD. It starts to hang more often when more devices are turned on while booting. And yes hawkeye - it's true - it only affects the bootup. Once detected, the SEQ is working fine with the SD. I'll take your advice with the wiring...we'll see, or someone else has a different guess.

Can it be that the connection to the SD card is too unstable, or is influenced and would a decoupling cap make sense for the power supply of the reader? Just strange, that once it has been correctly detected, it also works stably. I would be grateful for any help..