Just to add to the confusion I modified your sketch slightly to run within the Arduino IDE using a Micromod board. The modified sketch:
#include <arm_math.h>
#include <chrono>
int64_t GetTime()
{
using...
A couple of things that might be happening is that the Teensy might have completed sending your print before you can open Putty. If you change the sketch to:
void setup() {
// put your setup code here, to run once:...
@KurtE made some changes to MTP_teensy to simplify how MTP has to be configured. It looks like we never updated that example for the changes to MTP. Basically in looking at the current sketch:
MTPStorage storage;...
If you look through the sketch you will see two primary functions for getting the data:
uint32_t buttons = joysticks.getButtons();
and
joysticks.getAxis(i)
where axis data is an array of 64 depending on your...
Looked at the library and it is pretty straight forward. The teensy 4 may just be too fast. You can try to add some delays after reading pressure_baseline and at the end of the loop. Maybe start with with delay(1000)...
I got frustrated that the library did not use SPI Tranactions so I modified the sketch and library so it now uses transactions. Also made some tweaks. Tested the OV2640 on the T3.2, T3.5, T3.6 and the T4.0 and all...
Sorry havent got back to you sooner. Been a busy few days for me but I have been looking at Logic Analzer traces from the arduino R3, T3.2 and the T4. When the T4 fails to complete the image transfer its in the middle...
Know I am jumping in here late but it looks like you have Rx on the GPS going to Rx (serial 5). Try swapping it so so Rx on the GPS goes to the Tx on the Teensy (pin 20). In other words RX->TX and Tx->Rx
The previous sketch kind of pushes the limits of the camera clock so this version sticks with the original version of 8Mhz for the camera. Suggest that you start with this version before pushing the clock.
// ArduCAM...
Well before you do that I fiddled with the sketch again - issue really is the delays in the read fifo buffer. Right now with my 5642 seems like it is working reliably including video mode. And now I am not fiddling...
The problem is that the example sketches. Been testing this and seems to work better for JPEGs. Have to check the other capture modes. Let me know if it is working for you.
// ArduCAM Mini demo (C)2017 Lee
// Web:...
Try using bmp option. Seeing the same thing here and trying to troubleshoot. What’s going on. Something with this camera. As I said didn’t see these issues with the ov2640
@Paul
Been playing around with the Arducam and decided to test on the Teensy 3.2 and looks like issue:
has the same issue not just the T4's. Probably missed that in the threads.
Don't bother. I just reverted putting the begin's in the constructor and put them in the sketch. Just downloaded the updated library, https://github.com/mjs513/ArduCAM_t4 , and give the sketch below a try:
//...
Updated sketch
// ArduCAM Mini demo (C)2017 Lee
// Web: http://www.ArduCAM.com
// This program is a demo of how to use most of the functions
// of the library with ArduCAM Mini camera, and can run on any Arduino...
I did find that at times I would not see the camera but a simple cycling of the power would resolve that issue. Also did found that we have have to add the spi.endtransaction after completion of the capture fixes issue...
@the-photographer
I got my OV5642 and hooked it up to a Teensy 4.0. And it worked:
I am using the following sketch downloaded specifically tailored to the OV5642 that I go from the Github Arducam.
// ArduCAM...
Teensy runs alot faster than an R3 thats why the mods to SBI and CBI. Something else must be going on. As I said I have a OV5642 on order and should arrive tonight. So I can play tomorrow or when I get it.
EDIT:...
Simple answer is yes - if you dont have that uncommented it won't know what camera you are using. But just in case I ordered one and should be here today.
I just pushed an update to the library (not tested yet) that allows you to select Wire and SPI ports. The constructor has been changed to:
ArduCAM(byte model ,int CS, TwoWire *i2c = &Wire, SPIClass *spi = &SPI);
...
Ok looks like you are going to have to edit ArduCAM.cpp - made me look a bit deeper. At about line 115 in the file you will see this:
#if defined(__SAM3X8E__)
#define Wire Wire1
#endif
The library defaults to...
Will see if I can help since I don't think I have that particular camera. Looking at the example it looks like it not getting a different value than expected for the 5642.
//Check if the camera module type is...
Its been a while since I played with Arducam but I remember I had it working with a T4.0. With that said I did have to modify the library a bit to get it working by adding a delaymicroseconds on CBI and SBI. If you...
Ran the problem code from this thread https://forum.pjrc.com/threads/73301-TeensyDuino-1-57-flashes-fine-anything-else-same-code-bootloops?p=329705#post329705 to check "Fix const init on Wire, SPI, HardwareSerial" and...
Looking at the errors and then confirming my suspicions. The adafruit library that you point to does not support the Teensy LC only the T3.x series. It specifically calls out the Teensy 3.1 or 3.2.
If you look in...
Just doing a cursory review there are a couple of commands that pertain to the enabling the cursor.
1. showCursor(enum RA8875tcursor c,bool blink) and
2. setCursorBlinkRate(uint8_t rate)
showCursor takes two...
Been playing around a bit with this. As @defragster said - nothing obvious. I tried adding crashreport right the beginning:
void setup() {
Serial.begin(115200);
Serial.print(CrashReport);
while(1)();
I...
Find latest posts