Forum Rule: Always post complete source code & details to reproduce any issue!
Page 6 of 6 FirstFirst ... 4 5 6
Results 126 to 141 of 141

Thread: TeensyTransfer

  1. #126
    Junior Member
    Join Date
    Dec 2017
    Posts
    11
    Thanks, should have googled that one harder. Got the rebuilt executable to run, but having the same problems. Just to clarify, this doesn't need any hardware to run correctly, other than the Teensy and prop shield, yes? Would extra wiring mess it up?

    Also to clarify, by format do you just mean erase it? Or is there extra stuff to do before the flash will accept uploads?

  2. #127
    Senior Member+ MichaelMeissner's Avatar
    Join Date
    Nov 2012
    Location
    Ayer Massachussetts
    Posts
    3,830
    Quote Originally Posted by zenby View Post
    Thanks, should have googled that one harder. Got the rebuilt executable to run, but having the same problems. Just to clarify, this doesn't need any hardware to run correctly, other than the Teensy and prop shield, yes? Would extra wiring mess it up?

    Also to clarify, by format do you just mean erase it? Or is there extra stuff to do before the flash will accept uploads?
    Extra wiring should not make a difference.

    Note, I am not the author of of Teensy Transfer (FrankB is). Typically format means to recreate the file system in the flash.

    I assume you have installed the UDEV rules on your system?

    You might want to watch the system log message to see what kinds of log messages are going by. On older systems, you would create a new terminal window and do:
    Code:
    sudo tail -f /var/log/messages
    On newer systems you might want to use:
    Code:
    journalctl -f

  3. #128
    Senior Member+ manitou's Avatar
    Join Date
    Jan 2013
    Posts
    2,574
    Quote Originally Posted by zenby View Post
    Alright, I'm getting a communication error only when I try writing things to the prop shield. I have erased the chip; -l and -i don't give me communication errors. And after I get a communication error I have to unplug it and plug it back in to fix the connection. Any ideas?
    Sorry propshield+TeensyTransfer is still not working for you.

    1) can you attach a photo of your setup (wiring and soldering)

    2) Do the SerialFlash examples work? Examples > SerialFlash > ... first run EraseEverything, then RawHardWareTest (what does RawHardwareTest write on monitor?), then EraseEverything and ListFiles (you may need to run other examples to put files on SerialFlash, or create your own file creation sketch) Note: if you want to run RawHardwareTest again, you must run EraseEverything first. And run EraseEverything before starting to create files.

    3) For TeensyTransfer you have to build and load Examples > TeeensyTransfer > teensytransfertool and in Tools you must change USB Type to Raw HID. What does teensytransfer -i report? teensytransfer -l ? teensytransfer yourfile ?

    4) if you get errors, can you paste into your post the actual messages
    Click image for larger version. 

Name:	propshield_headers.jpg 
Views:	72 
Size:	20.6 KB 
ID:	12229
    Last edited by manitou; 12-10-2017 at 11:29 AM.

  4. #129
    Junior Member
    Join Date
    May 2019
    Posts
    1
    I see this thread is rather old but it still looks like >THE< thread for teensytransfer...

    I have a Teensy3.2 and a prop shield. I have the teenstransfer hex file downloaded to the teensy, but the command prompt program just returns with no output.
    I've tried: teensytransfer -i
    and teensytransfer -l

    I've tried it on two PC's (WIN7 and WIN10) and in both cases there is no return on the console.

    And the weird thing is... the teensytransfer.exe program itself dissapears from my system after I run it. These are work (corporate) PC's so I guess an anti-virus might be the issue, even though I get no notification of malware etc.

  5. #130
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    12,190
    Hasn't been much activity with TeensyTransfer recently - it was finicky with a number of steps to get right in the right order as I recall.

    But AFAIK it was last working when the needed steps were found and followed.

  6. #131
    On my mac, running Catalina, I get
    Code:
    raine001@John-Raines-19 ~ % /Users/raine001/Downloads/teensytransfer -i
    zsh: bad CPU type in executable: /Users/raine001/Downloads/teensytransfer
    raine001@John-Raines-19 ~ % file /Users/raine001/Downloads/teensytransfer
    /Users/raine001/Downloads/teensytransfer: Mach-O universal binary with 2 architectures: [ppc_7400:Mach-O executable ppc_7400] [i386:Mach-O executable i386]
    /Users/raine001/Downloads/teensytransfer (for architecture ppc7400):	Mach-O executable ppc_7400
    /Users/raine001/Downloads/teensytransfer (for architecture i386):	Mach-O executable i386
    
    raine001@John-Raines-19 ~ %
    I THINK the issue is that the Mac program is a 32 bit binary and Catalina supports only 64 bits. I haven't used it before and I certainly might be wrong.

  7. #132
    Senior Member+ MichaelMeissner's Avatar
    Join Date
    Nov 2012
    Location
    Ayer Massachussetts
    Posts
    3,830
    Speaking of TeensyTransfer, I made some simple modifications to Teensy Transfer so that it would run on Teensy 4.0. There are some parts that are not enabled, because it used internal Teensy 3.x machine specific features that are not present in Teensy 4.0, but it does allow reading from a flash memory chip that was soldered onto a Teensy 4.0 audio shield. I cloned the library and example, so they would not overwrite the standard version. I've not done the github git clone submission form:

  8. #133
    I used another Mac on an older OS and teensytransfer worked properly.

  9. #134
    It looks to me like instructions for building all the versions of teensytransfer (on an ubuntu system) are in the makeall.sh file included in the zipped download--presumably adding one target (I think -arch x86_64) to line 28 might be all that's needed. It's a bit over my head.

  10. #135
    Junior Member
    Join Date
    Aug 2020
    Posts
    4
    Hi,

    I'm a total newbie and I'm working on a project where I need files on the Prop Shield. Somehow I can't get to Raw HID connection. I only get this message "teensytransfer: no rawhid device found". I'm working with Teensy 3.2, Prop Shield, Arduino 1.9.13, Teensyduino 1.53. What am I doing wrong?

  11. #136
    Senior Member+ MichaelMeissner's Avatar
    Join Date
    Nov 2012
    Location
    Ayer Massachussetts
    Posts
    3,830
    Quote Originally Posted by shole View Post
    Hi,

    I'm a total newbie and I'm working on a project where I need files on the Prop Shield. Somehow I can't get to Raw HID connection. I only get this message "teensytransfer: no rawhid device found". I'm working with Teensy 3.2, Prop Shield, Arduino 1.9.13, Teensyduino 1.53. What am I doing wrong?
    You might mention what operating system you are using, there might be OS specific things you need to do. Teensydunio 1.53 now checks if Linux has the correct udev rules, but I don't know if there are Windows or MacOS specific things to do.

  12. #137
    Junior Member
    Join Date
    Aug 2020
    Posts
    4
    Thanks for the answer! I am using Windows and I'm still trying. I also found that when compiling tetransfertool.ino I miss some header files. I am a real amateur, but i promised my daughter to build this lightsabre, so i will install linux if necessery. Fun continues and I am grateful for any input.

  13. #138
    Senior Member+ manitou's Avatar
    Join Date
    Jan 2013
    Posts
    2,574
    Quote Originally Posted by shole View Post
    Thanks for the answer! I am using Windows and I'm still trying. I also found that when compiling tetransfertool.ino I miss some header files. I am a real amateur, but i promised my daughter to build this lightsabre, so i will install linux if necessery. Fun continues and I am grateful for any input.
    when building teensytransfertool, in the IDE Tools dropdown menu, you must first set USBType to Raw HID Then after build and load, windows should recognize the Raw HID device, and you can run teensytransfer.exe. Try teensytransfer -i
    Code:
    teensytransfer -i
    ID    : EF 40 17
    Serial: D1 65 38 25 47 44 08 23
    Size  : 8388608 Bytes
    You can also test out the SPI serial flash with Examples from the SerialFlash library
    https://github.com/PaulStoffregen/SerialFlash

  14. #139
    Junior Member
    Join Date
    Aug 2020
    Posts
    4
    Thanks a lot manitou! I have set it to Raw HID. What do you mean with "building teensytransfertool, in the IDE Tools dropdown menu"?

  15. #140
    Senior Member+ MichaelMeissner's Avatar
    Join Date
    Nov 2012
    Location
    Ayer Massachussetts
    Posts
    3,830
    Quote Originally Posted by shole View Post
    Thanks for the answer! I am using Windows and I'm still trying. I also found that when compiling tetransfertool.ino I miss some header files. I am a real amateur, but i promised my daughter to build this lightsabre, so i will install linux if necessery. Fun continues and I am grateful for any input.
    I missed that you were still trying to compile the teensytransfer device. It can be rather tricky to build.

    If Windows has separate window for the Teensy downloader that pops up after you've installed a sketch like blink, you might be able to load the pre-compiled image in the 'extras' directory:
    • extras/T32_teensytransfertool_with_SerFlash_CSPIN6.ino.he x


    After the download window pops up, there should be a 'File' menu. From there do File -> Open Hex File. When prompted for a file, locate the above .hex file, and click on it. Then press the program button on the Teensy 3.2, and the download tool should load the hex file onto the Teensy. Assuming it installed, then exit both the Teensy IDE and the download window. After you have exited both programs, unplug/replug the Teensy. You should then be able to do a teensytransfer -i to identify that you have the prop shield installed.

    <added>
    If you are getting errors trying to compile the Teensy Transfer tool, please post the full error message. That way we have a better way of telling you how to fix it.
    Last edited by MichaelMeissner; 08-02-2020 at 05:24 PM.

  16. #141
    Junior Member
    Join Date
    Aug 2020
    Posts
    4
    Thanks, that was the solution! The first big step is done.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •