Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Josh last won the day on December 6 2015

Josh had the most liked content!

About Josh

  • Rank

Recent Profile Visitors

697 profile views
  1. Thank you - this worked! Amazing how it was such a small thing... Also, looked again and I don't see any documentation explaining what you just did. I know it's sort-of internal to the API/Descriptor Tool, but off the top of your head did I just miss looking at something? Anyways, I'm going to clean this up and write some MIDI functions. Will post an update later.
  2. I've been looking into this and trying to compare to examples for a bit now. Here's where I'm at: Some comments on stUsbHandle: struct tUsbHandle { uint8_t ep_In_Addr; // Input EP Addr - only referenced in phdc functions uint8_t ep_Out_Addr; // Output EP Addr - only referenced in phdc functions uint8_t edb_Index; // The EDB index - 1 - used lots - just an index, dont think its an issue uint8_t dev_Class; // Device Class- 2 for CDC, 3 for HID uint16_t intepEP_X_Buffer; // Interupt X Buffer Addr - initial
  3. Ran into something interesting, after a while of messing around on the PC, this came up on the Message Analyzer log:
  4. Do you think I have an issue with my descriptors? I've copied directly from the example in appendix B of the MIDI spec (linked), and below are some screenshots of what I see using various apps on the host. I did look over each bit and the unidentified parts in the USBlyzer HTML report are just because they don't have a parser for it I am thinking - but any thoughts after looking at them? USB Composite Device.html
  5. Thanks for the message. Stepping through the code with breakpoints, I see that "USBCDC_sendDataAndWaitTillDone(midiTest, 4, 0, 100000)" returns successful two times, and then failed once with error 1: TIMEOUT, and then fails with error 3: USBCDC_INTERFACE_BUSY_ERROR every time after that. I do not see the two "successful" data transfers in USBlyzer - although I'm not exactly sure what I would see. Note that I've changed the time out to be much longer, but this error pattern is the same with the original 1000 loop timeout. After this, I noticed I have interface 0 selected in "USBCDC_sendDataAnd
  6. Thanks for the replies! I've managed to sort out the descriptors. I've got the device showing up in the device manager as a Generic USB Audio device and I've checked the descriptors with USBlyzer and they seem okay. Device manager reports the device is working properly and I'm able to successfully view the device and it's input and output ports in various MIDI programs (tested with midi-ox and ableton live). Now I'm trying to send a midi message to the PC but am stuck again. In my test code I'm trying to spam a note on command (cable 0, channel 1: 0x09905840) in a while loop. Being naive, I
  7. Hi everyone, TLDNR: How do I set up MIDI descriptors for MIDI over USB so that I can get my PC to recognize my F5510 as a class-compliant MIDI device, either using the TI USB Dev package, api, and descriptor tool, or manually? I'm working on my first MSP430 project and hoping to get some help setting up the USB interface in CCS. I'm working with an MSP430F5510 on a custom board and trying to set it up so that it's recognized as a class-compliant midi device on the PC - then I will send midi messages to the PC to control music programs, etc. I'm stuck on where to start for configuring the U
  8. Thank you heaps for the comments! Not settled, just how I put it so will change - ty! That's interesting you ran into some issues with it - I was looking at a few example schematics released by TI (dev boards, etc) and a few had caps in there but said "DNP" which I took as "Do Not Populate" so didn't include. The one with the reset button includes a 1nF cap and I also found some TI documentation that says it needs to be less than 2.2 nF (http://www.ti.com/lit/ug/slau278v/slau278v.pdf).%C2'>
  9. Hi all, I've put together a design for a MSP430 Midi controller running over USB. I really wanted to learn how to make a PCB so this is my first design (and also first time doing the schematic for the MSP). Hoping to get some feedback before I send it to be made. I used a rule set template for seeed studio (which has no errors now) and have been referencing some of TI's designs but I imagine I've missed a few things. Any comments or constructive criticism is much appreciated =)
  10. Well, typically a lot more in the winter! I could tease you and say that while I don't live in an igloo, I do take my dogsled to work and bring my pet beaver (the moose stays home). I have many COLOUR TVs and we only see black and brown bears here. Also I lied about the sled and pets. Hey buddy
  11. Hi! ...that is all for now
  12. Hi! ...that is all for now
  • Create New...