Search results

  1. A

    Access to more GPIOs on Teensy4.1

    Nice catch thanks! Unfortunately, I can't share my PCB, but I'm willing to review your design or answer any hardware questions. SparkFun has some hardware files for their MicroMod Teensy Processor Board that may be helpful.
  2. A

    Access to more GPIOs on Teensy4.1

    I ended up ignoring the warnings, and the board seems to be working just fine. I didn’t test every pin, but all the ones I needed functioned correctly. Your code worked perfectly as-is—thanks!
  3. A

    Access to more GPIOs on Teensy4.1

    Thanks for sharing your code, you saved me days of work! Was the board successful? Tried your code, seems to work, but I can't really test until I build a board. I get these warnings for GPIO_EMC_33-GPIO_EMC_41: warning: conversion from 'long long unsigned int' to 'uint32_t' {aka 'long...
  4. A

    Teensy 4.0 CAN2 (CRX2/CTX2) Not Working

    It seems it may have been a breadboard issue. I tried a new breadboard with the same software and hardware setup, and it worked fine. Thank you for helping me narrow down the issue!
  5. A

    Teensy 4.0 CAN2 (CRX2/CTX2) Not Working

    It did compile, can.h is custom header, setup() and loop() are in a separate file. When I call can_rx_print() I can read CAN1 and CAN3 fine so it not a build issue. Please just focus on the second sketch if you're anxious about custom code issues. Thank you!
  6. A

    Teensy 4.0 CAN2 (CRX2/CTX2) Not Working

    Hello, I'm having issues with my Teensy 4.0. I'm running the following code and successfully reading messages on CAN1 and CAN3 using the `can_rx_print()` function. I'm transmitting standard CAN 2.0 messages: CAN1 is connected to CRX1 (Teensy pin 23) and CTX1 (Teensy pin 22) CAN3 is connected to...
Back
Top