Search results

Obviously it will be larger since xxprintf() has lots of formatting capabilities whereas the Arduino Print class has very limited formatting capabilities. But back to the issue that Paul brought up, it is highly annoying that the printf() format checking routines are not smart enough to treat...

Nice. I'm obviously behind on my C standards...

Tried what? Compared to what? using PRIu32 vs using the a hard coded format type changing memory usage doesn't make sense to me. What exactly were you comparing. Can you show the two sketches? --- bill

bummer. I just did some testing on linux and it has become a bit difficult to create portable printf format strings. We now have good portable types in <stdint.h> and now there are some portable printf format helper types/macros in <inttypes.h> but they are clunky. Then there are somewhat...

It is possible to get gcc to sanity check that the arguments handed to the Print class printf() functions match the format string. All you have to do is add a format attribute to their declarations in Print.h I created a github issue for this: https://github.com/PaulStoffregen/cores/issues/485...

Paul, Could you do an update to the teensy product page here: https://www.pjrc.com/teensy/ The products listed don't match the products in the table below them. It would be nice to update the table with the current products. Thanks --- bill

Paul, I'm curious as to how you intend to handle the IDE 1.6.10 AVR PIN_A0 to PIN_A7 names that collide with existing Teensy++ defines. There is no way to fully resolve this to support both the new 1.6.10 IDE analog pin defines and and be fully backward compatible with Teensy PORTA pin defines...

Paul, Have the board names, board defines, and MCU defines been finalized? I saw in post #48 that you were still undecided. Have you finalized on: "Teensy 3.4", TEENSY34, __MK64FX512__ "Teensy 3.5", TEENSY35, __MK66FX1M0__ I need to know these to complete the openGLCD code updates and...

While I agree that the systems capable of running 64bit native integers should be using 64 bit time_t values, using 32 bit time_t values (the 2038 problem) isn't always as big of a deal as you might think While the 2038 problem is a much bigger deal than the Y2K issue that scared so many people...

Ok, so what issue are you having with openGLCD? I'm doing some updates to make it better, but the latest openGLCD release without these updates works "as is" for me. --- bill

You can buy a USB logic analyzer starting at under $10 USD that can easily handle multiple i2c buses. And then use some free open source s/w (sigrok) on it that decodes all the signals, so it isn't a big investment in terms of $ You really need test tools like this to play at this level. But...

Guys, i2c debugging typically involves looking at the i2c signals with a logic analyzer, to look for signal issues and see the state of signals when the s/w starts to have issues. With an analyzer tracing on all the busses as once, you could see things were happing on the wrong bus, or if SCK...

From that description, I would say that the code is wrong and should be corrected/changed. setClock() should set the raw i2c SCL clock rate on the bus. All the specs in datasheeets for i2c bit rates are based on a maximum SCL clock bit rate not a desired/theoretical/measured actual data rate of...

nox771, It is hard to tell from that table how the requested bit rate maps to an actual SCL bit rate. I'm assuming that the table above is a bit backwards. In other words, the "Actual Rate" column is showing the SCL rate that would need to be requested/set to get the data bit rate in the first...

Good News. I just did a test with openGLCD. Since the board is not recognized, opgnGLCD drops into a "corecode" mode which is supposed to work on any board. And it worked "out of the box" on the K66 board using TeensDuino 1.29-beta3 and the Teensy 3.5 board. It passed full diags (writes and...

Empty Post Empty Post

Can't you already do that today? i.e. create a self extracting executable image that runs the uploader tool? Even include a command line up-loader tool executable and any libusb share libraries so that the user doesn't have to have any s/w installed. --- bill

Paul, There have been many of what I would call unscrupulous actions over the decades that people seem to overlook or have forgotten. Ironically, there are even a few things that many people might call "good" or even "great" things that originated from some of these unscrupulous actions...

"Win" what? I'm not so sure on the outcome. I'm guessing it will be a mixed bag given how sloppily things were handled. Particularly given the "handshake" agreements that were in effect, the multiple jurisdictions involved, the sloppiness of how and when the trademarks were filed vs when they...

Seems pretty silly to try to start a new branding name push without making sure that whatever name you picked had domains available that you could own. I'd want to own at least .com, and .org of my brand name.

What causes this? I'm seeing this warning for my openGLD which I have cloned into my sketchbook/libraries directory for development. I have many other libraries that are git cloned into the sketchbook/libraries area which all have .git directories and they are not getting the warning. I'm using...

Even on the AVR, while it may "work" with the internal pullups for certain device configurations, it is out of spec and doesn't always work. The internal pullups are simply too weak. Consider yourself lucky if it works for your situation without the external pullups. --- bill

Starting in IDE 1.5.5 and then backported to the 1.0.6 release, LED_BUILTIN was changed from being a const int to #define While the difference will make no difference to most code, any code that is using LED_BUILTIN as conditional will break with the teensy defintion. I happen to stumble into...

Well, that explains a lot. So from its very origin. Arduino was not a business. And that is its problem. No business can survive if it gives away all it is IP and then gives free support to any competitor that takes that IP and builds competing products.

While I may sound harsh, I think we are seeing the beginning of the wind down to eventual death of Arduino. (At least the fully open model with support by Arduino LLC) Many factors are all combining to create a perfect storm. I still believe that most of this driven from the fact that you can't...

BlueScreen? Huh? we aren't talking about Windows or anything running on a PC host. We are talking about code running on an AVR. The AVR Print class code has a bug. I posted a small sample sketch which demonstrates the bug which is that the output generated will not be what it is supposed to be...

Work arounds are easy and sure printf() is better, and also WAY better, IMO, than the goofy streaming stuff since you can do real formatting but I ran into this bug when using an example using sketch in library code I didn't write and when things went wonky I tracked it down to a Print class...

That is because Teensy 3.1 is an ARM processor and not an AVR. Like I said this is a bug in the Print class in the teensy AVR core code. The Print class Teensy AVR code is different from the IDE supplied AVR code and is different from the Teensy ARM code. --- bill

Paul, The Teensy AVR print class has a bug in the printNumberHex(unsigned long) function. This shows up when you print uint32_t variables. If you print a number that is 8 hex digits, you won't get the proper output and it also looks like there is a buffer/stack overflow as well. Anyway, it looks...

Yeah the issue seems to be that Teensy shows up as multiple devices and switches back and forth. In the past I had success by adding USB filters to the VM for the USB device (vendor, device id etc..) and enabling them.. That way the USB device is automatically handed to the guest when it showed...

The silk screen on the bottom of my PCB for that pin says "17-5V"

capitalism can cruel. That said, it isn't necessarily a fair fight. The issue over logos and trademarks, product names is a big and important issue that needs to be resolved. Unfortunately, from what I can tell it isn't so cut and dry given the sloppiness of how the "business" was run early on...

1.21-b12 seems to work ok with the openGLCD 1.0rc2 library included. Tested on Teensy 2++, 3.0 and LC. I didn't realize that the Teensy installed libraries were installed in the teensy vendor area vs the user sketchbook. Makes sense, but bummer is that no other non teensy boards can use the...

I installed 1.6.1 from the zip image on a fresh install of Windows 10 tech preview. When I ran the 1.21b10 installer, it installed the serial drivers. When I navigated over to the 1.6.1 directory, it reported a list of matching things it was looking for and then it reported a missing 1.6.1...

So here is another oddity with 1.21b10 The IDE appears to be scanning the user sketchbook libraries more times than it used to. When I change boards and the target is a teensy board, the IDE scans the user sketchbook "libraries" directory 4 times. When the target is say an "uno" it only scans...

Paul, the releases are coming out so fast it is hard to do much testing on them. I did find an issue in the bet10 just released. Not sure if it is specific to an OS environment, but I'm using Linux Mint 13, Mate 32 bit. When installing and you get to the section where you can select which...

Ok, so I trapped the bad read. The data on the pins was correct when everything was stopped. The highs were 4.88 volts and the lows were 0 on both sides of the resistors. I'm definitely beyond the digital world. The code normally tells the LCD to drive the data bus then goes to read it around...

I know about the level converter, which is why I'd like to see a schematic to see what type of load it puts on the ARM pin. I've increased h/w timing delays to the millisecond range with no changes so I don't think there is any sort of slew rate issue for the signal nor any type of realtime...

ok, tracking my 5v pin read/write issue down a bit more. writes to the GLCD are working as expected. The issue is occasionally pin reads don't read the expected level correctly. It isn't random and is very repeatable which is actually great. It appears that the pin read issues track back to two...

Just getting ready to look at the datasheet for the LC. To stop the guessing, pullups are not needed. The LCD drives the data signal lines both ways (+5/GND) when the data lines are outputs. (technically it isn't 5v but the voltage on the USB since everything is powered from USB so it is a tad...

The 5v signal is from a ks0108 GLCD. Depending on what is happening the 8 GLCD data pins can be inputs or outputs. I hooked up the analyzer and my h/w delays are the same for both Teensy 3.0 vs Teensy LC. Typical delays are between 140ns and 500ns depending on the type of operation. (actual...

The issue only seems to happen when building with teensy boards. The errors will be "normal" when building for say UNO. --- bill

Something is different with the LC vs the 3. I tried using 10k series resistors instead of the level shifter and the LC doesn't seem to be a able to reliably read the 5v signal levels which ends up putting trash on the display. I don't believe it is a timing issue as the Teensy 3.0 works even...

Missing error information Just ran into a strange issue in the 1.21-beta6 on the 1.6 IDE There seems to be an issue with the error output when building for teensy boards. I see this when a #error is encountered. If I build for uno, I can see what I expect and the useful information like the...

Just as a followup, __thumb__ is defined when building for Teensy 3.0 and for Teensy LC so that define isn't the magic bullet. --- bill

One thing I still need to get resolved is can the LC 3v pin inputs tolerate a 5v output when fed through a 10k series resistor like the Teensy 3 could?

Great so using the __thumb__ define is definitely the way to go vs using a processor define. Thanks again. --- bill

So it looks like __thumb__ is the defined when using thumb16 where "subs" can't be used. Thanks. Another question, out of curiosity, is thumb16 a locked in mode for a given processor or is something that can change depending on how the code is compiled through command line or optimization...

Have some questions on pin i/o. Maybe this isn't the best thread for this, but I'll start off here. Currently openGLCD jumps through lots of hoops to try to do the fastest pin i/o as possible. On the AVR that drops down to direct port i/o and can even do multi bit nibbles or even byte i/o when...

WOW. That sucks. Seems like a tool bug to me, since the assembler and the disassembler don't agree on the mnemonics. I can't imagine the amount of time wasted spent trying to figure that one out. That fixed it. Is there a better define rather than using the processor define of __MKL26Z64__ to...