Stewieman01
Member
Ive designed and assembled my own teensy 4.1 with ethernet, and USB-C instead of micro. The Bootloader flashes the blink script to the memory and it executes properly which is the most success I've had in months, I'm ecstatic!
However my windows PC wont recognize the teensy and gives the 'error code 43, descriptor failed' in the USB serial list with no COM Ports available. I have tried on another windows PC but not success and i dont believe it to be the cable. I know how elusive this code 43 can be and have tried all the traditional ways of fixing it but with this being a custom job no success.
I've already checked the USB-C additions and can rule them out, the CC1 and CC2 resistors are correct and the layout as far as i know is correct. i based the layout and design off of this custom Teensy 4.1 design which the maker has confirmed it works.
when pressing the program button on the board the bootloaders LED blinks dim at a constant rate, which is it attempting serial communication to the PC which it doesn't receive. it wont get out of this program mode until i hard reset the board which just rewrites the blink code. To my understanding pin 6 (TDO) and 7 (TDI) on the bootloader are responsible for confirming USB connection to the PC.
I'm not fully versed in JTAG so i wanted to know, what should i see on these pins when probed? when the blink sketch is active OR attempting Communication they are at 1-10mV's, during hard reset flash to the memory TDO is at ~3.3V and TDI is ~2V. is this correct for a functioning design? i haven't got any official boards so i cant check them unfortunately.
My two suspicions for failure at this point is between:
1. the traces between USB Port and the mcu which followed differential pairing rules, but may not be appropriate.
2. communication between the MCU and the bootloader, i know flashing works so i believe the only pins not to rule out are pins 6 and 7 on the bootloader.
If some one could explain to me the bootloaders steps in communicating with the MCU and the PC when attempting to program this would help a lot in solving the issue, i am so close to having a fully working board, and I'm dying to test out the Ethernet design.
my Github link is here which contains all the files, the image is my board overview. the host USB is USB 1 and U3 is the bootloader. thankyou for any help as I've been struggling with this all week
However my windows PC wont recognize the teensy and gives the 'error code 43, descriptor failed' in the USB serial list with no COM Ports available. I have tried on another windows PC but not success and i dont believe it to be the cable. I know how elusive this code 43 can be and have tried all the traditional ways of fixing it but with this being a custom job no success.
I've already checked the USB-C additions and can rule them out, the CC1 and CC2 resistors are correct and the layout as far as i know is correct. i based the layout and design off of this custom Teensy 4.1 design which the maker has confirmed it works.
when pressing the program button on the board the bootloaders LED blinks dim at a constant rate, which is it attempting serial communication to the PC which it doesn't receive. it wont get out of this program mode until i hard reset the board which just rewrites the blink code. To my understanding pin 6 (TDO) and 7 (TDI) on the bootloader are responsible for confirming USB connection to the PC.
I'm not fully versed in JTAG so i wanted to know, what should i see on these pins when probed? when the blink sketch is active OR attempting Communication they are at 1-10mV's, during hard reset flash to the memory TDO is at ~3.3V and TDI is ~2V. is this correct for a functioning design? i haven't got any official boards so i cant check them unfortunately.
My two suspicions for failure at this point is between:
1. the traces between USB Port and the mcu which followed differential pairing rules, but may not be appropriate.
2. communication between the MCU and the bootloader, i know flashing works so i believe the only pins not to rule out are pins 6 and 7 on the bootloader.
If some one could explain to me the bootloaders steps in communicating with the MCU and the PC when attempting to program this would help a lot in solving the issue, i am so close to having a fully working board, and I'm dying to test out the Ethernet design.
my Github link is here which contains all the files, the image is my board overview. the host USB is USB 1 and U3 is the bootloader. thankyou for any help as I've been struggling with this all week