Antichambre

Most of the issues I found about "ACMD41" are a voltage problem, Gerald is maybe right you need to check that...

In the firmware, mios32_sdcard.c

Yes you can add a delay mechanism at startup.

The SPI doesn't use high transfer rate, edit:but more than 2MB/s for sure. A SC 1Go is maybe enough? Maybe try another HC, other brand/model. Mine is a micro-SD PNY 16Go HC I with adapter. Note: I've just checked: // init SPI port for fast frequency access (ca. 18 MBit/s) // this is required for the case that the SPI port is shared with other devices MIOS32_SPI_TransferModeInit(MIOS32_SDCARD_SPI, MIOS32_SPI_MODE_CLK1_PHASE1, MIOS32_SDCARD_SPI_PRESCALER); 18Mbit/s is the maximum, it's 2.25MByte/s. Very close to 2MB/s Do you really feel the difference?

So don't use XC, I've got a HC and it works fine.

I know it works when started correctly but did you try another SD-Card, this one is perhaps a little sensitive...

MIDI is supposed to isolate your devices electrically(opto-coupled), did you try to disconnect the devices one by one? Maybe only one device causes this issue... Is there another MIDIbox connected to?

Did you try another SD Card?

Hi Andy, First thanks for taking a look. I didn't but I will add those jumpers. It's a good idea, it adds more flexibility. Done! CAN(with transceiver) is a differential pair signal, then bad behaviour like crosstalk to power and audio paths should be very limited, but you're right this has to be tested, noted! Best regards Bruno

I finally decided to add CAN transceiver to the board. The modules will be able to communicate natively in midi thru the regular euro power supply ribbon, using MCAN. No need of an other board to connect to the external world too, just a connector in front which will give access to the lines MCAN_L and MCAN_H. Best regards Bruno

Thanks! :) Yes for CAN, J18 is always the one. But Andy's wCore and Disco platform have only One-Wire connection. This one has Power pins for transceiver supply, RX and TX are separated. But you can add the regular Resistor and a Diode on the dipBoardF4 to link others Cores directly and easily with the One-Wire. This MCAN connector may be called J18E for 'extended' I suppose... A small transceiver module will be created to link the CAN bus with the external world, internally I planned to use the Euro Power connector, the power ribbon by using BUS1 and BUS2(last pins of the 16pins IDC) called CV and GATE sometime but never used in fact. Best regards Bruno

Autocad is my best friend since a long tilme now ;)

Hi, This is some update about the Core part of the project, I just finished to design it, artwork is not perfect but PCB and assembly are ready. I achieve the size of 12 HP and a depth which doesn't exceed 45mm, overall with IDC connectors present at the back. I can reduce it to the previous 11 HP but result is less clean at the front and assembly is more complicated then it will be 12 HP. The features: Euro Module 12 HP x 45mm. 2 MIDI In/Out. 2 independent USB, one Device, one Host. Micro-SD Card. Reset and User Button. 2 leds. Power switch, acts on both external and USB power. It is optional. Automatic switching between the Power sources, EXT/USB. Priority to external first. Can be connected to a regular Euro power connector (IDC16), regulation from 12V. Can use 5V from your skiff or provide it to the bus. 'Regular' MIDIbox ports In the order: J4, IIC A and B. J5, internal ADC for 2 analogue Inputs. J8/9, SPI 5V(SRIO). J11(2xMIDI IO). J15, displays(serial only, 2 CS lines). J16E, SPI 3,3V, Reset and User buttons, 2 leds(. J18. MCAN, Ready for CAN transceiver or 'One-Wire' CAN connection. J19, SPI 5V. Some 3D render: The PCB, all SMD will be assembled by manufacturer. It can be used for small desktop project too. I designed this module for the HAARP but it can be used for other application, you can use it with the MIDIPHY Analog modules to create the perfect interface for your modular system. And you can create your own Surface Control and/or your hybrid analogue modules. Voilà Best regards Bruno

Thanks man for having checking it. We can now put TK in the loop... @TK. ;) if you confirm it too, it can be modified in the repo. Best regards Bruno

What is the solution that you retain from this? You can use bitmaps, one for each screen, first you write into it then you transfer the whole bitmap to the screen one by one( cs by cs) and maybe only the one which has changed using some flag, the problem with this is that you will use a some of the RAM, 128*64*9/8=9216 bytes(9K), maybe not bad depending on your app. Best regards Bruno

Yes just remember you also built a SeqV4+. ;)

Beautiful design for both! No doubt you will sell it fastly!

It was not all the time but more than other people for sure, electrostatic thing maybe, we never knew.

I know a guy I used to work with who can't touch any computer because they hang. Yep it's strange sometimes ;)