PaulStoffregen
Senior Member

I've not heard of anyone has writing code for Pico to work with Teensy's audio shield. I did see a few people working on generic audio stuff (not specifically for SGTL5000 or this shield) but it looked like a pretty...

SPIFIFO isn't really recommended anymore, but I decided to give it a quick try just to see how much of the CPU time on a Teensy 3.2 would remain unused if an IntervalTimer uses it every 5 microseconds. Here's the...

Yes, there is a solution. All you need to do is use a recent beta version, because PDM support for Teensy 4.x was added after 1.53 was released. Get it here:...

Yup, let's fix the struct in imxrt.h and see if anything breaks. ;) EDIT: committed a fix. https://github.com/PaulStoffregen/cores/commit/64f7d7c1eededf0102510530a4e621395c4d51f7

Yup, sent a pull request just now. I'm not sure it's 100% working yet. I'm seeing a lot more VSYNC interrupts than screen refreshes. I added a some code to print the actual refresh rate.

Opps, sorry, I made some mistakes. Working on it now...

Send a pull request for continuous FlexIO DMA. I took the liberty of replacing Defragster's continuous "F" mode in hm01b0_testv3.ino.

I'm working right now to add start / stop for FlexIO, as similar to Kurt's API as I can.

Just wanted to ask which buffers are really meant to be DMAMEM vs DTCM? I see this in the examples. uint8_t frameBuffer; uint16_t imageBuffer; DMAMEM uint8_t sendImageBuf; uint8_t frameBuffer2 DMAMEM; ...

Yes, I believe your library tries to do the dynamic allocation of FlexIO resources, right? The camera interface is a bit special through, because only shifters 3 & 7 support receiving parallel signals. The other 6...

Yup, that did the trick. I see where I went wrong. A silly mistake really. Sent a pull request to fix it. EDIT: with the latest updates I'm getting a really dark picture...

Can you point me to that DMA serial receive code?

Before trying to answer, I need to admit two things. 1: I've only read Kurt's code quickly, haven't actually worked with it or analyzed carefully 2: Obviously I don't know everything about FlexIO DMA, since I...

I believe all you need to do with Teensy 4.0 & 4.1 is edit the sample rate number in AudioStream.h. That file is located inside your Arduino folder. When you search for that file, you should find 2 copies. Pay...

Hope you can find whatever I missed on the FlexIO hardware trigger. It's probably something "trivial" I overlooked. I wouldn't toss that code! It still could be really useful on Teensy 4.1 where we don't have...

Looks like my display woes might be from pulling in the latest ILI9341_t3n. When I run graphicstest from ILI9341_t3, my display works. But graphicstest from ILI9341_t3n now gives a white screen. Later today will try...

The example seems to no longer work with my ILI9341. Not sure why... can't do more right now.

Sent a PR with the work-in-progress DMA code. https://github.com/mjs513/TMM-HB01B0-Camera/pull/7/files When you run it, you'll probably see this in the serial monitor ERROR: 19764 manual triggers were needed...

I'm playing the FlexIO DMA. Can't seem to get hardware triggering to work, but the DMA does transfer the image if I cheat and manually trigger the DMA channel each time the shifter status flag is set. Going to send a...

Ok, I just sent a pull request with initial FlexIO. No DMA yet, but it should be fairly "easy" to just set up a DMA transfer which reads from that FlexIO register and writes to the buffer.

I updated to the latest TMM-HB01B0-Camera from github, in prep to clean up my flexio stuff, but it seems I no longer get a working image from either "s" or DMA. I'll admit, I fell behind on the forum these last couple...

Should I make the FlexIO code just read the whole 324x244 data? That would be simpler...

Somehow I was under the impression we were keeping the first 320 pixels and discarding the last 4. Just to confirm, on each line of 324 pixels, we're supposed to ignore the first 2 and last 2 pixels and keep the 320...

I just connected all 3 power pins to 3.3V. That test board doesn't connect the video signals at all. They just route to those pads in the middle of the PCB. Only power and I2C are actually connected. All the...

Right now I'm using Sparkfun's ML carrier board with ILI9341 connected to the left side pins. Nothing special on the HM01B0 camera. On the breakout board, which is still at least a week away, I put 2 camera...

More fiddling with FlexIO... and I finally have it somewhat working. For reasons I don't fully understand, it's capturing only 7 of every 8 pixels. So I added a bit of kludge code to add 4 white pixels to fill in the...

Another detail to keep in mind is the display redraws the screen from its own frame buffer at a speed probably less than 60 Hz. I recall seeing a register to adjust the internal refresh speed. But no matter what...

I'm working on FlexIO again today. Building test code inside your lib and targeting 8 bit mode, mostly just overriding the readFrame() function while I struggle to get it just working in any way at all. Will convert...

I started playing with FlexIO for the camera. So far it's unresponsive, but hope to have something soon... Pulled in the latest QuadEncoder.

Running the DMA version now. Wow, frame rate is so smooth. Seeing some tearing & artifacts.

Which Teensy are you using? The process is different on Teensy 4.x than the older boards.

I finally got the display wired up and have it running here too, showing a super exciting view of my oscilloscope from the workbench. Send another pull request, just minor stuff & compiler warnings.

A little breakout board to play with the signals on a Teensy 4.1 arrived last night from OSH Park. I build one this morning. I'm running the camera completely on 3.3V. Haven't looked at the data yet, but it...

I tested just now by adding Serial.println("test"); to main.cpp. That original Makefile compiles it properly. I uploaded the hex file to a Teensy 4.0, and indeed it does print "test" every second when I open the port...

I believe the Himax HM01B0 camera does support HSYNC gated PCLK. Try setting bit 5 (mask 0x20) in the OSC_CLK_DIV register (address 0x3060). Maybe change this line in HM01B0.cpp {OSC_CLK_DIV, 0x0B},...

That crystal should be fine. From everything you've said, especially that you do observe the crystal oscillating under some circumstance, I'd say the crystal is very unlikely to be your problem. There are 2...

The "queue" objects are meant to let your program get access to the actual audio samples. See File > Examples > Audio > Recorder for sample code. Edit that code to delete the part which writes to a SD card and instead...

I also want to know why it would do this, because it should not normally blink 8 times if you have used the IMXRT1062 chip. But I can not see your PCB. I know nothing of its design details. Even if I had the design...

@mamdos - Can you tell me which hardware you're using for passive PoE? If I wanted to experiment with various diodes and resistors, which gear should I buy to give me the PHY-destroying scenario you had?

You can use Serial.availableForWrite() to check how much space is remaining in Teensy's transmit buffer.

Looks like you changed Wire to Wire1 only in setup(). You also need to edit these lines in loop() Wire.beginTransmission(address); error = Wire.endTransmission();

Sure, just connect the button to the Program pin and GND.

That probably explains why the ML carrier board schematic has the wrong I2C address. The Himax camera is address 0x24. OV7670 uses 0x21, according to a couple pages I could find.

To try answering your question.... This really depends on what you meant by "functional difference". The short answer is they use exactly the same communication. I have made every effort to keep the functions...

By default, the timers used by IntervalTimer run directly from the 24 MHz crystal clock. No. The 24 MHz clock they use is fixed at 24 MHz, regardless of how the rest of the chip runs. Well, expect in the...

Reboot your PC. Then run the Teensyduino 1.53 installer before you run the Arduino IDE.

Oh, I know that mistake well too!

Looks like Sparkfun's ATP carrier board lacks any sort of USB host current limiting or even a 100 or 150 uF capacitor. As far as I can tell none of their other boards do USB host, so they're probably not yet familiar...

Did you solder GND which is next to pin 0, or GND which is between VIN and 3.3V? The one next to pin 0 (on the audio shield) must be connected. It will not work if you used a wire only on the other GND.

Ok, 7mm it is! Here's roughly what I have for a breakout board with alternate camera pins. As you can see, I also routed pins 0-23 to a Teensy 4 layout so we can plug in shields for testing. The 24 pin FFC...

I started a quick carrier board design which brings out the pins and attempts an alternate 4 bit camera connection which should leave all the audio pins available. Does anyone know the correct distance from the M.2...

The udev rules changed since 1.53 was released. Here are 3 possible solutions. 1: Run "sudo cp /tmp/49-teensy.rules /etc/udev/rules.d/" as the installer suggests. That will put the 1.53 version of udev rules onto...

If you're running I2C at the default 100 kHz clock rate, maybe try adding small capacitors between the signals and GND, located close to Teensy. Shielding the I2C wires might help too.

Yes, though "blind guess" would be a better phrase than "explanation" when we can't see your code or which library you're using or your wiring. So here's a few blind guesses 1: The library might be hard-coded to...

I can confirm 5.2V is perfectly fine for VIN & VUSB, as long as there isn't a large spike above 6V during startup. I'm sad to say 0.65V is a pretty bad sign, likely hardware damage. When 3.3V power measures only...

Use INPUT_DISABLE

The thread is #4-40.

Here is layer 2 from that part of the PCB.

Sounds like a defective or damaged board. I asked Robin to contact you directly. If you can, please try to find the 6 digit order number from your purchase.

Have you tried the 15 second button press to fully wipe the flash memory?

If you run the code from msg #6 and change the number of bytes in the line with malloc(), you should see the reported memory usage change.

If you do the 15 sec button press, then wait about 1 min while it wipes all the flash, please know the LED blink program you get after that process is complete implements RawHID, not Serial. So it is supposed to be...

Very unlikely. If uploading still works, the hardware is almost certainly still good. First step is to check Tools > USB Type in Arduino. If that got changed to any of the settings withing Serial, then no COM port...

With the audio library, you can use AudioMemoryUsage() to see how much of the AudioMemory you reserved is actually in use. Details here: https://www.pjrc.com/teensy/td_libs_AudioConnection.html Using the more...

Yeah, saw that. The code is in so many files with so much extraneous abstraction layer stuff that it was simpler just to write minimal code from scratch. Maybe we'll use that library eventually, but pretty much...

Ok, I've played with the HM01B0 camera a bit more. It seems to be 3.3V tolerant, even though Sparkfun's is powering it with 1.8V. It's definitely transmitting 1.8V signals which is pretty marginal for receiving with...

The USB-C is on the carrier board. https://www.sparkfun.com/products/16400

I got the camera to start answering I2C with the Wire scanner example. This is needed to turn make the camera respond. // turn on power to camera (1.8V - might be an issue?) pinMode(2, OUTPUT); ...

I'm pretty sure it's too late for Sparkfun to bring out those 2 unused pins.

Looks like the camera needs 1.8V signals with the way Sparkfun wired ML carrier board. But they have 2.2K pullup resistors on SDA & SCL to 3.3V, so I don't really understand how they intended this to work. The...

It is unfortunate the way Sparkfun connected the microphones. When(if) the camera is working in 4 bit mode, perhaps we can convince them to make another base board with the camera using only pins 40-45 and connect...

The tentative plan for Himax HM01B0 camera support is to use FlexIO2, similar to AN12686. I'll attach the PDF to this message. HM01B0 pin pin# NXP Usage ---------- ---- --- -----...

I will send you one soon.

Maybe subscribe to this other thread about attempts to go to 8 channels. https://forum.pjrc.com/threads/60557-48kHz-8i80-USB-Audio

Ok, here's a fix. Find w5100.h. It should be in {Arduino}/hardware/teensy/avr/libraries/Ethernet/src/utility. Search in the file for "__IMXRT1062__" and edit the resetSS function like this: #elif...

Looks like we may be doing something too fast for that old W5100 chip. I did get W5100 to work with Teensy 4.0 by setting Tools > CPU Speed to 150 MHz. And to answer your question: It's been used many...

Looks like W5100 may be not working with Teensy 4.0. I tested just now. W5200 & W5500 definitely do work with Teensy 4.0, but W5100 doesn't seem to initialize. All 3 work work with Teensy LC & 3.2.

Here's one that's a DIY PCB, but it was meant for Teensy LC. http://rasterweb.net/raster/2016/02/19/teensy-lc-bob-v1-2/

It really depends on what sort of applications you will develop. Most programs use RAM1 for nearly all variables and RAM2 for buffers and larger arrays. Sometimes the PSRAM is really needed when you just can't fit...

That's really a question for Sparkfun. While I understand everyone has a lot of questions about this not-yet-announced product, please try to be patient. Holding a Q & A session before release really isn't...

No, there's no Ethernet PHY support.

I've added a BGA pinout diagram to the T4 bootloader chip page.

I have not personally tested this way, but from NXP's documentation it probably should work. As with all freshly designed PCBs, best to build & verify only a few prototypes before committing to production quantities....

Hold the control key and click Teensyduino. Click Show Package Contents. In the new package contents window, navigate to Contents > Java > hardware > teensy > avr > cores. There you will find folders named teensy3...

That pattern, alternating between 0 and 1 or between 0 and -1, is exactly what happens when only 1 of the 2 signal wires is connected.

On both Teensy 4.0 and 3.5, the timers run from a peripheral clock which is slower than the CPU clock.

Try replacing "reinterpret_cast<char*>(sbrk(0))" with "(char *)&_heap_end". EDIT: oh, wait... using "&top" is completely wrong for Teensy 4.x. Try this instead: extern unsigned long _heap_start; extern...

I have Windows 7 Home Premium here on a laptop, but it's got an i7-2760QM processor, not Celron. It's a relatively clean & unused Windows 7 install, mostly just for testing Teensy hardware. Do you think I could...

We should probably also (someday) extend AudioEffectDelayExternal to have a mode where it just works with a user allocated buffer. Then it could be used with 16 MB on Teensy 4.1. Not only can you have twice as much...