PaulStoffregen
Well-known member
Weird results with the audio-shield.
with my patched file (attached) I get different results every time i disconnect-and reconnect usb-cable. Output should be all 1s.
I'll look into this I2C issue.
Weird results with the audio-shield.
with my patched file (attached) I get different results every time i disconnect-and reconnect usb-cable. Output should be all 1s.
@Paul (and others) One thing I noticed with both this Beta 2 board as well as Beta 1 (at least in the adapter boards). If I have the something like a USB to Serial adapter plugged into lets say Serial4 connection (using CP2104 adapter). And then plug in the T4 into USB, the board is not detected by PC... Not sure if it booted or not, but no sounds showing Serial port plugged in... But if the adapter is not connected comes up fine.
My guess is it has to do with the voltage on the RX pin back feeding?
I've not seen this problem, and I have done a *lot* of testing with a FTDI TTL-232R-3V3 cable connected to Serial4. But I'm using Linux (Ubuntu 18.04.2 x86-64) and I have both the FTDI cable and the T4 plugged into a USB2 hub.
Maybe I need to get one of those CP2104 adaptors? Which one are you using? Any idea if this happens with all OS, or only Windows?
in Post #6 :: teensy_ports issues with 3+ boards, #1330, #1398,
That sounds like behavior I was seeing many weeks back? Where I had to have other Teensy's OFFLINE in order for the T4-1 so show up. Those posts suggest it failed to start … @KurtE put a blink to see if it is running to confirm similarity
Sounds good , hopefully enough pins will be accessible to test out SPI1Opps, I probably should have made one with all 10 pins for you. They were all done the same and soldering extra pins times 9 boards was time I didn't have.
I'll send you a package today with extra pogo pins and another bare PCB. Some assembly required. That's the most I can do at this moment. If you're still needing Serial6 & Serial7 hardware, ping me in a week or so and I'll get another board soldered up for you.
All I am doing is:The temperature calibration point fuse values are available in the OCOTP_ANA1 register.
uint32_t calibrationData = HW_OCOTP_ANA1;
@defragster
I will take a look but it seems to be reading about 15-20deg higher than what I am reading with my temp gun. Keep checking the code but the only thing I come down to is the calibration data that is set in one of the fuses. It seems to be reading it ok but...
Heres' the quote from the manual
All I am doing is:
I think that is all I need to read the fuse.Code:uint32_t calibrationData = HW_OCOTP_ANA1;
I've not seen this problem, and I have done a *lot* of testing with a FTDI TTL-232R-3V3 cable connected to Serial4. But I'm using Linux (Ubuntu 18.04.2 x86-64) and I have both the FTDI cable and the T4 plugged into a USB2 hub.
Maybe I need to get one of those CP2104 adaptors? Which one are you using? Any idea if this happens with all OS, or only Windows?
T4-2:: THERMO read at 800 MHz 41.4 CF_CPU MHz 600 Sec=10 CM#=53 [Max C=47.897198] AFTER :: °C=47.897198
F_CPU MHz 600 Sec=20 CM#=106 [Max C=48.551403] AFTER :: °C=48.551403
F_CPU MHz 600 Sec=30 CM#=159 [Max C=49.205608] AFTER :: °C=49.205608
// and 800 MHz
F_CPU MHz 804 Sec=30 CM#=194 [Max C=54.439251] AFTER :: °C=54.439251
25 sec Cooling Period ... °C=53.785046 After Cool :: °C=44.626167
F_CPU MHz 600 Sec=10 CM#=54 [Max C=56.043480] AFTER :: °C=56.043480
F_CPU MHz 600 Sec=20 CM#=107 [Max C=56.652172] AFTER :: °C=56.652172
F_CPU MHz 600 Sec=30 CM#=160 [Max C=56.652172] AFTER :: °C=56.652172
// and 800 MHz
F_CPU MHz 804 Sec=30 CM#=194 [Max C=62.130436] AFTER :: °C=62.130436
25 sec Cooling Period ... °C=60.913044 After Cool :: °C=53.000000
seems to be reading about 15-20deg higher than what I am reading with my temp gun.
I am using the Adafruit CP2104 adapter used for USB Host problems earlier)...
@defragster - I am pretty sure blinking LED won't work. When I plug it in, nothing happens. No debug output on Serial4, Serial port not created on Windows, and pressing program button does nothing
Pressing the power button for about 10-15 seconds appears to turn off power, pressing it again, appears to turn it back on, but still nothing else.
Windows 10, I think both are plugged into an USB3 hub
UART6 Serial1 [0/1] UART4 Serial2 [7/8]
UART2 Serial3 [15/14] UART3 Serial4 [16/17]
UART8 Serial5 [21/20] UART1 Serial6 [25/24]
UART7 Serial7 [28/29]
I can't seem to reproduce the I2C problem.
....
@defragster what should be updated? Serial8 is no longer valid as the two pins on bottom that had the Hart was replaced with the can pins.About to connect T4-2 Serial Updated Post #3
BETA2 T4 1062::
Code:UART6 Serial1 [0/1] UART4 Serial2 [7/8] UART2 Serial3 [15/14] UART3 Serial4 [16/17] UART8 Serial5 [21/20] UART1 Serial6 [25/24] UART7 Serial7 [28/29]
Found this Ref for 1062 mapping - post 1917
Based on Paul's post 1909
Not seen @KurtE's latest spreadsheet. If above post 1917 table is correct that needs to get back to Post 3.
@defragster what should be updated? Serial8 is no longer valid as the two pins on bottom that had the Hart was replaced with the can pins.
...
I'm still having SD problems with T4 beta1.
Solved:
Problem was caused by Kingston uSD. Used a SanDisk uSD and it worked fine on T4 beta1. For whatever reason, T3.2 could read the Kingston uSD just fine.
For whatever reason, T3.2 could read the Kingston uSD just fine.
How long were the wires? Was ground routed close to the clock?
How long were the wires? Was ground routed close to the clock?
I'm continuing to look into the audio problems. It's really starting to look like a signal quality issue. Turns out the 1052 chip on beta1 has the exact same problem as 1062 on beta2 when I replace the 5 mux chips with wires.
I soldered another board just now, using 33 ohm resistors in place of the mux chips. It's drying in the oven now, will test with it in ~15 min.
Edit: beta1 audio works with the 33 ohm resistors...
would a capacitor MCLK to ground not also filter the signal?Unfortunately this appears to be the only way to get the audio shield to work with the beta #2.