Search results

Replying based on your other thread about JTAG programming a custom board. Tie MOD / AD_B0_08 to GND for programming and debugging. High is for boundary scan mode. The easiest way to test would be to write a program in Arduino IDE and enable verbose output during compilation. Click on verify or...

See this thread https://forum.pjrc.com/index.php?threads/ethernet-header-socket-board-to-board-part-no.74260/

https://forum.pjrc.com/index.php?threads/teensy-4-1-ethernet-pins-socket.65288/#post-266193 Samtec MTMM-103-10-T-D-355 and TE 2314820-6 Both can be sourced from DigiKey. These were the best I could find before Paul offered a kit.

I have multiple Teensy in an industrial environment, each inside an enclosure powered by 24V stepped down to 5V using Mean Well DDR-15G-5. They have worked well for me about 4 years now, and they have built in protections which may be helpful for you. It may be worth trying them out, they are...

Is this a new Teensy? Is anything wired up or was wired up to it? Also, the black foam it comes with is conductive, I would recommend taking that off if the Teensy is powered on with it attached. Not sure if that could cause this but it is something to note.

The blink code you displayed in the video is showing a problem with the bootloader chip, it means it can not communicate with the main Teensy chip. You will not be able to program the Teensy over USB, or use the button to put it in programming mode if this is the case. I don't believe the USB...

I believe this is the blink code you are experiencing. 2 blinks, 0.6 seconds apart, 2 second pause. Which is "NXP JTAG Not Responding". It is possible there is an issue with the GD32 bootloader chip (small chip next to red led) which is not allowing it to communicate with the IMXRT chip, this...

I have not shared the files for this version yet. I intend to share everything once I feel it is at a point where someone can easily install it, hopefully that will be very soon. I will also look into reusing the bootloader now that I know it should not be an issue. The 6pin chip is an ATTINY10...

Sorry if my previous experience caused me to provide incorrect information. I was still working with the MKL02 at the time but I had not experienced the blink codes until then, I was under the impression that the software changed in some way that cutting the JTAG connections may affect the power...

Looking at eeprom.c this is the line that generates that error message. https://github.com/PaulStoffregen/cores/blob/3c442f9c67ee785ddad921ff5d0a3ebe5a9682ca/teensy4/eeprom.c#L53 Looks like you want to set it to 3824. 3824 would be the max address, 0 is the starting address, the size of the...

Right, the button shorts (to GND) the trace that the program pin is connected to, so pressing the button and shorting the program pin to GND do the same thing. A quick press will put the Teensy into programming mode which will also stop your program but not erase it, so you will want to avoid...

No worries, I would hope it was just a strange accident that it was pressed between 13-17 seconds and not that something shorted the program pin for that amount of time.

The Teensy has a LED Blink restore feature if you hold the program button down between 13 and 17 seconds. Is there a chance that this happened? It would also happen if the program pin was pulled low for this time window. See here https://www.pjrc.com/store/teensy41.html See the section below

Done. I have also added some information which I hope will be helpful.

I have been using this library ever since our last message and everything has been pretty smooth so far. I did find one issue today when testing client reconnection, if you unplug and plug back in the ethernet cable about 7 times in a row you can no longer connect a client to a TCP server. I am...

Thanks for the tip. I was not aware of this software, it works great!

I do something similar with a device that communicates over RS485. In my case the device has a model which has ethernet but we only have the RS485 model, I was able to use their software and connect to the Teensy over ethernet and transfer the data between the Teensy and the RS485 device. I just...

Will I have a similar issue (delay) when I read the response or is it handled differently than writing? I will be sure to let you know how it goes.

Okay so what I am seeing is by design, just call flush whenever data is time sensitive and if not, I can let the library buffer and send the data when the timer hits to be more efficient? I will try using flush and make sure everything is working properly. The largest amount of data I may send...

I tried making the switch over to QNEthernet this week but I had a few issues/questions. First issue I noticed was that the data that I was sending from the Teensy to the PC wasn't being received fast enough, I did confirm it was being received but it was coming in rather slow. My application...

Great! After playing around with it I am able to read the program on the flash simply by reading a variable pointed to the flash address, I thought I would need a special function to read from the flash.. does the cpu abstract reading the flash in the background or cache it or something? Is this...

Thanks for the clarification and all your work on this, this should work perfectly for my needs I just need to send the file over ethernet. Assuming I verify the program with either a CRC or sending back each line, is this sufficient to ensure the program is correct? Is there a way to verify the...

No worries, in my case I am not using LittleFS, I just wanted to use the flash space between the program and EEPROM for buffering the new program. With the default offsets I was having the issues described above. Everything works great as long as the space is empty and I use the mentioned flash...

I came across the same issue as @ipaq3115 when testing this, I also use the EEPROM in my program and when trying to flash I get "buffer = 0K FLASH (601FC000 - 601FC000)". I decided to use a ram buffer instead and modified flash_move to also erase the flash when using a ram buffer so that next...

I have an application where I am communicating between a teensy and PC, I was originally connecting a Teensy 4 to the PC using an RS-485 bus in anticipation of a long distance run but have since switched to using Teensy 4.1 with Ethernet (TCP) or USB Serial. With my original design I used CRC to...

Nice work! Glad to see someone else take on the challenge, it sure is satisfying when you get it working. My setup is VSCode issuing commands to Arduino_debug.exe to build and JLink.exe to upload. Just a warning for anyone attempting this. I'm not sure if the new bootloader firmware has made...

You should be able to establish a J-Tag connection as long as you connect everything between the Teensy and the MKL02 except TDO, TCK, TMS, TDI. Pins 6, 8, 5, 7 respectively and connect those along with a ground and vref to your debugger. The MKL02 can not be connected to the J-TAG pins at the...

Paul sells 3x2 pins and sockets and they work great for custom boards. No clearance issues on my end. I just used this footprint in KiCad https://github.com/XenGi/teensy.pretty You can see an example on the store here. https://www.pjrc.com/store/header_socket_3x2.html As for the interference...

Nice to see someone else giving this a shot. I have come a long way since my last post, I will share here shortly. One of the issues I had was that the pads were so close together there wasn't much room for the holes and copper. I was able to get it to work once but later attempts caused the...

Arduino CLI 0.19.0 was just released with support for pluggable discovery. This is good news, I assume Arduino CLI and Arduino IDE 2.0 Beta are finally ready for Teensy support. https://blog.arduino.cc/2021/09/02/the-new-arduino-cli-0-19-0-is-out-and-better-than-ever/

That is a problem. Pin 10 should be pulled high by the MKL02. If this is LOW, I believe pin 9 will also be low which is your power on reset. This means the processor is being held in reset and it will not run your program. You mentioned you added in a button, could there be a short on this pin...

Are you powering it with a LiPo? I remember reading that the ESC has regenerative braking and it could damage a power supply so you had to use a LiPo to power it. If so disregard, I just remember reading the warning.

You could try his code before going ahead and buying one although he explains how he only could get it to work with a KISS ESC, not sure the reason. It should work on either of your Teensy versions, I would follow the pins on the teensyshot GitHub or his guide. Here is what he said, I wonder if...

Are you using a KISS ESC? If so, Give this a shot. https://sbasami-tech.hatenablog.com/entry/2020/08/23/095106 Specifically this ino. https://gist.github.com/sbasami/06c419e61e01a2bc9e5d60622069f288 He used a teensy 4.1 but I would assume a 3.5 should work if you wire to pins 22 and 0 instead...

Did you try pin 4? It looks like ESC 1 should be on pin 4 according to the readme on github. Sorry for the simple question, I will try and look deeper into it tomorrow. Which version Teensy are you using? It's possible the simple library is written for a different Teensy. Also it looks like...

How far did you get with attempting to use the teensyshot library? At first glance it looks as if once you load the program on to the Teensy you need to write a program on the pc which sends data to the Teensy over usb serial at 115200 baud with this struct // Host->teensy communication data...

This may do what you need but it is $199. https://www.pemicro.com/products/product_viewDetails.cfm?product_id=15320138&productTab=1 Only other thing I could find is this article. https://mcuoneclipse.com/2017/05/06/using-eclipse-to-program-binary-files-to-an-embedded-target/ Is this for a...

It's normal. If you do not have a cable connected it will hang forever. You can see it on line 293. I believe it was left that way to be consistent with the original Ethernet library but you can comment it out which is the solution I used in my project...

First thing I found was this. Not sure if this is related but it's worth a shot either disabling the timer before calling parsePacket then re-enabling it. Alternatively call noInterrupts() and interrupts() around it just to see if it makes a difference...

You can usually put multiple slaves on one SPI bus and the CS pin will tell the slaves when they are being communicated with. I believe you should be able to get rid of one of your spi lines and set both slaves up on spi0 with two CS pins to cut down some of your wiring and pin usage. By daisy...

You could use IntervalTimer if you plan to run these at a fixed interval. This is what I have used to acquire data from SPI and pass data to the main loop. https://www.pjrc.com/teensy/td_timing_IntervalTimer.html Also check out TeensyThreads. If you don't already have it installed you can do so...

No problem, hopefully that's the issue. I'm not even sure if UDP_TX_PACKET_MAX_SIZE does anything inside of the library, I quickly searched for it but I didn't get any hits. I would assume it's just a standard way of declaring the buffer array size and using it across your program in that case...

I noticed you are running outside of the leds array, the length is 14 and you are accessing up to packetSize which is 24,24,27. It could be causing your problem. The garbage data in your third acknowledge message may be from your code overwriting the null character at the end of your char array...

I have a project in which I am powering a Teensy 4.0 with 5V directly from a power supply and I have the trace cut so I can still use the USB for acquiring data over serial. I noticed recently that when I programmed or unplugged + plugged in the USB I would get a message in Windows stating "USB...

I will probably upload the files and/or post it on OSHPark. It requires hot air, good soldering skills and flux. I would love if they did this. I feel as if they are waiting until they make the switch from Arduino IDE to bother with debug capability. Sorry, I am not sure on this one. I don't...

I have been working on a Teensy 4.1 debugger mod for a month or so now and I figured it was in a good place to share my progress. This project started by de-soldering the MKL02 chip, soldering magnet wire onto each pin of the MKL02 and the Teensy to break them out to 16 pin headers on a...

That's great Paul! I will be sure to use these for my board. Is there a recommended footprint for the header? I'm sure I could use a similar part's footprint and it would be fine but just to be safe. 0.7mm drill / 1.1mm pad?

No problem. Hope it is really as easy as swapping out a part rather than needing another pcb manufactured. I have been fine so far with user libraries, but it is always good to double check them for sure. Have fun with your project.

Thanks for the suggestion, this is what I am after for sure. I have not gotten around to making the next revision of my board yet but I will definitely consider these. Since I have posted this I found a few candidates as well. Samtec MTMM-103-10-T-D-355 and TE 2314820-6

Looking at the J0011D01BNL datasheet, it looks like the pinout is different between the J0011 and the J1B1211CCD that PJRC uses? Here is the J0011 and J1B1211CCD Cable side is the same but PCB side looks different to me. The J0012 looks like it matches.