smaudio
-
Posts
36 -
Joined
-
Last visited
smaudio's Achievements
MIDIbox Newbie (1/4)
0
Reputation
-
Ok, I think I've figured this out - After checking with another Din sync/MIDI converter it looks like it's not the clock being sent from the Midibox seq v4 that's wrong (and thus it's not a matter of voltage), but that the MC202 adds some extra time in the last step of every sequence. This makes it drift. I've worked out that the 202 sequences need to be trimmed a bit at the end to get the two to synch properly. I hope this helps anyone that comes accross the same issue
-
Hi blingy, have you managed to resolve your Din sync lagging issue? I seem to be having the same problem. I have level shifted the J10 clock output from my STM32 and I'm getting 4.99V on the start/stop signal (which works fine), but only around V0.20 on the clock signal. My MC202 does respond to changes in the tempo but it always lags behind a bit. I wonder if there is any way I could compensate for this lagging through the software.
-
Wow, Seems like we got a result!! Here are the results: app_skeleton_unmodified.hex: No drivers come up after upload and reboot. app_skeleton_without_usb_host.hex: Works! Query works too :) app_skeleton_enforced_usb_device.hex: Works! Query works too app_skeleton_r2023.hex: Works! Query works too midibox_seq_v4_087_pre4: Works like a Charm! Thanks so much for all the work and for an awesome OS for the MBSeq, I played around v 4.084 yesterday for the first time and it's an awesome system. Have a beer on me, it's the least I can do!
-
Hi TK, You're right, it seems that I'm using an A-type USB cable (it's got the letter A on it).. hm that'd be very interesting if that's the culprit. I've used another 2 cables but I don't know if they're type B as they haven't got a letter on them. Thanks for building the apps, if it's not easy to fake it in software, I can get a B cable later in the week and test it with that. Many Thanks :)
-
Thank you, here are the results: app_skeleton_r2023.hex: works, query works and core info come up in the window (like in bootloader mode) app_skeleton_unmodified.hex: loads without a warning, but after loading no USB driver comes up, and thus no communication can be achieved app_skeleton_without_usb_host.hex: driver comes up and query works! So do we deduce that there is something in the new USB host that messes up the communication in this core? I have attached the result after loading app_skeleton_r2023.hex and 4 screenshots of the messages exchanged while loading app_skeleton_unmodified.hex, in case they are useful. Best Regards
-
Here are some images from my core and MIOS studio to go with the points above too ;)
-
3) Yes, the query has always worked without issues under bootloader mode, I get the core information and everything in the device info window as expected. 4) It's just a MBHP_CORE_STM32F4 PCB from SmashTV's shop that I've put together with the components from Reichelt With the core working standalone like in your pic above, the same thing happens ('no response from MIOS8 or MIOS32 core..' in the device info box) however, I get information in the MIOS studio communication box underneath: Init DHCP, SD card not found, and when I type help in the command line, I get the welcome message and commands list, so it seems like the core communicates in normal mode, it just doesn't send the device info somehow...
-
Hi Thorsten, 1) the 'normal' driver didn't seem to appear in the list of USB sources here, only the bootloader driver when boot holding, so seems like the latest driver doesn't get transmitted at all from the core when in normal mode but.... 2) some success!! the midibox_seq_v4_083 driver does display the USB driver ('MIDIbox SEQ 4') on both Win and Mac, and also the other 3 MIDI drivers ('MIDIIN2 (MIDIbox SEQ 4)','MIDIIN3 (MIDIbox SEQ 4)', 'MIDIIN4 (MIDIbox SEQ 4)' )! However, I'm still getting 'No response from MIOS8 or MIOS32 core' and it won't get the core details listed underneath. The core does send a f0 00 007e 32 00 0f 4d 4f 53 33 32 f7 message though every time I query. So it seems like we need to configure the options in the new driver? Many Thanks
-
Thanks for that.. I successfully flashed the core with the midibox_ng_v1_032_pre4 STM324F/project.hex file through ST-Link 3.4.0 Win7, but I'm getting the same behaviour again: the Midibox NG app works fine on my MBSeq4 (READY.) but the drivers don't come up on either Win7 or Mavericks. Only the MIOS Bootloader driver comes up when I boot hold. I tried to find the saved USB MIDI driver in my PC device manager, but I didn't seem to be able to find something that fits - I looked in the same place where the boot hold 'MIOS bootloader' driver comes up and anywhere else I could think of. On the mac I deleted the MIOS Bootloader (the only thing that comes up) to no avail. I have used 2 different micro USB cables interchangingly, but I'm not sure they'd be just power cables as the boot hold MIOS bootloader seems to come up ok. I have tried everything both powering from ST-LINK or USB-MIDI (by stuffing the jumper on the module). The only thing difference I've noticed from your instructions image is that the ST-LINK utility Memory display size used to be 0x020CE8 and now it is 0x4DAD8 (not 0x12700). Would this give any clues to what is wrong? Many Thanks again
-
Hi Thorsten, Many thanks for looking into this (and for all the awesome projects)! I do appear to have a STM32F407 core on the STM32F4 Discovery board (STM32F407VGT6 MCU 168 MHz/210 DMIPS), so no luck there.. I should also say that when I flashed the core for the very first time on my PC, I did get the 'good' USB host showing up as 'MIOS' and everything seemed to work as planned (and I've been able to achieve this once again after flashing), but the host just stopped working somehow after I power-cycled again :( Other than that I don't know what else it could be.. it's very strange. Perhaps it's my STM32F4 then and I need a new one?
-
Hi everyone, I have a strange problem with my STM32F4 Discovery not being able to communicate with MIOS studio. I flash the STM32F4 with the mios32 bootloader no issues via ST link, but then if I reboot the core and connect through the left Micro-USB, the USB MIDI driver doesn't come up on either windows or macOS (so I can't connect it to MIOS studio). If I boot the core in boot hold mode, the USB-MIDI driver comes up on both Mavericks or Win7 (MIOS bootloader) the core gets recognised and can upload an application (ID=0), but when I then upload midibox_seq_v4_086 and reboot, even though it works on the displays of my MbSeq4, no USB Midi drivers again in either Win7 or Mavericks. To test further, through boot hold mode I uploaded midio128_v3_019, reboot, and the drivers do come up and I can use the terminal, but I get 'No response from MIOS8 or MIOS32 core' (I've checked with all Device ID values, none works). If I now try to upload midibox_seq_v4_086 I get the 'Warning: no reponse from the core' message half way through and the core doesn't seem to send an upload request after booting. I have done this when the STM32f4 Discovery board is not connected with the MBHP_CORE_STM32F4 module and it exhibits the same behaviour. Is this midibox_seq_v4_086 messing up the USB midi drivers somehow? Or perhaps some residual code somewhere if it connects under boot hold? Any help is much appreciated!
-
If you can't get the profiles only, put me down for an aluminium case (it'd be wasteful but by far the most effective way of getting those profiles!) Many Thanks
-
Many Thanks! Let me know
-
I mean without side, bottom, front or back panels, just the aluminium profiles (guides). Or if that's not possible, with whatever panels would be the minimum I could go for (eg. just side&bottom)?
-
Hi Kristal, would there be any chance that I just ordered a set of the profiles through you (no panels)? I have customised my Midibox seq and as a result I have to print the panels elsewhere. Let me know Thanks
