Best I can offer you the number of times the 7 Teensyduino software files meant for Arduino 1.8.x use have been downloaded from the PJRC website over the last 14 days (our server retains only 2 weeks...
Type: Posts; User: PaulStoffregen
Best I can offer you the number of times the 7 Teensyduino software files meant for Arduino 1.8.x use have been downloaded from the PJRC website over the last 14 days (our server retains only 2 weeks...
Forgive me, as I haven't kept up with every message (been really distracted by supply chain issues), but is this problem confined to just 1 laptop computer?
Regarding Arduino CLI:
Today...
Maybe try using Arduino CLI. It's not as lightweight as a makefile, but you do get excellent compatibility. Newest Teensyduino 1.57 packages for CLI / IDE2 are supposed to detect if you're running...
Can't see much of the code in your screenshot...
Did you also change Wire.begin() to Wire1.begin() in your program? Looks like this library doesn't call the Wire library begin function, so you...
Virtual machines cause a lot of problems. They tend to work fine for "normal" software. But for hardware access, there is a pretty incredible amount of emulation code between you and the real...
Any chance for a photo of the board? Just curious to see how it turned out.
If the root cause of trouble is overflowing the allocated stack space (just a blind guess), then moving the stack allocation somewhere else where you're less likely to overwrite anything important...
Possible, yes. As easy as just clicking the USB Type menu, no, at least not for Joystick together with Audio. For that, you'll need to edit usb_desc.h to create a custom USB type.
Maybe you have Serial.begin(9600) in your program?
On Teensy, Serial.begin() tries to wait for the Arduino Serial Monitor to connect. It waits up to 2 seconds if your PC begins the USB detection...
Look at the xy() function in the OctoWS2811 examples.
This is the one from the File example (in Arduino, click File > Examples > OctoWS2811 > Fire)
// A simple xy() function to turn display...
Look for them soon at Envistia
https://envistiamall.com/collections/pjrc-teensy-microcontrollers
I would imagine you'd write the channels mask to the MCTRL CLDOK bits to zero the LDOK bits for all the timers you wish to alter. Then write your new settings to some or all of the 6 timing...
I'm assuming you're editing this line when you connect the wires to pins 18 and 19?
if (!bmp.begin_I2C(&Wire2)){ // hardware I2C mode, can pass in address & alt Wire
But I can't see...
Looks like this should work. Adafruit's library is designed to work with any I2C port, so you shouldn't need to use "#define Wire Wire2" or edit the library to change "Wire" to "Wire2", as is needed...
I hope you can understand nobody can say specifically what the problem is with an unseen PCB. The best we can do to help you is offer some suggestions of tests to perform and explain what the...
Are these the sensor libraries you're really using?
https://github.com/pololu/lsm6-arduino
https://github.com/pololu/lis3mdl-arduino
If anyone is going to go to the trouble of editing these...
Unfortunately, no. The addresses I have are (probably) meant to be private.
I sent an email around the time I wrote msg #4. So far, no reply. But it's only been 2 full business days. Remind me...
Maybe the Linux version of teensy_post_compile should check if the udev rules are installed?
Until recently, this program was only delivered by the Teensyduino installer which checks if the udev...
Did you install the udev rules? It's required on all Linux systems.
This is indeed the default (no threads) behavior for Teensy 2 and 3.
On Teensy 4, the default has the stack start at the top of ITCM (RAM1) memory, and the heap is located in RAM2 memory.
First, install Teensyduino 1.57. Version 1.56 and earlier had MSQ output, which is basically PWM but with extra noise shaping stuff. Versions 1.57 adds PWM output for Teensy 4. But you still might...
Maybe run commands to uninstall and reinstall the teensy board package? Maybe if run with the verbose flag, info about *why* arduino_cli didn't install teensy-discovery might be shown?
This is expected behavior. The 15 sec button press only wipes the flash memory on Teensy 3.5 & 3.6.
Teensy 4.0 & 4.1 added the "restore program" which is written into the flash after fully erase....
Any chance you can trim the code down to something small enough to share here in a forum message, but still reproduce the crash?
I'm not aware of any production flaws or problems. I can tell you every board was tested with a sine wave diving a 10 ohm resistor in the test fixture, though the test lasts only about 1 second.
...
SPI protocol lacks multi-master arbitration or other sharing mechanisms. How do you imagine 2 masters could possibly work on any SPI bus?
I sent you an email. We have several with cosmetic flaws, mostly just stray solder paste on the through-hole pads. Will be happy to sell you these at the normal price. PJRC doesn't price gouge!
The USB controller operates with DMA accessing linked lists of structs in memory to define the properties of all the USB endpoints and manage all the pending data transfers. If you really want to...
Maybe look for signs of damage to the wires between the 2 chips. Since pressing the button is at least causing the bootloader chip to reboot the main processor, there's some chance the parts might...
I don't know what's causing the problem, but I can answer this:
An ISR, or just ordinary code which calls noInterrupts() and never turns interrupts back on, can interfere with automatic...
Maybe the IDE only writes changes the preferences.txt when you quit?
The teensy_secure utility looks for your key.pem file in 1 specific place. The full path it will search is shown in the Tools > Teensy 4 Security window.
On Windows, that location comes from...
You could just edit the code to change MAX_AUDIO_MEMORY if you *really* wanted to use more.
Each audio block gives 2.9ms delay, since the block size is 128 samples.
Looks like it should work.
2 blinks means it can't communicate with the IMXRT chip, the JTAG port isn't responding.
Documentation on the blink code is on the page for that chip. Scroll down to "Troubleshooting & Diagnostic...
However, as a blind guess, this might be your problem:
Using pinMode() puts the pin into GPIO mode. If done before analogWrite(), as your message seems to say, it has no effect because...
Pins 0 and 1 are not used by USB serial. That's info which applies to boards like Arduino Uno, but not relevant to any Teensy.
Please show a complete program which can be copied into Arduino and...
Yes, a buffer overflow definitely could "crash" that way. But better to think "get stuck" rather than "crash".
For example, you could overwrite variables in RAM used by USB Serial, or hardware...
Does the Program signal have 3.3V when you're not pressing the pushbutton?
Haha, that's pretty much the exact opposite of how I've used the 2 that live on my workbench. I almost never bother to screw them down tight (or at all) and I move them between various carrier...
Ok, ran the test again on both boards, this time using the screw to hold them done.
Exactly the same result, 1s on pin 22 & 28 and 0s on all other pins.
29093
I tested with the card tilted, exactly as you see in the photo. I too was lazy about using a screwdriver to secure it. ;)
I wired all the ATP pins to GND and ran it here on both MicroMod boards on my workbench.
29092
Pins set to input
Pin 0 state: 0
Pin 1 state: 0
Pin 2 state: 0
Does the problem change if you remove the diode and connect the power with just a wire? Or maybe use a DC voltmeter to check the actual power supply voltage arriving at the VIN pin?
An issue was...
I keep a couple MicroMod boards on my workbench for software testing. I'm not seen any pins failing. But most of the tests I usually run are meant to test the more complex libraries like Audio,...
I can't speak for Sparkfun. I can only comment on PJRC's role. And I suppose I could dabble in some guesswork...
I can tell you every MicroMod Teensy is tested on a test fixture PJRC made for...
You can use extmem_malloc() to dynamically allocate the PSRAM which isn't already consumed by EXTMEM variables.
The raw speed of internal RAM, either tightly coupled RAM1 or normal RAM2, isn't going to be the limiting factor for this sort of application. Plenty of other aspects of how your code is written...
Many people probably won't touch IDE 2 until Arduino calls it officially released.