K66 Beta Test

Status
Not open for further replies.
TelephoneBill said:
I have not used an SD Card before with Teensy (or any other MCU). Where would be a good place to start learning - the Arduino IDE has some info - is this directly applicable to T3.6 Beta?

If someone could point me at a (relevant to T3.6) simple example, that would be most helpful. I found this - https://www.arduino.cc/en/Tutorial/Datalogger - but not sure if it would work directly with T3.6 ???
Click to expand...

Bought a cheap 16 MB SDHC Sandisk Class 4. Running Win7 and 1.6.11/1.3Beta3. Formatted card as FAT32 with SDFormatter - Card inserted. Using SdFat Library.

Have compiled "Tutorial/DataLogger" successfully and downloaded OK. Serial reports ""Initializing SD card..." then "Card failed, or not present".

Good so far... code is working with the SdFat library.

I can't locate a schematic, so unsure if any additional external wiring is required for T3.6 in order to get an SPI interface. Is this SD card socket same as the older shield and should I wire pins at either side same as the shield? Or is there pre-wiring on the pcb that does this for me?

Appreciate this is a noob query and other important things happening at this time. Only referring it here because "...here be all things T3.6 till advised otherwise" :)
 
TelephoneBill said:
I can't locate a schematic, so unsure if any additional external wiring is required for T3.6 in order to get an SPI interface. Is this SD card socket same as the older shield and should I wire pins at either side same as the shield? Or is there pre-wiring on the pcb that does this for me?

Appreciate this is a noob query and other important things happening at this time. Only referring it here because "...here be all things T3.6 till advised otherwise" :)
Click to expand...
For K66 uSD (no SPI, native SDIO), you need to use the following https://github.com/WMXZ-EU/uSDFS
 
Paul - Robin : I created A thread :: https://forum.pjrc.com/threads/36567-K64-Beta-Test-Teensy-3-5?p=113821#post113821

Can you elevate and move that to ANNOUCEMENTS ?

I just got home and found a BETA Teensy 3.5 in my mailbox - delivered 12 minutes earlier - I'm excited to see what Frank is up to.

Powered and BLINKING - and looks like this to TYQT on WINDOWS 10::
TYQT OUT OF BOX.PNG
 
Last edited:
manitou said:
For K66 uSD (no SPI, native SDIO), you need to use the following https://github.com/WMXZ-EU/uSDFS
Click to expand...

Thanks Manitou. If I interpret your comment correctly, then the pcb is prewired from SD socket to K66 BGA chip with an SD Host Controller (SDHC) interface (aka SDIO). This means that - for now - the only way is to use the WMXZ-EU/uSDFS library to communicate with the SD Card. I noted that there is an AP NOTE (http://www.nxp.com/files/32bit/doc/app_note/AN2906.pdf) which shows in Table 1 that this is likely to be a 9 pin interface with 4 data lines, CMD, CLK and VDD and two VSS.

I presume that SD High Capacity (SDHC) cards will still be compatible (???) and not need specific SDIO cards.

Thanks also to WMXZ - it may be easier for a noob like me to wait for Bill Greiman's FAT. Making another presumption, this upgrade will then make the T3.6 compatible with former sketches such as DataLogger (???) et al.

Appreciate any info you get on progress. I'd like to use data logging for my own projects to see how they perform over time.
 
DaQue said:
I can I just wondered if the library had a format command. Also I have been reading PCs often format SD cards in a way Arduino doesn't like.
https://forum.arduino.cc/index.php?topic=228201.0
Click to expand...

ChaN's FS has a command 'f_mkfs', which seens to create a filesystem, (I'm not sure, I did no Unix programming in the last 10 years)
but as I said PC formatting is fine, or you can get the official formatting program from the SD association https://www.sdcard.org/downloads/formatter_4
 
TelephoneBill said:
Thanks Manitou. If I interpret your comment correctly, then the pcb is prewired from SD socket to K66 BGA chip with an SD Host Controller (SDHC) interface (aka SDIO). This means that - for now - the only way is to use the WMXZ-EU/uSDFS library to communicate with the SD Card. I noted that there is an AP NOTE (http://www.nxp.com/files/32bit/doc/app_note/AN2906.pdf) which shows in Table 1 that this is likely to be a 9 pin interface with 4 data lines, CMD, CLK and VDD and two VSS.
Click to expand...

The short answer is "yes", but there has been much discussion of pins to the microSD in this thread. The pins to the microSD can be configured either as SPI or SDHC, so in theory, you could access the SD card with SPI, but the teensy core doesn't configure those pins as SPI (other posts have shown how that might be done).
 
Oh, i completely missed that info.
This means someone could just edit the std sd - lib to use the SD-Slot with SPI ?
I'm could do that.. at least, we'd had a compatible way to use the inbuilt slot, then. preliminary .
 
Last edited:
Paul / Kurt :: there was a question of Serial6 and the LPUART baud rate usage - I got good results in this thread on 7/26 with K66 Proto board::

regarding K66 and LPUART baud rates - I found that UART to work as well at higher speeds as the others in the range I tested. Preceding post 905 has sketch where I cycled through various rates - 8Mbaud worked at high clock speed - then I dropped to max of 4Mbaud until 96 MHz require 2Mbaud.

See HERE >> K66-Beta-Test?

I can retest with K66 and K64 and repost sketch after I solder K64 headers and see KurtE's confirmation it should be working.
 
manitou said:
I did digital IO check of beta3-breadboard to breadboard jumpers, and voltages were all OK, so I'm going with "breadboard/jumpers not so good at 50mhz" since defragster had success with female headers + shield on beta3. I actually get the PHY regs to read every so often, and occasionally see the shield LEDs flicker.

EDIT: as a test, i used jumpers from the K66 proto female headers to a breadboard with the ether shield. That also failed.
Click to expand...

With female headers on K64 beta, ethernet shield worked just fine. :D
 
Manitou - Of course it did ... errr ... good to hear :). I got my headers on and didn't get back to it tonight. I had a bit of diagnosing TYQT that doesn't know the magic name for handshake with the T_3.5 so I hopefully got details Koromix needs to clear that up and then I can enjoy using it rather than having it confuse the T_3.5 for a T_3.6.

Glad you got the headers on the K64, it is a close fit. Will ok on the K64 thread for any updates with your next trial - maybe I'll get to something before you.
 
Here a draft of the latest pinout card. Hopefully I got all the pins right this time?

card9a_rev1.jpg

I should explain a sort of double standard regarding display of alternate pin functions. For communication signals, alternates are shown. But for PWM and SPI chip selects, alternate locations are not shown on the pinout card. For example, pin 25 is PTA5 & FTM0_CH2, but it's not shown as PWM because we use pin 9 for that FTM0_CH2 signal.
 
Hi Paul,

I will take a look, Personally I wish the card could show all of the alternate SPI CS pins, or at least have some easy to find location that does. Unless you are someone like me, who goes and looks at the code, about the only place that I remember that sort-of documents it for T3.2 is the ILI9341 display page that says, you can use these pins but not these... But I also understand there is only so much room and a potential for too much information.

These days I go to my Excel document or Michael's documents.
 
This is probably more along the lines of a web dev sort of thing but it would be amazing to have an interactive pin out diagram for the teensys. One that could display the whole functionality for a pin or you do something like "highlight SPI1" and all the pins related to SPI1 are highlighted and everything else dulls out. That would be super sweet for visualising the pinout.
 
KurtE said:
Personally I wish the card could show all of the alternate SPI CS pins
Click to expand...

The original Teensy 3.0 card did this. The duplicated pins became terribly confusing when people tried to use multiple libraries like Ethernet and ILI9431_t3 which use the hardware CS feature.

JWScotSat said:
T... an interactive pin out diagram for the teensys. One that could display the whole functionality for a pin or you do something like "highlight SPI1" and all the pins related to SPI1 are highlighted and everything else dulls out. That would be super sweet for visualising the pinout.
Click to expand...

That would be mighty sweet. :)

Maybe it could also have a couple documentation panels that auto-update with details for the selected pin and info about the peripheral with links to examples or libraries?

Maybe it could even allow you to somehow choose how you'll use the pin and adjust what it does with the others. Maybe you somehow say you're choosing to use pin 5 at TX1. Then it could disable or hide the other TX1 options, maybe change how other pins display as appropriate?

Anyone particularly good with Javascript and toolkits like jQuery & D3 want to take this on?
 
That would be mighty sweet. :)

Maybe it could also have a couple documentation panels that auto-update with details for the selected pin and info about the peripheral with links to examples or libraries?

Maybe it could even allow you to somehow choose how you'll use the pin and adjust what it does with the others. Maybe you somehow say you're choosing to use pin 5 at TX1. Then it could disable or hide the other TX1 options, maybe change how other pins display as appropriate?

Anyone particularly good with Javascript and toolkits like jQuery & D3 want to take this on?
Click to expand...

That's exactly the kind of thing i was thinking. Probably really useful for folks new to teensy to see that when you use certain functionalities it can have knock-on effects.
 
PaulStoffregen said:
The original Teensy 3.0 card did this. The duplicated pins became terribly confusing when people tried to use multiple libraries like Ethernet and ILI9431_t3 which use the hardware CS feature.
Click to expand...
I totally hear you. For me, what I do is not just mark it as CS but also which channel: So for example:
Pin 2 could be marked as CS-0 So is pin 10 and pin 26 - And you have to know that if your program uses Hardware SPI CS pins, it can only use one of the ones that are on the same channel...

As mentioned would be great to have interactive pin diagram and of course we can put lots more details like this up in a WIKI later on.
 
Status
Not open for further replies.
Back
Top