Search results

The following code seems to work roughly as expected (not exhaustively tested). Note the addition of the preprocessor directive "#define TEENSY_3_6_PRO" at the top of pins_teensy.c, enabling the extended IO definitions. core_pins.h /* Extended pin definitions for standalone MK66 projects...

Of course it refers to the array index! I can't believe I missed that. For now, I'm inclined to pad the array and maintain the established numbering. I will finish populating the rest of the new pin numbers and test. Perhaps someone would like to help with the new ADC channels and UARTs? Home...

More info: I have tested pins 72-74, and 95-99. All pins still freeze the processor. Current info below: core_pins.h (do NOT use my old posts, I found an error and cannot edit those posts) /* Extended pin definitions for standalone MK66 projects compatible with the Teensy 3.6 toolchain. *...

Haha, that would be correct! Thanks, Brian. I added the following after line 106 of pins_teensy.c (still just working with these three pins): {GPIO_BITBAND_PTR(CORE_PIN72_PORTREG, CORE_PIN72_BIT), &CORE_PIN72_CONFIG}, // new {GPIO_BITBAND_PTR(CORE_PIN73_PORTREG, CORE_PIN73_BIT)...

I'm finally getting back to this. I have hardware on hand that gives me access to the additional IO, and have started some basic testing. FYI, I have reworked my definitions to follow MichaelB's graphic, and am considering that the "official" standard for this project. Updated code below...

Michael, that's really smashing work! Thanks a lot! It will indeed come in handy. Good catch on the pin numbering, I tried to give a bit of buffer, but not enough, obviously. I will rework my pin definitions accordingly when I get to testing. I haven't made any progress on actual testing, as...

Thanks folks. I was aware that the SD bus pins are usable on standalones, but I copied from brtaylor's list above, and I haven't worked down to PTE0-4 yet. Would love for somebody to confirm or deny that PTA 7 and 8 are working before I continue. I will remove PTA6, thanks WMXZ.

Okay, this is VERY preliminary, and essentially untested. However, it DOES compile. :D I'm just hoping that this works the way it looks to, as I haven't spent as much time in the datasheet and libraries as most of you. This code belongs to Paul, so thanks again. You can refer to the extra pins...

Awesome! Glad you feel the same way.

Glad to hear it! I'd be curious to see what you have in mind, and how it differs from the current definitions. I'm flexible as to how we accomplish this, and I'm certainly open to hearing a better best-practice.

The purpose is the same as all open-sourcing: to save future developers time, effort, frustration, and to educate and lower the barrier to entry. If we can avoid it, why have a dozen people doing redundant work? That seems like a waste. I also hope that this may benefit PJRC (and all of us in...

My apologies for not being clear with my question. I wasn't referring again to adding pins to the public Teensy core. I'm not concerned with actually merging them, honestly! A special header file is fine with me. That question was to do with the numeric order of the *extra* pin definitions for...

That's my thought as well. For now, I expect to include an extra header file in my projects to add the remaining definitions.

Haha, indeed! The right tools make a world of difference, or in this case, 7".

For the record, the PJRC adapter board worked flawlessly. My jumper wires test fine, but apparently they are long/bad enough that the fast SPI bus does not like them. Word to the wise!

I appreciate the input all. Whether or not anything from this thread gets merged into the TD core is currently beyond the scope of this thread, and immaterial to me. I'd like to steer us back to the original topic, if that's alright with everyone. I wanted this thread to be a place to share and...

That is extraordinarily helpful, thanks! Can anyone think of a reason not to go numerically down the remaining pins? For example (I haven't double-checked these): new pin 58 on PTA6, new 59/A25 on PTA7, new 60/A26 on PTA8, etc.

If we want to have this merged into Teensyduino public releases, I think we'd better expect to require a special preprocessor definition for the extra pin numbers. Say, #define MK66_extended_pins or #define Teensy_3.6_Pro It doesn't even have to be included in the main documentation. As long...

That's a good suggestion. I did try different combinations of power and ground pins, but the red LED told me they were all working on the clone. Oh, well. I'm sure the adapter board will work out of the gate, and that will suffice for proof of concept, which is what I was really after.

Thanks Paul. You're some kind of customer support superhero. Like the Flash, but with microcontrollers. :D I guess my issue has to be with the length of the jumpers, so I'm ordering up your adapter for testing. Will update. Yes, my clone has the red LED as well. Handy for diagnosis on the...

I'm working on a Teensy 3.6 standalone application (with PJRC's MKL02) where I'll be using IO not currently defined in Teensyduino. I'm sure I'm not the only one, so I figured there might be others who would want to standardize an extended pin numbering scheme, or be willing to share what they...

This is strange. I got a genuine Wiz850IO in from Mouser today. Still nothing. Tried with different MAC. Nothing. For giggles, I tested all the relevant pins with an LED (Blink-type program), and no hardware problems. I tested my 3.6 with a known-good W5200 Seeed Arduino shield. Doesn't work...

Awesome, thanks Luni! I'll look into that.

Luni, thanks for linking that. It does look good. Can I assume that the code in that thread is current? Also, I think I follow the intended use of the TeensyHalfKayDriver class, but do you have code you could share where the process is demonstrated?

Thanks for looking at that. I should have mentioned that I tried pulsing reset in various configurations. Just gave it another shot to no avail. I guess I'm going to order one up from WizNet.

Thanks, Paul. Here's the specific wiring and some photos. This board is a generic clone as it turns out, but it does work with Mega. I confirmed that the compiler is using the library versions included with Teensyduino. The jumpers are roughly 6.5" long. There's two brown jumpers, because that...

I am testing a Teensy 3.6 with Wiz850IO board connected with jumpers via pins 10-13. When I run the WebClient_test example sketch below, the Teensy always prints "Ethernet shield was not found." The same adapter and sketch works fine on a Mega2560, pins 50-53. The adapter seems to be powered up...

Would this be easier on a standalone PCB with MK66 and MKL/Halfkay programmer on-board? I'd like to re-flash with a cheap processor, but if another 3.6 is the easiest way to do it, I'll go that direction.

Does the USB exit the bootloader, or reset the target device?

I'm interested as well. I hadn't planned to use a second Teensy, but I'm guessing a USB host is required to talk to the programmer?

Any thoughts on this? I was thinking about having an STM32, ESP, or 328 in the same box (something cheap and decently well-supported), hooked up to the Teensy and ready to burn updates through a simple web page.

A lot has been written on using Teensys as programmers for 8-bit Atmels. I'm wondering if someone could point me in the right direction as to how I could instead program a Teensy from another MCU. My goal is to be able to flash new firmware remotely using an on-site coprocessor. Hex files would...

Johan, This sounds like an XY problem. It's doubtful that you're anywhere close to running out of flash, so what you want could be done pretty easily with a few if() statements. Conditionals would be much easier than what you're proposing.

I'm also interested in this, as I was just about to start shopping RTOS options myself. Long-term support is what brought me to the Teensy platform.

Fantastic, thanks for answering my question! Yes, I'm excited about the much faster interface. Take care.

Paul, I'm grateful for the huge effort you must have expended to do all this work and testing. Thanks. Just to be clear, for those of us who want the latest updates and fullest feature-set, would you still recommend the Teensy Ethernet library across most of the Arduino compatible processors...

Very good! I'd glanced over your thread, but wasn't looking for something as complex as your initial aim. At $20-30 for a simple board, it would definitely be feasible for a lot of development projects. I'm under pressure to get started on mine, but if you or Paul print a breakout like that...

I personally would love to get some boards made on the Teensy design philosophy -- that break out ALL the IO. Right now, I'm developing a big project and looking at something like this for the simplicity of board design...