Search results

If you have a C++ rule which forbids multiple "return" inside a function, then the last code is okay. Otherwise the previous just prevents a double assignments to busStatus for a better machine code (supposedly the compiler is not smart enough to do that optimization).

Your return is inside a conditional block so it lacks of a return when condition is false.

So yeah, my second T4.1 runs fine. I probably left my first T4.1 running at 816MHz one day or more under condition where overclocking was not safe.

So with a new T4.1, I was able to go with 812MHz (but I didn't test too long). Getting back to my T4.1 with 16MB PSRAM and uploading the same program, it runs fine but then I got something wrong: That T4.1 was running 812MHz fine in its early days, so I'd be inclined to think that...

The program I tested is simply the example _Teensy/Tutorial 1/Blink. After a success, I altered delay in both "delay(1000);" between 100/400 and 400/100 so I can check the right program is uploaded and running. I'm also doing so to distinguish it from the default one running after a long...

When just using TeensyLoader even with default settings (Faster, 600MHz): KO. If I only use TyCommander "Upload New Firmware" after recompiling Blink (just light LED ad aeternam) by closing TeensyLoader, I seem to be able to have the right behavior and a stable USB port: OK. So now I avoid...

Basically, I need to do the long process of resetting the firmware before uploading mine. If I try to upload without resetting, it looks as if uploading works but I have a situation where Teensy is rebooting (which may explain the spurious USB serial connection) because when I try to have...

Now back to blink demo, I now have a toggling between two screens of TyCommander : So basically I need to unplug devices and plug them in reverse order to have a working blinking. Now I'm trying different ways. Seems TeensyLoader (closed just after recompiling a source after modifiying it) is...

Hell no... USB issues are back... seem deeper.

Ok, it looks like my other USB port was conflicting with Teensy 4.1 because when I unplug the other port (my external keyboard and my external mouse), then unplug T4.1 then plug it back and… blinking is now regular and TyCommander reconises it. Gosh! If I plug again my external keyboard and...

After a long time not developing upon Teensy 4.1, I'm back. Whenever I tried to upload a new firmware, I'm losing USB ports - including the Teensy port. So I tried TyCommander as TeensyLoader is not helping me there. I use the blink demo and set original delay of 1000ms to 100ms to make it...

Updated to 2.3.1 then installed 1.59.0 under Windows 10. Was able to build and run the test program.

When I had a laptop with Windows 11, I had once an issue with files copying. I don't know whether it may be related in your case:

Having COM9 connexion but receiving nothing was clearly due to using Serial1 instead of SerialUSB1, which is my mistake and is now fully resolved in that regard. As for COM8, the issue is that Arduino IDE's Serial Monitor was automatically connecting to Teensy Dual Port COM8/COM9. Now under...

Could you elaborate? I have no idea of what it means.

I had been blocked upon 1.58.0 or later for over one year. So I was stuck on 1.57.2. Whenever I tried to install 1.58.0 or later, I get the same issue as above with no access to serial port(s) or to teensy port to upload next build and so no idea how the program ran. I'm really clueless about...

So getting back to 0.59.5, after uninstalling 1.57.2 and firing Teensy uploader, I reinstall 0.59.5 and recompile EchoBoth. Upload the firmware in Dual Serial mode and... have a stable connection to teensy port and still access to COM8 and COM9. G*d! It really wears me out !!!!

Yes, I noticed I had to replace Serial1 by SerialUSB1 to have COM9 working but thanks for the clarification as I didn't know it.

Windows 10, Arduino IDE 2.2.1, Teensy 1.57.2. Back to 1.57.2 since the more recent versions are not working. So I tried EchoBoth.ino again. I made some changes : HWSERIAL is Serial1, and I set LED to ON when receiving through Serial and OFF when receiving through HWSERIAL. [Correction] if I...

Windows 10, Arduino IDE 2.2.1. Sketch EchoBoth, HWSERIAL replaced with Serial1 and using DualSerial USB mode. I tried 0.59.5 and still the same issue since 1.58.0: I have intermittent connections (shorter) and disconnections (longer). Cannot see my dual serial ports on any terminal. Firmware...

I just noticed it in the list. I have both 0.59.3 and 0.59.4. So having 0 instead of 1 is a way to say they are BETA?

Using Arduino IDE 2.2.1, boards manager is only offering me up to 1.58.1, no 1.59. I also tried SHIFT+CTRL+"Arduino: Update Package Index" but that didn't change anything. Note that I cannot use 1.58.1 or 1.58.0 as they mess up the uploaded firmware (including the default LED blinking program...

@BriComp That's what I thought first but look at the commented code, they are not the same.

Your MultMatrices function may be inlined and unrolled, allowing good optimization and fast execution. Supposedly arm_mat_mult_f32 is inlined (or not), the fact that you need to initialize parameters outside arm_mat_mult_f32 (arm_mat_init_f32) seems to indicate its loops are using structures...

Did you update the Teensy board package before you got into those issues? If I try above 1.57.2, I lose the USB connection and even Arduino IDE cannot find the board. If I get back to 1.57.2 and do the very long process (>15s) to reset the Teensy to the default blinking led firmware then I can...

(Is there any way to delete an attachment which contains errors? I wanted to replace but the attachment system is obscure to use)

I have mapped GPIO6 for my project this way: So I multiplexed the high order 16-bit of GPIO6 into mix of input/output signals using latch or bi-directional buffers. - GPIO6.PIN[32..24] = 8-bit MSB address bus as output or control/system bus as input (CLK and /WAIT in later details). -...

@PaulStoffregen It seems PMs are forbidden here. Where can I send you my two .7z archives to you?

Sure, but understand it works fine at start and I don't know how to trigger that condition. I prepare the archives (one with source and another with product) that I'm going to PM you. Using library SdFat at version 2.1.2 in folder...

Ok, it makes sense. So I guess I must close the Teensy application first then I can Remove/Update/Install a package. Now I'm back to my personal laptop (again, Windows 10, Arduino IDE 2.1.1) and if I retrograde to 1.57.2, tzz80-zexall runs fine on my T41 and I can see the zexall messages from...

It was already given before your post: "Windows 10, Arduino 2.1.1". Do you need more info? The one giving headache is Teensy 1.58.1. Mostly: Dual Serial, 816MHz, Small code.

Well for now I was just expressing my frustration and I'm well aware that long duration shouldn't be a problem because it shouldn't be a common occurrence. "compile_helper": ok, I understand. I indeed removed then reinstalled to overcome it. I was hoping stable 1.59 will be out because I want...

Basically, I had to retrograde to 1.56 or 1.57 to get back the things running fine. When I try to get back 1.58.1 and when I don't have the compile error due to a missing "compile_helper" file, I lost the access to USB ports again. ***SIGH*** Windows 10, Arduino 2.1.1. EDIT: I get the issue...

I'm clueless why it ends this way OK, I'm seriously starting to despair and harbour a certain hatred towards Teensy 4.1. I have a personal laptop and a work laptop. I've installed this release many times under both types of Arduino IDE and also PlatformIO. It works fine a moment (as long as...

Ok, thanks. I will try that.

*sigh* I'm not counting the weird things I have when I try to compile my project... I'm writing a Z80 emulator which is connected to a true Z80 bus (though 36 signals). I have an INO file called MZ80K-CPU.ino with several included files. One is MZ80K-CPU.z80.original.h (which is more or less...

So whatever I installed as release version, I got the same "weird" behavior so it has nothing to do with that version. It looks like Serial.printf/print[ln] are not blocking functions (I thought they were) because if I replace a delay(1000) by delay(10000), I get more USB traces. So I suspect...

I'm having got some troubles to get a correct behaviour after building a program. I'm using that release to build a program with a Z80 core emulation. It worked fine the first times I installed a version which was only working with Arduino IDE 1.8.x (Windows 10) then I tried your 1.58 beta...

Since it appears there is no beta #4 with String corrections, I tried that beta #3 then copied the cores directory which contains String corrections in the GitHub but with no avail: WString.cpp: In constructor String::String(unsigned char) WString.cpp: 70:9: error: 'utoa' was not declared in...