Hi All! I still have a clicking sound, I've tried everything. Anyone have any tips on how to fix it?
T4.0, A1 SDHC 32gb micros, original repo with "256-sample audio blocks tweak"
Thank you very much!
Ok, by just moving that code around inside startup_MIMXRT1052.S, I pretty quickly found this is the part that's crashing.
#ifdef __STARTUP_INITIALIZE_NONCACHEDATA
ldr r2, =__noncachedata_start__
ldr ...
I can confirm the code is starting up, before something goes wrong.
Added this to mbed-ce-hello-world/mbed-os/targets/TARGET_NXP/TARGET_MCUXpresso_MCUS/TARGET_MIMXRT1050/device/TOOLCHAIN_GCC_ARM/startup_MIMXRT1052.S...
Divisions are slow. I have not tried it, but maybe it helps to multiply with 1.0f/max instead:
std::max(max, 10.0f);
max = 1.0f/max;
for (int i = 0; i < m_signalLength; i++) {
m_targetSignal *=...
The only thing I did notice is, the Teensy bootdata.c file has this:
const uint32_t ImageVectorTable = {
0x432000D1, // header
(uint32_t)&Reset_Handler,// program entry
0, // reserved
0, // dcd...
Hmm, I took a look through the boot stuff in the hex file (IVT + flash config + vector table) and I didn't see anything that screamed out at me as being wrong. Addresses for various things match the map file and are in...
I can confirm the csf section is only needed if you run the teensy_secure program which creates the .ehex file from the .hex file. Everything else just ignores it.
Thanks a ton for giving it a shot, guys! Home from work now so I will check this out.
> Seems like the mbed T4.0 code is derived from the 1050
Yep, that's correct. It's based on Mbed's 105x HAL layer, plus boot...
Easiest and maybe effective in some fashion - unless the included library examples were altered:
This 320x240 color TFT display is recommended for use with Teensy 3.2 to Teensy 4.1, for high resolution color...
Any more specific suggestions on how I should rearrange the info on that page to make it clearer?
Somehow I suspect @donperryjm's suggestion to move the link much farther down the page, to just after the pinout table...
Yes, I copied from that link in post #2 to resolve the problem ...
It seems a bit distant {with two interposed lines} as it gets missed? And the examples for the prior linked display library include the Analog not...
Was going to wait until Jamie chimes in again before looking at this code again, but since you mentioned it...
__attribute__ ((section(".boot_hdr.boot_data"), used))
const uint32_t BootData = {
...
In "lv_fs_fatfs.c" I'm getting an error that ff.h is not found. I'm using the sdfat library and I set LV_USE_FS_FATFS 1 . Is there anything you had to do for that file to be found?
So have you actually run your HelloWorld project on a T4.0?
maybe add the HellowWorld.hex to your git repository.
I believe T4.0's are in stock at pjrc.com
Paul, have you examined mbed-os/targets/TARGET_NXP/TARGET_MCUXpresso_MCUS/TARGET_MIMXRT1050/TARGET_TEENSY_4X/bootdata.c
Above my pay grade ...
Seems like the mbed T4.0 code is derived from the 1050. I did some...
Good results Fast!
Yes, that confusion has come up before where the display examples don't fit the PJRC display.
@Paul might see this - but there is a 'Web-site-could-use-a-few-updates' edits needed thread - if...
The post seen should resolve your issue.
To answer this - some Touch Screens present analog output to represent the touch position. The PJRC display has onboard logic to parse the analog values and present them...
I see this section in the code.
What is the relationship between this snippet and the config on the PJRC page? #define YP A2 // must be an analog pin, use "An" notation!
#define XM A3 // must be an analog pin, use...
That uses library #include "TouchScreen.h"
That is not the one for the PJRC display.
Use a sample from this library folder: github.com/PaulStoffregen/XPT2046_Touchscreen/tree/master/examples
That uses library:...
Hey guys, me again.
I bought this touch screen display from PJRC.com
and applied the code written here to a teensy 4.1
the display seems to be working but i cannot get touch to work. I triple checked the jumper...
Jimmie:
Why not use a small laser and a sensor at the other end?
or,
You could try two thin strips of aluminum foil very close to each other on a non conductive layer perhaps made of Capton or something like it. You...
BriComp:
A while back I decided to try your suggestion on my Mac(OS Monterey 12.6.3). It would not even install, I got a whole lot of errors with no explanation as to what the errors meant.
Regards,
Ed
NEWSFLASH
Sysex file transfer works!
/* one tool to rule theM 1. - | copy left | M1Addict 2023
*
* a KORG M1 -> Translator + Midi repeater
*
Midi CH | function
I glanced at the linker script and generated code. Can't see anything obviously wrong.
I noticed you have a .csf section. Are you supporting code signing and BEE on-the-fly decryption? Of the many developments on...
OC Trial posts long ago - but not sure it ever has worked over 1.08 GHz.
Internal voltage has to rise as the speed goes up - and over max spec voltage before 1.08 GHz.
There is some cusp/spike internally when it...
While I have little experience with the audio capabilities of the T4.1, this thread does raise some interesting questions about memory management. The one that intrigues me the most is whether it would be possible to...
There are a couple of changes that should be made to ensure 3.3V compatibility:
1. D2 and D3, the 4.7V zener diodes in the input limiter to the analog pins should be changed to values below 3.3V
2. The encoder...
Do you mean the problem of copying data from a large buffer to a smaller one? You had the basic idea, but you had some mistakes in your logic. I suggest you make more use of print() and println() for debugging, because...
Tried it here. Same result, doesn't work. Same 8 blink error.
It printed this at the end of the build process
Linking CXX executable HelloWorld.elf
-- built: /tmp/mbed-ce-hello-world/build/HelloWorld.bin
--...
did that. and voila!
static uint16_t MIDI_BUFFER_LENGTH = sizeof(midi_buffer)/sizeof(midi_buffer);
Now everything works as i wanted it to :)
Thanks for the help!
ITS WORKING !!!
data array gets read into 128 byte buffers.
if the buffer size is bigger then the remaining data from the data array
the missing bytes are padded with 0x00. (overwriting the garbage that was there...
Tried but failed. :confused:
on Ubuntu 18.04.06 with stock arm-none-eabi-g++ version 6.3.1, cmake looked OK, and ninja built HelloWorld.hex
ninja
Linking CXX executable HelloWorld.elf
-- built:...
Thank you for the timely reply and helpful answers to my questions, Neal.
Understood. Good thing that I haven't already deleted it from the schematic and haven't wasted my $ on purchasing the CAT811T ICs.
Thank...
Hi everyone, I would like to extend RAM on the Teensy 4.1 to make a four channel looper.
I would like to make a new version of Frank's board for the APS6404L-3SQR-SN 8MB SPI memory chip with 8 chips on it.
I am...
joepasquariello: Did it. Its ok. prints out the same numbers. so i revert it to non static declaration.
31520
128
the garbage after the last byte is also the same. as with fixed values for the array lengths.
Ok, so far. it almost works when i use a buffer size of 128.
Still having problems with the padding. and "random" values
following the last byte of the source array.
1B 58 05 00 00 00 00 00 1C 5A 05 00 00 00 00...
Try adding these two lines after you compute the lengths of the buffers. With this information, can you see what's wrong?
Serial.println( SYSEX_PRESET_LENGTH );
Serial.println( MIDI_BUFFER_LENGTH );
A1: In my experience, the CS42488 reset line startup requirements are a bit sensitive. You need the CAT811T to make sure no short glitches occur during the power up process. If a glitch occurs, the CS42488 doesn't reset...
Just noticed that my midi buffer was 10 bytes short.
i fixed that and added some 0xff on the end and on the beginning of the array as markers.
Still memcp doesnt seem to work and doesnt overwrite the buffer.
...
ok, changing the size does help in that it doesnt reset the teensy anymore.
EDIT: joepasquariello, kd5rxt-mark : So you are totally right that is wrong.
i did miss that cause it made no difference in mey...
Sorry, I may have been editing my post at the same time as you were replying, so you may not have seen the question about the memcpy length parameter.
Since the CrashReport is saved from the previous crash, load/run...
In your call to memcpy(), the 1st argument is the destination (midi_buffer), the 2nd argument is the source (sysex_buffer), and the 3rd argument is the number of bytes to copy. You are passing in the size of the...
Thanks, i tried but still no output on the serial :(
void setup()
{
Serial.begin(115200); while (!Serial) {;} // wait for serial
if (CrashReport) {
Serial.print(CrashReport);
}
...
Should the length to be copied in your memcpy call be MIDI_BUFFER_LENGTH instead of SYSEX_PRESET_LENGTH (assuming that the MIDI buffer is smaller than the total SYSEX array) ??
Maybe try adding the following to...
Hello!
Im playing around with copying data from a large u_int8 array into a small u_int8 buffer.
the large arrays size is 31520 bytes, the buffer is 256 bytes wide.
Seems that my code does something really bad....
Hi guys, I am messing around with overclocking a T4 and managed to get it to pass CoreMark at up to 1.08GHz.
Disclamer: I did this at work where we make high performance coldplates.
I used a 10x10mm coldplate and...
what i am using
/**
* Audio Guestbook, Copyright (c) 2022 Playful Technology
*
* Tested using a Teensy 4.0 with Teensy Audio Shield, although should work
* with minor modifications on other similar hardware...
I installed fresh everything from the original repo. After applying the audio tweak, my recordings sound choppy. I tried several high speed SD cards, all with the same error.
If in continueRecording() function...
Indeed 71.582788266666666666666666666667 Minutes - the question mark was there for a reason ... Opps
There is a 1 ms interrupt that is used to track Millis() systick - that is also the base of Micros() response...
micros overflows after 71 minutes right? Or am I remembering incorrectly.
I had a couple questions to this, I know there's the systick interrupt which goes at 1 ms. So I figure millis uses this in part for...
Now that we're into February, is there any updated information (one way or the other) from NXP regarding the future availability of the MK20, MK64, and/or MK66 chips? Thanks very much.
I agree @MichaelMeissner but if you look at @jmoore's basic design (see post #1) there does not seem to be any reason why a T4.0 might not work.
He would have to make sure non of the T4.0 inputs were more than 3.3V.
The systems used in the UK for temporary speed measurement consist of a rubber tube with one end (the far end) closed and I assume a pressure sensor on the sensing end measuring pressure pulses. Each positive pulse is a...
Incredibly, if you simply ask it "Are you sure?" it will return a (more) correct answer, with an apology for the previous mistake. You can even ask it to double-check its answers before it sends them to you in the...
Not quite. It depends on what you do. Many programs will work fine, but others won't. I wrote the following pages to look at the differences:
Unofficial Teensy Wiki, teensy differences:...
upload_protocol = teensy-cli
Many thanks, kind stranger! That worked like a charm! Uploaded a large-ish program 20 times, and it was blazing fast every time.
So it looks like there may be an issue with the...
Very satisfied PlatformIO user here. Have used it without any problems for many years. Perhaps one of the reasons is that I *don't* use the native graphical teensy uploader. In my platformio.io for all my projects I...
A little more info. After I rebooting my Mac, I no get the "An error occurred while uploading..." message. For the first ~8 uploads everything was very quick, but after that it started to bog down again. So basically...
Thanks for the quick response, Paul! I haven't used the Arduino IDE in a long time, but I fired it up and tried it with the Blink example sketch. (It would take a while to translate my multi-file program back to that...
My first question for all PlatformIO issues is whether the same problem happens when using Arduino IDE.
Going to skip another PIO rant, but please understand PIO is not a consistent software install we can easily...
I've been using the Teensy 4.0 for several years as part of an LED controller for outdoor art installations (like this one). I've had some challenges for sure, but all were eventually overcome, often with help from this...
