brtaylor
Senior Member

Thanks, that works for me on Teensy 4.1: Teensy Loader, Command Line, Version 2.2 Read "spi_example.hex": 18396 bytes, 0.9% usage Soft reboot performed Waiting for Teensy device... (hint: press the reset button)...

Oh nevermind, I was testing with a Teensy 3.6, since that was what I happened to be working on. Tried again with the Teensy 4.1 and I can repeat the issue - no soft reboot working for me either. Interesting that I'm...

I just checked my use case again. If I don't have the Teensy plugged in and powered on, my readout is: Teensy Loader, Command Line, Version 2.1 Read "spi_example.hex": 15572 bytes, 1.5% usage Error opening USB...

We'll need more details - is it hanging on Waiting for Teensy device... (hint: press the reset button) Or is there some other problem? Have you installed udev rules? Is the teensy connected via USB and powered?

Yes, use the teensy_loader_cli with the '-s' option. See: https://www.pjrc.com/teensy/loader_cli.html

Hi Robert, Check out this thread: https://forum.pjrc.com/threads/54114-Extended-Pin-Numbering It's about a custom 3.6 and using the additional pins. In short, you may need to update core_pins.h to add the pin...

Thanks! I actually meant air pressure as a replacement for the BME280. Regarding staging, when I was working as a researcher at NASA AFRC, we had a close-call where the Flight Termination System on a UAV was...

Also, if you have good experiences with a different static pressure transducer, please let me know.

So far our Flight Control Systems have only used the Teensy 3.6. I do see noise on the BME280 if there is any sort of transmitter on the vehicle. Haven't had any issues with SD or any of the buses. We occasionally get...

I could be wrong, it's been a few years since I messed around with the Teensy 3.6 startup code, just one of the things that is sticking out at me on a quick glance.

I don't see a crystal on the RTC. On Teensy 3.5 / 3.6 it's included on the board - I wonder if the startup code should be edited for it?

Paul, is the board designed to a temperature range (i.e. -40 to +80)? Thinking that this could be cost effective for a commercial product I'll be developing later this year.

I use CMake for Teensy 3.x, 4.x, and LC: https://github.com/bolderflight/core/ Has 'hex' and 'upload' targets and uses the command line uploader for uploading to the Teensy. It's modified from the standard Teensy...

My library works fine at receiving the high accuracy GNSS data that you'll get from applying CORS or RTK corrections. Be sure to download the latest from: https://github.com/bolderflight/ublox-arduino During the...

You'll need the ground wire, only the power should be cut. Otherwise you can cut the trace on Teensy to separate VIN from VUSB and use a standard USB cable.

Ideal world we would have 3 layouts of each teensy: 1. Current Teensy breakout for solderless breadboarding 2. MM for compact product integrations 3. DDR2 SODIMM (i.e. Raspberry Pi Compute Module 3) for product...

Not from PJRC and not my work, but this Teensy 3.2 reference board clone has a BOM: https://github.com/thewknd/teensy-boards/tree/master/Teensy%203.2%20reference%20board%20clone I built it years ago and it works.

Is there a good definition of the protocol? All I've found is forum and github discussions - enough to understand the approach, but not enough to write a driver.

Thanks! It seems pretty daunting and I'm not sure if it'll be successful. Probably faster to just make another GCS from scratch.

I just thought I would add that looking at the bits/second isn't the best measure because they aren't spread evenly over the time interval. I'm running this on a control system running at 50 Hz. If we consider that all...

I send the heartbeat at 1 Hz, the GNSS data as I get new data from the receiver at 5 Hz, and the attitude, speed and heading, and battery voltage at 25 Hz. The packet sizes are: * Heartbeat: 9 bytes, includes...

It's a very small piece of code, but I wonder if this would help: https://gitlab.com/bolderflight/software/mavlink I wrapped a class around a few of the mavlink packets I use for our flight software to make it...

Works great Paul.

Yes, it can be done. I use the -s option on my linux boxes that only have one Teensy connected, that often means that I don't need to press the program button or use a GPIO to "press" it.

Hi Paul, Can confirm the sha1sum and Teensy Loader 1.54-beta6b

Ditto, it doesn't fix it on my Ubuntu 20.04 either.

Just to be clear, IMUs don't measure angles, they measure angular rates (i.e. deg/s), acceleration (m/s/s) and sometimes magnetic field (uT). You'll need a filter to estimate the attitude from those measurements....

MPU9250 is way faster on SPI than I2C. It's been several years since I tested the performance, but if I recall correctly it's something around 22 us to get data from one IMU on SPI and around 200 us to do that over I2C....

Which IMUs? EDIT: nevermind, saw the code snippet of LSM9DS1. I haven't worked with that IMU, but just based off the fact that SPI is available, my initial reaction would be to go with SPI. Put all the IMUs on...