Search:

Yet another printf() post ;-)

I've been looking into Teensyduino's Print.printf because I'm implementing a Tee Print class with multiple outputs and I wanted to make sure that the printf...

Are the TLC5948s and the NRF24 on separate SPI busses already? If not, and while this would be a fascinating problem to debug, you could potentially make your life a lot easier by patching your board...

Re: the bite sensor, 10 years ago you could buy a cheap sample pack of Quantum Tunnelling Composite (QTC) rubber pads on a number of educational/science online stores. These were great because they...

This seems to use what is known as 10-bit addressing ("2-byte read" in the manual). I don't think any of the standard Arduino or Teensy libs support that!

However the sensor can be reconfigured to...

Otherwise, this reminds me that the I2C implementation does a similar sort of bit banging to rescue a stuck bus. Maybe this can give you some inspiration:...

If you want to go low-level, you can check the manual here: https://www.pjrc.com/teensy/IMXRT1060RM_rev2.pdf

Also study the existing libraries and the core source code:...

I found that after upgrading to Teensyduino 1.54 my custom hardfault handlers did not get called any more. Here's the result of my investigations for future reference.

The cause is this commit....

Ah yes, I posted in the wrong thread!
Correct. I get the 8 second pause and restart. How do I get my custom fault handler running again?

On platformio, after upgrading to framework-arduinoteensy 1.154.0, I can no longer set a HardFault handler.

Minimal example:



FASTRUN
static void hardfault_handler_isr(void) {
...

No I'm not -- I thought about using it, but there was no documentation and I wasn't sure what the units for the timeouts should be. There was also quite a lot of code in there and I got worried that...

For reference, I've managed to make the RTWDOG interrupt work.

My mistake was that I had forgotten to call
NVIC_ENABLE_IRQ(IRQ_RTWDOG);

With this enabled, the interrupt fires and I can...

This is working well now for most of my state that I set from the control loop.

There's just one variable that I'd like to write from the RTWDOG interrupt, and somehow can't seem to set -- either...

I'm not using the watchdog interrupt to set the DMAMEM variable.

I solved my problem -- turns out I needed to call
arm_dcache_flush(&counter, sizeof(counter)); for the value to persist. I have...

Strange: the DMAMEM trick worked for a while, and now not any more.
Even with a minimal, clean sketch the value resets every time:



DMAMEM unsigned int counter;

void setup() {
// put...

Thanks, that looks exactly like what I need!

My application requires a watchdog timeout of 5 milliseconds, so I can't use the other ones.
It's part of the control loop for a micro-hot plate that runs at 1KHz.

I'm going to try this, but I'm worried that the delay is too short for EEPROM writes — this is RTWDOG/WDOG3, so the interval between interrupt and reset is fixed at 255 bus clock cycles.

1000...

I'm trying to debug the causes of a RTWDOG reset by saving some state to non-volatile memory.
A single bit would be useful, 13 bytes would be perfect.

Does the Teensy4 have any memory that
-...

Any thoughts on setting a very large time slice to do cooperative multi-tasking with TeensyThreads?

I needed yield-based cooperative multitasking that works on both Teensy 3 and Teensy 4, and so...