First, since this is my first post here, let me say hello to you all, and introduce my self. My name is Chris, and Ive been lurking around here for a while, researching the teensy, and the projects that you all have made with it. It seems to be a very impressive/capable device, and I really enjoy seeing everything you guys have been able to create with it. I am totally new to embedded programming, but I've got a couple decades of programming various platformss (android, windows, mac, linux, etc) in several languages (c, c++, pascal, delphi, etc), under my belt.
I am currently working on a car-puter project built on a raspberry pi 3.0 for my truck, and I just purchased a teensy 3.6 because it sounds like it will do what I want it to do. Which is, I want it to act as a USB mass storage device proxy, between my car stereo (which only understands how to talk to USB mass storage devices) and my raspberry pi which is going to be linked to a hard drive storing all of my media files. The basic idea is that when the car stereo tries to browse or stream a file from the teensy, I will proxy the request over to the pi, which will locate the appropriate file, and return it to the teensy to serve it up to the stereo.
I've been playing with my teensy 3.6 for a few days now, and have been able to successfully load various test programs, and examples onto it, using both Arduino, as well as c++ code, and a makefile.
It seems that the teensy should fit well into this role, from all of the reading that I've done on here. Unfortunately, it looks like a USB mass storage device isn't yet supported for the 3.6? As far as I can tell from the core code, there is a USB MTP device, but that seems to be a stubbed out empty implementation. I have been poking around in the code, and in the programmers reference for the MCU for the last couple of days, and I'm not quite understanding everything that is going on when setting up the usb devices.
I would greatly appreciate it, if you guys could a) let me know if I'm on the right track here, and the teensy can in fact do what I want it to do, and maybe b) give me a few tips/pointers in where to look, to get an understanding of what I will have to do to create a USB mass storage device object similar to the other usb objects in the core code, that I can then use to implement my proxy.
Thanks again for any help you guys can give me,
Chris
I am currently working on a car-puter project built on a raspberry pi 3.0 for my truck, and I just purchased a teensy 3.6 because it sounds like it will do what I want it to do. Which is, I want it to act as a USB mass storage device proxy, between my car stereo (which only understands how to talk to USB mass storage devices) and my raspberry pi which is going to be linked to a hard drive storing all of my media files. The basic idea is that when the car stereo tries to browse or stream a file from the teensy, I will proxy the request over to the pi, which will locate the appropriate file, and return it to the teensy to serve it up to the stereo.
I've been playing with my teensy 3.6 for a few days now, and have been able to successfully load various test programs, and examples onto it, using both Arduino, as well as c++ code, and a makefile.
It seems that the teensy should fit well into this role, from all of the reading that I've done on here. Unfortunately, it looks like a USB mass storage device isn't yet supported for the 3.6? As far as I can tell from the core code, there is a USB MTP device, but that seems to be a stubbed out empty implementation. I have been poking around in the code, and in the programmers reference for the MCU for the last couple of days, and I'm not quite understanding everything that is going on when setting up the usb devices.
I would greatly appreciate it, if you guys could a) let me know if I'm on the right track here, and the teensy can in fact do what I want it to do, and maybe b) give me a few tips/pointers in where to look, to get an understanding of what I will have to do to create a USB mass storage device object similar to the other usb objects in the core code, that I can then use to implement my proxy.
Thanks again for any help you guys can give me,
Chris