Search results

I have received different boards from the supplier MichaelMeissner mentioned earlier on this thread (https://www.tindie.com/products/loglow/teensy-3536-breakout-revision-a-dip-64/). I can confirm they have superb quality and usability. Those break-away power bars and socket kit were exactly what...

That was my understanding as well, that is why I pointed out that schematics is identical. Taking it as starting point OP can experiment with pullups and mosfets to get required switching time. Of course one channel IC with acceptable characteristics and no external parts would suit him even better.

I might be missing something but the schematics of Pololu level shifter is identical to Sparkfun one.

Another option is mosfet-based circuit like this: https://www.sparkfun.com/products/12009. Don't know about "recommended" but it is widely used one. Also, depending on input impedance and voltage levels of your target you might be able to use cmos output as is. I would add resistor in series...

Looks like OP and Paul agreed on the conclusion of this thread. That's good, but before we part I'd like to propose a little experiment. Just ask yourself these three simple questions: 1. How many projects have you done with Teensy where there was absolutely no way to fit anything bigger...

I thought the whole point of the OP idea was to have ONE form factor covering most of the use cases. And the best part of it was that it did not even require any alternative routing.

that is not a problem at all. You have 3 options here: 1. If you do not need servo connections you do not solder in those pins. As simple as that. 2. If you want servo connections AND breadboard you can use readily available long pins that will stick out down and up at the same time for signal...

If all MCU pins are routed to Teensy pins then you'll be hard pressed to find a case where multiplexing like that is necessary. And that is exactly the reason for OP suggestion. And yes, in most cases it eliminates the need in addon boards, breakout boards and such. In rare cases where...

This is exactly the kind of controller layout I had in mind when I posted on the carrier board thread. The logic is simple - there are two typical uses for controllers: breadbording/prototyping and final product. For the former having access to all the pins is essential and far outweighs the...

I might be missing something obvious here, but from all I see I got the impression that you are trying to GUESS actual servo position: if (servoActualPosition < servoTargetPosition) { servoActualPosition = servoActualPosition + 1; } else { servoActualPosition = servoActualPosition - 1...

Just to clarify previous post: It is not a good idea to use 5V I2C bus with 3.3V master device, even if master has 5V tolerant pins. It might work, but you can also fry it in the long run. What you can do depends entirely on the specific slave device you are trying to control. 1. If device has...

I am still puzzled by this and similar statements in earlier posts. What do you mean when you talk about "adding larger resistor"? No matter how large resistor is, adding it in parallel will REDUCE total resistance even further. Anyway, the datasheet for HT16K33 states VIH on SDA/SCL as...

Wait a second, this wasn't clear in the original post. So you have pull-ups in the shifter AND in the device it is connected to? 10K + 2.2K in parallel? Then the only option you have is to remove 2.2K off the board. ADDING any more resistors will REDUCE the total even more. And you cannot drop...

In all my searches on I2C I would eventually land at TI document written long time ago which gives formulas for allowed resistor range. Unfortunately it uses line capacitance that is not easy to predict or calculate. Here is one of the incarnations of that document...

I oversimplified a little, of course. Yes, some code to initiate programming condition either on reset or, for example, on interrupt from one of no longer used jtag pins. So, you are right, it is not THAT simple. But I am not talking about writing my own bootloader, I do not have required skills...

Wow, I am obviously out of my comfort zone here. I did not know that you can run code from RAM, for example. That of course would allow user code to occupy entire flash. But is "NON-Teensy" approach really that different, code-wise? I would say it is only a matter of accessible address range -...

This idea came to my mind right after I made a post. It is my understanding that MKL02 checks MK20 upon power up and uploads bootloader code if it is missing. Therefore it should be possible to separate the two and use this add-on to program MK20. What I do not know is if the code loaded into...

Facing similar problem I wrote a library with several filters that could be daisy-chained and tried them in various combinations and with different settings. In the end I'd given up on low-pass filter because of unavoidable propagation delay (it is still useful for slow paced processes though)...

Is there a detailed description of the bootloader functionality somewhere? I found bits and pieces in several threads but they provided more questions than answers. I am not asking for bootloader code, of course, just general information on how it all works together step by step. Here is my...

Thanks for the explanations, Paul. I totally forgot about that additional possibility for current path - from 5V rail through upper mosfet to 3.3V rail. So, not only lower mosfet can be fried by attempting to drive 5V low, but the whole controller can be fried by 1.7 over-voltage on power rail...

Hi Paul, Thanks for prompt reply. Since I am not building any fancy circuits I think there is no point in a new thread. I am simply connecting controller to off-the-shelf external devices, like servos, serial adapters etc. Ground to ground, output to input. So this is straightforward question of...

My apologies for digging up this old thread but I really need to understand this before committing to new hardware and abandoning a lot of code accumulated over the years. I've been using ATmega extensively and without problems for quite a long time. I was excited to get more power and...

Let me add another 2 cents to the whole lot of good (and sometimes contradictory) suggestions here. There was a suggestion to add pads for i2c pull-ups in the beginning of the thread. I second that wholeheartedly. Actually since not everybody is good with iron I'd rather see pull-ups already in...

Hi Frank, Your board is nifty but as I mentioned before, I do not work with hardware directly, I am writing software for it. The guys I am doing it for do not bother with soldering, they are focused on mechanical part of things. The controller for them is just something they stuff into a box...

I asked for 21 because breakout board adds 20. Hmm... actually 14 might be OK, it covers 12 pads and reset. So only 2x7 extra holes, 5.1 mm extra length. Even better! Oh, and I am removing a request for on-board CAN transceiver. They vary a lot depending on the environment and industrial use...

Yes, that is exactly what I had in mind, Michael. Except with 21 holes (14 do not cover all necessary connections) and without turning neat teensy board into another Frankenstein's monster as all these breakouts do. I have to admit that I am looking at this from the position of a user...

After some thinking, I'd like to clarify my suggestion for making full pinout teensy. To keep in line with the goal of having tiny board, I think the best option is to: stretch the board just enough to accommodate 3 more rows of 7 holes on a side opposite from USB. That's 21 more pins with only...

In my experience most of the uses for micro-controller boards like teensy fall into two primary categories. First, breadboarding various experiments, trying new things and developing software. For this current teensy format is OK, although the popularity of breakout boards certainly tells one...