Getting started with Teensy 4.0

Status
Not open for further replies.

rew

Member
I just got my teensy 4.0 in the mail yesterday. I thought I'd try to "get started".

The "getting started" is written for teensys up to 3.6, not 4.0. That'd be fine if things would work precisely the same. But they don't, at least not for me.

I run Ubuntu. My work machine still has 16.04 because that had a working arm-none-eabi compiler. Home has 18.04, but responds identically.

I've connected the teensy to an USB cable. It does the slow blink. I downloaded the teensy application, it shows me the start window. I press the button and it continues to prompt me to press the button.

At one point in time I've seen it complain in the verbose log that it found my teensy but couldn't open it. I then installed the udev rules, but now it does not report finding my teensy anymore.

So far I also don't see the teensy-4 binaries for slow and fast blink in the blink-binaries-download.

What am I doing wrong?
 
Do you have any plan when support for Teensy4.0 will be added to the teensy loader ? For the one wo like to use other tools that Arduino....
 
Oh, opps, the stand alone Teensy Loader hasn't been updated yet.
Might I suggest that a proper error message would've been helpful? When I saw the verbose log, I could at first see "device found, but permission denied". A quick "status message" say at the bottom the main window would've been even more helpful. That should've changed to: "device found, but not compatible with this version" once I fixed the permission issue. Now with nothing in the window and nothing in the "verbose log", I spent some time debugging something that had no chance of working.....
 
Actually I am not clear from the original description, if you downloaded the Teensy loader CLI app or you downloaded Teensyduino?

As for the CLI app, there have been a few threads about this already, including: https://forum.pjrc.com/threads/57176-teensy_loader_cli-and-Teensy-4-0

In that thread I started making a change, to allow the T4. However there is some interesting thing in the T4 file that it starts the output at a very high memory address (where the FlexSPI memory is), which the CLI program does not like as it exceeds how much memory it allocates a buffer for. However up on that thread, another member made a patch that instead of offsetting the storage into the array by the offset value it simply remembers the offset value and stores the values at the location minus the offset, which worked for him.

I had concerns about this, as not sure if we could get a second offset record and then the data could collide.

I proposed to detect if another offset record came in to remember the minimum of these and if necessary then move the stuff we have already put into the memory array... Have not done that yet...

Also this does nothing about setting the RTC....

Kurt
 
I wanted to "get started" with my new teensy 4. So I googled "getting started with teensy 4.0" and got "getting started with teensy" as the first hit. So that's where I started. It didn't mention 4.0, but I assumed that was because it would be precisely the same.... And when I followed the directions, I got the slow blink as indicated, so things lined up that I thought it would be appropriate.
 
Thanks!
I've put off the "then learn how to do it the other way" until now, so now I could continue doing it the way I was trying before.
 
I've updated the stand-alone Teensy Loader to version 1.48.

https://www.pjrc.com/teensy/loader_mac.html
https://www.pjrc.com/teensy/loader_linux.html
https://www.pjrc.com/teensy/loader_win10.html

Also updated blink_both.zip to have files for Teensy 4.0, and all the other files are rebuilt with version 1.48.

Hi Paul,

Along those lines, wondering if you might take a look at the CLI code. I have a version in a PR: https://github.com/PaulStoffregen/teensy_loader_cli/pull/48
That appears to work for the T4, but still does not do anything with real time clock stuff...
 
Status
Not open for further replies.
Back
Top