Search results

Please. Not another thread about the kids spitting the dummy.

https://en.cppreference.com/w/cpp/language/types.html By definition, short is at least 16 bits and long is at least 32 bits

I know you said you didn't want to add a DS3231, but have you considered one of these? https://www.microcrystal.com/en/products/real-time-clock-rtc-modules/rv-3028-c7 Accuracy is great for my purposes and it needs so little power that a supercapacitor will keep it alive and accurate for more...

Did you try loading the the "old" library and then "Migrate Libraries"?

If we assume that your include path in VS2022 is correct and you are actually including the correct SD.h, then the next thing to check would be what defines are present on the command line of the build. SD.h includes the following: #if defined(__MK64FX512__) || defined(__MK66FX1M0__) ||...

On my vivaldi browser I see the following Also expired. But I don't have *any* problems viewing the site.

Perhaps the bus isn't terminated properly (120 ohms at each end) if there's only one transceiver attached?

Thanks for that. I remember that the urban myth when I worked for a living was that it was not a coincidence that Windows NT was one character advanced from VMS :geek:

You might also consider using '/' as your path separators and let microsoft's appalling choice of separator just turn into a distant memory. As a bonus your code will also just work on linux filesystems without any problems. Edit: I consider MS's choice of '\' as a path separator to be...

Also see https://www.pjrc.com/teensy/eagle_lib.html

A million thanks. Working fine. (As soon as I remembered I needed to patch my linker script!)

Try https://github.com/XenGi/teensy.pretty

Hi shawn Thanks for doing the legwork for this. Unfortunately: Tool Manager: Installing git+https://github.com/ssilverman/teensy_betas.git#teensy_1.60-beta5/tool-teensy/linux64 git version 2.51.2 Cloning into '/home/skunk/.platformio/.cache/tmp/pkg-installing-34lhpqms'... Tool Manager: Could...

Have a close look at the modules. I had some manufactured by waveshare that included a 120 ohm termination resistor across the bus. I also notice that you have not soldered the header on the 4.0. As is it in the photo I doubt you have any decent connections.

After this you should check if the call succeeded with if (TheFile.isOpen()) or even if (TheFile) before blindly assuming the IO will succeed. TheFile.write() returns the number of bytes actually written to disk. So if it returns 0 or less than the number requested then you know there is a...

You might find that the compiler is actually calling a bool() operator override instead of a null pointer test

Doesn't this method do what you want? inline int32_t readAndReset() {

Check the code that is running on the teensy. The symptoms sound like the usual while (!Serial) { }

Call addMemoryForRead() and supply your own buffer

if (hueShift == 0 && previousHueShift == 255 && !isHueReset) { I suspect this will never be true since you set previousHueShift to hueShift in the last line of your loop

Have you done some tests to see how much time is being spent in the 1) very slow and 2) multiple, redundant Serial.print() calls?

See https://www.pjrc.com/store/ic_mkl02_t4.html Scroll down to "Troubleshooting & Diagnostic Blink Codes"

What happened when you pressed the "PROGRAM MODE BUTTON" as instructed in the message?

Yes. It is integrated into the hardware interrupts that handle the read / write of the UART.

Look at these functions: // Increase the amount of buffer memory between reception of bytes by the // serial hardware and the available() and read() functions. This is useful // when your program must spend lengthy times performing other work, like // writing to a SD card, before...

+1

This isn't really related to PJRC teensy products

Teensy 4.1 is *not* 5V tolerant. Applying a 5V signal to pin 14 probably fried things

Surely you want to change the constructor of UI() to pass a reference to U8G2_SSD1309_128X64_NONAME0_F_4W_HW_SPI instead of passing the actual instance which would cause the compiler to (try to) instantiate a new copy.

I doubt whether you will get any useful output from Serial.println() while interrupts are disabled

Did you consider adding a dummy stub like this int _write(int file, char *data, int len) { return 0; }

Try with framework = arduino instead of framework = Arduino

whats the problem? long long is int64_t https://gcc.gnu.org/onlinedocs/gcc/Long-Long.html

If you look at the card that was supplied with 4.1, look for the pins labelled CTX1/CRX1, CTX2/CRX2, CTX3/CRX3

If you look in HardwareSerial.h you will find the following virtual void setRX(uint8_t pin) { serial_set_rx(pin); } virtual void setTX(uint8_t pin, bool opendrain=false) { serial_set_tx(pin, opendrain); } edit: copied from correct core

Perhaps the callbacks need more STACK space than you have available. Post the memory information generated after the build so we can look to see just how close to the edge you actually are.

The definition of DMAMEM is in avr/pgmspace.h. So try adding this at the top of your source file #include <avr/pgmspace.h>

Try msg.buf[6] = 0xA5; msg.buf[7] = 0x5A;

Or you could just use this https://github.com/sstaub/TeensyID

@wwatson - Yes I'm using SPI. Unfortunately, the above changes have made things unstable (an endless stream of Serial.println("2D ready failed"); ) and I have reverted them. My setup is probably a little unusual in that I have *very long* wires to the screen (>2m) and even with inline resistors...

Changing #define DRAM_FREQ 166 // 120 // SDRAM clock frequency, unit: MHz. RA8876 to #define DRAM_FREQ 160 // 120 // SDRAM clock frequency, unit: MHz. RA8876 gets rid of the compiler warning and still "feels" faster. Also does not exceed this // SDRAM access clock,suggested 50~160MHz

Thanks for this. Unfortunately using these values results in an overflow. It works, but probably not as intended lib/Ra8876LiteTeensy/src/RA8876_t3.cpp:809:69: warning: unsigned conversion from 'int' to 'ru8' {aka 'unsigned char'} changes value from '264' to '8' [-Woverflow] 809 |...

Please stop posting ChatGPT generated rubbish. It adds nothing the the thread.

more ChatGPT spew

Aside from the above, I believe you have a bit of a logic bug in your posted code for (int i = 0; i < msg.len; i++) { Serial.print(msg.buf[i]); Serial.print(" "); Serial.println(""); switch (msg.buf[1]) { case 0x75: output_voltage = (msg.buf[6] *...

I would use something like an INA219

Calling SPI.begin() will assume you are using the default pins. CS=10, MOSI=11, MISO=12,SCK=13 If you wish to use alternate pins/ports, you will need to ensure that SPI is initialized accordingly and the library has support for alternative SPI ports (some don't. I don't have any experience with...

As far as I know there are some limitations as to which psram chips are supported. I assume you have read this?

Is there another device on the bus to ack the message? Without the ack it will just resend forever

To be safe you should probably use the value from SD.h #define MAX_FILENAME_LEN 256