com - midi

[Evgeniy Chernyh]

Hi! Got a problem with discovery board com port connertion - it freeze when i choose com port and press connect. it connect like chibios comport in windows but control software can not connect to it. any thoughts?
How about making it connect like midi and transfer all thru sysex? i have stm midi drivers but don't know, how to connect it ti chibios..

[Johannes Taelman]

Hi,

Have you applied the documented modifications to the firmware for the disco board?

Generic data exchange over USB-Midi Sysex is not the right thing in my opinion. The only advantage is that it is "driverless".

Tunneling over SysEx is very inefficient, packing in 7bit. It's also quite useless to connect the Axoloti Patcher over MIDI. And it could confuse people, recording this sysex'es in a sequencer etc.

In the future I hope to develop a composite device, with a HID vendor specific part for Patcher interaction (rather than USB-serial), and a MIDI part for sequencing.

My arguments against the current USB-serial implementation is that it's data packets in a byte-stream in usb packets. USB-serial is really legacy, OSX asks to setup a dialup connection, windows needs a (signed) driver, linux users need to add themselves to the dialout group.

I believe USB-HID could be driverless, and more efficient.

On Tue, Feb 24, 2015 at 1:39 PM, Evgeniy Chernyh <man1...@gmail.com> wrote:

Hi! Got a problem with discovery board com port connertion - it freeze when i choose com port and press connect. it connect like chibios comport in windows but control software can not connect to it. any thoughts?
How about making it connect like midi and transfer all thru sysex? i have stm midi drivers but don't know, how to connect it ti chibios..

--
You received this message because you are subscribed to the Google Groups "axoloti-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to axoloti-dev...@googlegroups.com.
To post to this group, send email to axolo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/axoloti-dev/718167c7-c56c-4779-af47-9bc2be85ad0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Evgeniy Chernyh]

Afaik, hid uses interrupt transfer, so overall speed will be much slower, than cdc. Packing is bad, but we can use handshaking and switching to transfer non-midi information. Don't know about computer drivers, but on the board it is not hard to implement.
about discovery - yes, i define discovery, not axoloti. it compiles, i load firmware in st-link sw. On poweron I2S signals fine.

[Evgeniy Chernyh]

i tried hex firmware from this thread https://groups.google.com/d/msg/axoloti-users/1ub1DOCfCnI/aiN7fnRLjXcJ

it does not freeze, but show this

port: COM5

Initiating connect to COM5

creating tx thread...

connected

Ping: WaitSync Timeout, disconnecting now

Disconnect request

transmitter: thread stopped

can you public eclipse project file? i'm new to gcc. only worked in keil ide before. don't know what to do with makefiles))

[Johannes Taelman]

Please don't use old firmware!

If you have the tools downloaded/installed (as get_dependencies.sh does), you can compile firmware from the Board menu in Axoloti. You don't need to deal with makefiles.

Eclipse: use ChibiStudio, though I'm not sure about the right steps to import the project.

--

You received this message because you are subscribed to the Google Groups "axoloti-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to axoloti-dev...@googlegroups.com.
To post to this group, send email to axolo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/axoloti-dev/c992bb00-bcec-4895-aac0-8a8bb6e07667%40googlegroups.com.

[Evgeniy Chernyh]

have reinstalled all, checked all versions and.. got same problem - initiating connect to COM5 freezing.. 

also programs, that work with com (terminalbpp) also freezes, when trying to connect to this port.

old firmware works as com, i think it is not hw or driver problem. may be some compiler options??

вторник, 24 февраля 2015 г., 22:03:13 UTC+5 пользователь Johannes Taelman написал:

[Johannes Taelman]

Could you try a full flash erase before flashing the firmware?

Possible cause is that there is data in sector 13 of the flash, and that's where axoloti stores a compiled patch to run at startup. If it's not a valid compiled patch (must match firmware), this would be the result.

To view this discussion on the web visit https://groups.google.com/d/msgid/axoloti-dev/56312b8b-9f4e-4d45-8dcd-f0207b8315e8%40googlegroups.com.

[Evgeniy Chernyh]

BIG THANKS!! now works))

среда, 25 февраля 2015 г., 19:39:58 UTC+5 пользователь Johannes Taelman написал: