Hideto KANOSHIMA
New member
Hello everybody. I am a Japanese hobby programmer. I am having fun with two Teensy4.0.
Please tell me about the "memory area that I should not access" in T4. Is there an area where execution of the program is stopped just by accessing it?
From the figures I have and the logs of this forum, I interpret the rough memory map of T4 as follows.
https://www.pjrc.com/store/teensy40.html
FLASH:
0x0000: 0000-2MB
RAM1:
0x2000: 0000-512KB-0x2000: 2007: ffff
RAM2:
0x2020: 0000-512KB-0x2027: ffff
I wrote the following program to see the data actually stored.
void loop() {
// put your main code here, to run repeatedly:
const char *ptr = (const char *)0x2007f000;
Serial.println(*ptr, HEX);
delay(1000);
}
However, if the address given to read RAM1 is 0x2007f000, this program will lock. If it is 0x2006f000, 0xD7 was read normally.
I would be glad if I could give some advice to me.
(Mac mini / macOSⅩ Catalina / teensyduino 1.50)
Please tell me about the "memory area that I should not access" in T4. Is there an area where execution of the program is stopped just by accessing it?
From the figures I have and the logs of this forum, I interpret the rough memory map of T4 as follows.
https://www.pjrc.com/store/teensy40.html
FLASH:
0x0000: 0000-2MB
RAM1:
0x2000: 0000-512KB-0x2000: 2007: ffff
RAM2:
0x2020: 0000-512KB-0x2027: ffff
I wrote the following program to see the data actually stored.
void loop() {
// put your main code here, to run repeatedly:
const char *ptr = (const char *)0x2007f000;
Serial.println(*ptr, HEX);
delay(1000);
}
However, if the address given to read RAM1 is 0x2007f000, this program will lock. If it is 0x2006f000, 0xD7 was read normally.
I would be glad if I could give some advice to me.
(Mac mini / macOSⅩ Catalina / teensyduino 1.50)