Jump to content

latigid on

Frequent Writer
  • Posts

    2,516
  • Joined

  • Last visited

  • Days Won

    147

Everything posted by latigid on

  1. Hehe! Yes, plenty more than 44 sold but some people are not aware that this thread (or even this forum!) exists.
  2. Haha! Honestly I had the PCBs built for a while but never found the time to put everything together. I had to test a PCB revision anyway so though it was a good opportunity.
  3. Took a while! I didn't have enough of one LED colour so it is multicoloured
  4. Awesome! Glad that you could get to the bottom of it and that the caps didn't explode too violently!
  5. Congrats #43 ! Looks great in the rack!
  6. Yes! Just switch the jumper appropriately.
  7. Hi Laurent, For euroceiver versions 1.5 or older there is a J0 jumper above J19, near the USB. There is a jumper on the line transmit board but it basically supplies power over the DB cable, which you don't really want as there is a big voltage drop. If grounding is not the issue then I would typically expect power supply (e.g. noisy USB), bad cabling or similar. At least you can test directly without the line drivers now the SEQ is open. Best, Andy
  8. It is important with older euroceiver boards that the J0 jumper is installed. This grounds the two systems. Is yours grounded? To rule out the line drivers, you can bypass them but you'd have to open the SEQ case of course... Something else to try would be a different power supply e.g. the USB+5V instead of the regulator etc. Best, Andy
  9. That pad (pad 3) is not connected, so you can ignore it!
  10. Where is the trace lifted? Attached is a layout snippet that I hope could help.
  11. Hello, Not sure sorry... But you should be able to interrupt the J8/9 header with your module. Best, Andy
  12. It should press fit but Peter has a technique to use Scotch tape to hold it in place before lowering the case. For me, I slightly roughen the back powder coating (say 120-grit sandpaper) and apply drops of superglue to the corners, away from the edge. Then I carefully place the protector in. If you mess this up though, you'll get a nasty smear on the plastic, so tape is probably safer and sufficient.
  13. Excellent job! Regarding the light|shield/standoff collision, I had the same experience but like you say, it is simple to just cut out a little bit. I also found that it was useful to cut out a bit of the waveshare JTAG header (the side near the crystal) to avoid collisions with the THT resistors on the back of the base PCB.
  14. We have seen a case where trying to flash with the PA0 port left floating could lead to a corrupted bootloader. Hence the resistors R101 and R102 seem to be very important (that were not installed on your initial build). The footswitch/gate LEDs are driven by the buffer chip IC6, so it is expected that they don't illuminate with no inputs. Anyway, great that it seems to work well!
  15. Were the CN3 jumpers removed from the DISCO board? Otherwise the SWD programmer is connected to two STM32F4 chips. To my knowledge the circuit shown is correct but it has been a few years since I tried it.
  16. Connecting over JTAG might be a good try. You'll find some documentation for that on the wiki, especially flashing with an ST-LINK/DISCO board http://www.midibox.org/dokuwiki/doku.php?id=wcore
  17. If you think an available commercial device can fulfil your needs, then get one! DIY is a different thing. It is potentially more expensive and you have to put in the tools and effort to finish things, but the journey can be very rewarding and sometimes you can obtain tools that are not found elsewhere, often for the very reason that they would be impractical or uneconomical to produce in scale.
  18. Looks really great! Depending on the width and power draw of the modules, you might want a few more bussboards/PSUs. See how you go! Best, Andy
  19. Well done! Are you building the CS too or somethin else?
  20. Sorry, the extent to which I could help is already in the posts above. If you have more specific questions there might be others who are more into code modification. But at the moment it is hard to know what step you are on. It sounds to me like you are stuck right at the beginning, and I think it is rather up to you to learn how to modify the code to get what you want out of it.
  21. Hi Frederik, Yes, most ports with specific functions can be used in parallel. J8/9 is for SRIO i.e. input/output shift registers that chain in parallel (DIN/DOUT) J19 is for SPI with two chip selects (AINSER/AOUT) etc. Check the STM32F4 Core details The SRIO chain extends in series parallel, no need for additional Cores generally. Regards, Andy
  22. https://github.com/midibox/mios32/blob/master/mios32/STM32F4xx/mios32_ain.c https://github.com/midibox/mios32/blob/master/modules/ainser/ainser.c https://github.com/midibox/mios32/tree/master/modules/aout Basic drivers/assignments: https://github.com/midibox/mios32/blob/master/mios32/STM32F4xx/mios32_spi.c https://github.com/midibox/mios32/blob/master/mios32/STM32F4xx/mios32_iic.c Maybe it would be easier for you to use the Arduino and output an analogue voltage to be read by the STM32F4 AIN? That way you can use your working system without much extra coding effort. MBIO supports AIN either on the MCU ports J5A/B or using the AINSER module (typically less noise on the signal).
  23. As far as I know, there are no I2C peripherals that were coded into MIOS32. The closest thing that I am familiar with is the I2C MIDI modules, that according to TK. were not trivial to code for, and at that on very low-performance 16F PIC chips. All the MBHP framework gives you is a hardware port on the MCU. You could consider to compare your arduino sketch with a device running off an STM32F4 chip or similar. Alternatively, you might find more code examples of SPI devices. Maybe you can try to code a driver for a similar sensor with an SPI interface? The uCapps project is here: http://ucapps.de/midio128.html -- it is more targeted towards general users who would like to use the project without writing code for it. The git project is here: https://github.com/midibox/mios32/tree/master/apps/controllers/midio128_v3 You would need to modify the code to suit your needs. Note that the code is written in C, not python. You can find the documented functions and some examples here: http://www.midibox.org/mios32/manual http://ucapps.de/mios32_c.html Best of luck to you if you decide to follow this journey. Others will probably not write the software for you, but if you post your modifications and explain where you are having difficulty, some might be able to help.
×
×
  • Create New...