Search results

Here is the X-ray of one of the boards. NXP chip in the middle, boot loader at the bottom, ST NFC chip on the right, flash top-left.

Project thread here.. https://forum.pjrc.com/index.php?threads/high-performance-custom-nfc-reader-based-on-teensy-4.76634/

My company GoToTags, makes NFC encoding robotics and software. We got to the point with off the shelf NFC readers that they couldnt meet our performance goals, so we decided to make our own. We worked directly with STMicro engineers on the board and antenna design and tuning; months of effort...

Best thing we ever did was remove PlatformIO; all it did was act as an annoying middle man. Given we use CLion we made our own cmake for Teensy and it has been great. We use the Arduino IDE and Teensyduino tools from cmake so we get all the updates and tooling.

I went through the process of getting the Teensy 4 bootloader chip (IC_MKL02Z32_T4_QFN16) added to the list of parts at JLCPCB. As always you will need to buy it from PJRC and send it to JLCPCB as a consigned part. Its now JLCPCB part# C9900168489...

It still unclear to me what is different about the lockable Teensy 4s. Is it that you have configured them differently when they are made? Im making a custom Teensy 4 and need it to be lockable.

Thanks for taking a look Paul. I'm not sure I understand your comment. Are you referring to the 5V-3.3V LDO? If so it seems well able to handle the current as its rated to 1A. The part is NCP692MN33T2G. https://www.digikey.com/en/products/detail/onsemi/NCP692MN33T2G/2194205 It's also being...

Im building a custom board based on a Teensy 4. We heavily use the Teensy 4.0 and 4.1 in our other projects but for this project we need a very small form factor and a limited number of exposed pins to talk with another chip via SPI and a couple other GPIOs. Ive read through countless forum...

Is there a way to have the Teensy 4.1 be in an off state when powered up? Ive read through how the on/off switch works in relation to the coin cell. I understand that without the coin cell it is on when powered, and with the coin cell it powers up to the previous state (on or off). But is there...

So we figured it out... one of my developers noticed that the device is sending data as if the shift key is being pressed. When we checked `keyboard.getModifiers()` it returns 0. We eneded up just making a lookup table for the chars we wanted to "unshift" and it processes correctly now. Im...

I agree that code is not correct, but it is not causing the issue. If I make the change to have keyPressed take the key, it produces the exact same result.

We have connected a USB HID keyboard device (think barbode scanner) to a Teensy 4 via the underside D-/D+ pins and are using PaulStoffregen/USBHost_t36. We have configured the device so it returns the following characters when a button is pressed. This works as expected when connected to...

Old thread... but the easiest way to to get the compiled teensy_loader_cli for your OS is to use PlatformIO, install the Teensy board and then get the file out of it. The paths: Linux: `$ENV{HOME}/.platformio` Windows `$ENV{USERPROFILE}/.platformio` and then the folder...

No idea what the real issue was here, but it was more complicated than just "linker order" considering I was using PlatformIO and I got different results based on code (not config). I ended up removing platformio, detail here...

Old thread, but I finally had to remove platformio. Posting this here for anyone else that comes by. This has only been used on Linux. Not sure what happens on Windows or macOS. ### Arduino The Arduino IDE is used for the compiler, Teensy cores and libraries. All updates are handled through...

Exactly. The commit where my proposed change is in the Arduino code explains the issue. https://github.com/arduino/ArduinoCore-avr/commit/4e469e0c83799ad6d3698e7cfa51ef8a5f2a2c76

It's not clear that this problem is reproducible in the arduino ide as it doesn't support multiple files. I believe this to be a linking order issue. Without multiple source files you can't have ordering. The issue is easy to see. The original arduino new.cpp had a limitation that it never...

Paul any reason to not mark the new and delete functions as weak? It seems that at one point the arduino code did not, but looking at this code now they are. https://github.com/arduino/ArduinoCore-avr/blob/master/cores/arduino/new

See related to the SPI library. It seems to be using "new" and "delete". If I remove my code that uses the SPI1 then it works.

If I manually add the weak attribute to the delete functions in new.cpp it works. Again, not a good idea. __attribute__((weak)) void operator delete(void * ptr) { free(ptr); } __attribute__((weak)) void operator delete[](void * ptr) { free(ptr); } __attribute__((weak)) void operator...

Ive made some progress but still dont fully understand. What I think is going on is that when the stdlib is being included it somewhere includes the same functions that are in "\.platformio\packages\framework-arduinoteensy\cores\teensy4\new.cpp" like "operator delete(void*)". The linker sees...

Teensy 4.1 1.58 Clion 2023.3.4 PlatformIO 6.1.13 toolchain-gccarmnoneeabi-teensy 11.3.1 Windows 11 platformio.ini (nothing interesting) Im trying to create a function callback in a class. If the callback takes an argument it fails. This works: std::function<void()> onChanged_; This does not...

That one is dead too. This is the latest: https://github.com/technyon/Arduino-CMake-Toolchain

Ive found several projects that attempted this, then died.. this seems like the latest iteration of the zombie. https://github.com/a9183756-gh/Arduino-CMake-Toolchain

Anyone using CLion without PlatformIO? If so, how? I spent the last 5 hrs chasing down why the Wire library was not working only to find out everything is busted if you set "build_type = debug" in platformio.ini...

To anyone else that comes along here, this bug also effects the Wire library.

PS, I tried to change the post title to me more useful/searchable to other but I dont see that is possible.

Your 2nd code is what I have and I think it works. I just dont have the knowledge to look inside the SPI class to know if using pin 39 as INPUT_PULLUP would mess up SPI somehow. There is a lot of bitwise operations on the register flags going on in there. I still think putting this in the SPI...

Thanks again. To be clear the Teensy is master and the TLC9547 is slave. I think by the fact were down in the weeds looking at if register flags conflict or not is an indication this is a thing to avoid, hence why it should be more explicit in the docs. For me, luckily I only put components on...

Thanks for the link. I already have full control of the ordering of when the code is called so can setup my digital input pin after SPI1... but that doesn't really answer my question. Does that cause any issues? If I set pin 39 input mode to input_pullup after it's been set as the miso for spi1...

Setup - Teensy 4.1 - TLC9547 LED driver which is a slave only SPI device; its connected via SPI1 with alternative pins (MOSI1:26, SCK1:27, CS1:38); MISO is not used or connected for this component as its not needed* - Serial1 with pins (RX1:0, TX1:1) - Digital input switch on pin 39 All three...

Thank you. That's exactly what I thought was happening. Since the local String b is beating created just after a, it is being put in the same memory position as a so the pointers are now pointing at the same place. Except both a and b don't really exist anymore, but the memory is still there...

If I ditch the "const char*" and use a String everywhere it seeems to work. Id still like to know why the above code doesnt work though. class ComponentY { public: explicit ComponentY(const String& name) { this->name_ = name; } String name() const { return...

Ive been struggling getting String appending to work. There seems to be a memory/pointer issue I cant figure out. Im not a C/C++ expert so its very likely Im doing something wrong, but Ive spent all day on this and cant get it figured out. This is being used for a serial logger. Any help would...

Old thread.. but I have a relevant question. I understand the Teensy 4.1 has 3 SPI with corresponding pins.. but do you have to use those pins or can you use any digital out pins? Im controlling a slow slave device and dont need the fastest implementation.

I had always been using COM1 on the UPA and Serial1 on the Teensy; that part was fine. the AC noise also went away when I wired them up properly. Here it is working. Ignore the janky wiring as all of this was just meant to be a proof of concept...

About 2 minutes after I closed down my computer in frustration last night I realized I had wired TX-TX and RX-RX. #whammy

I have a Teensy 4 and am connecting it via Serial1 to a 4D Display 43DCT via a 4D-UPA (breakout board for the display). The UPA docs state it is 3.3V logic, with 5V power either from USB or external power. The display and UPA work fine when connected via its USB serial so I know that is working...

What should be done with the unconnected power pins if powered via USB? - Vin - 2x 3.3V I noticed on this usage of a Teensy 4.1 the 3.3V are connected to a 10n capacitor. https://gitlab.com/CrazzyFrenchDude/peenaple_v1.1b/-/blob/master/PeeNaPle_V1.1b_Fab_Files/PeeNaPle_V1.1b_Schematic.pdf...

I have 2 Teensy 4.0s and I would like to connect a single momentary switch to program both Teensys. Do I need a diode between the Teensy program pins and the switch input? If not, I would be connecting two pins with 3.3V high. The other pin of the switch would connect to ground. If I do needs...

Hello all, I'm looking for feedback on the below design. We are more software people than electronics/hardware people and this is our first board. Hopefully there is enough detail here. I have a set of questions Id like to get answered, plus if anyone sees anything else that should be fixed...