Code: Select all

tar -xf xtensa-esp32-elf_psram.tar.xz

Code: Select all

sudo apt-get install git wget make libncurses-dev flex bison gperf python python-serial
sudo apt-get install gawk gperf grep gettext python python-dev automake bison flex texinfo help2man libtool libtool-bin g++ libncursesw5-dev
cd ~/esp
git clone -b xtensa-1.22.x-ext_ram_patch https://github.com/espressif/crosstool-NG.git
cd crosstool-NG
mkdir .build
cd .build
wget http://loboris.eu/ESP32/crosstool-NG_psram_.build_tarballs.tar.xz
tar -xf crosstool-NG_psram_.build_tarballs.tar.xz
rm crosstool-NG_psram_.build_tarballs.tar.xz
cd ..
./bootstrap && ./configure --enable-local && make install
./ct-ng xtensa-esp32-elf
./ct-ng build
chmod -R u+w builds/xtensa-esp32-elf
			
loboris wrote:Some of the servers with needed toolchain components are not accessible at the moment (isl.gforge.inria.fr/).

You can download compiled (for Linux 64-bit) toolchain package from my GitHub repository.

Just unpack with:
Code: Select all
tar -xf xtensa-esp32-elf_psram.tar.xz
You can download needed tarballs from here.

After cloning crosstool-NG, got to to the cloned directery and create .build directory.

Unpack the downloaded tarball archive to the .build subdirectory.

Now you can build following the instructions.

The whole procedure:
Code: Select all
sudo apt-get install git wget make libncurses-dev flex bison gperf python python-serial
sudo apt-get install gawk gperf grep gettext python python-dev automake bison flex texinfo help2man libtool libtool-bin g++ libncursesw5-dev
cd ~/esp
git clone -b xtensa-1.22.x-ext_ram_patch https://github.com/espressif/crosstool-NG.git
cd crosstool-NG
mkdir .build
cd .build
wget http://loboris.eu/ESP32/crosstool-NG_psram_.build_tarballs.tar.xz
tar -xf crosstool-NG_psram_.build_tarballs.tar.xz
rm crosstool-NG_psram_.build_tarballs.tar.xz
cd ..
./bootstrap && ./configure --enable-local && make install
./ct-ng xtensa-esp32-elf
./ct-ng build
chmod -R u+w builds/xtensa-esp32-elf
Hi Loboris,

Thanks for valuable reply.

So, If I extract your 64 bit supported Toolchain then will it work directly into 64 bit supported Ubuntu 14.04 or 16.04 Linux System?

Also, I will try steps which you have provided to clone cross NG and will build into my system as well and will provide result as soon as possible.

Again thanks for your support.

									
Regards,

Ritesh Prajapati
			
Ritesh wrote:So, If I extract your 64 bit supported Toolchain then will it work directly into 64 bit supported Ubuntu 14.04 or 16.04 Linux System?
Yes. Tested on Ubuntu 16.04 & Ubuntu 17.04, but should work on any 64bit Linux system.
			
loboris wrote:
Ritesh wrote:So, If I extract your 64 bit supported Toolchain then will it work directly into 64 bit supported Ubuntu 14.04 or 16.04 Linux System?
Yes. Tested on Ubuntu 16.04 & Ubuntu 17.04, but should work on any 64bit Linux system.
Hi Loboris,

Thanks for quick response.

Tomorrow morning I will check it and get back to you if any issue while accessing it.
									
Regards,

Ritesh Prajapati
			
Hi Loboris,

Thanks for your help. Your provided toolchain for linux 64bits works fine. I tested dynamic memory allocation in PSRAM successfully.

Thanks.
			
Hi Loboris,

Thanks for quick support to resolve ESP32 Toolchain building issue for PSRAM support. We have checked sample example to malloc higher then 1 MB which works fine without any issue.

We have also checked data read/write on that buffer which is also works fine without any issue. SO, in short we can use up to 4 MB SPI PSRAM malloc for our application development purpose.

Hi Loboris / Espressif Systems Developer,

Right now, We have cloned psram_malloc branch to check PSRAM feature support which works fine but i think it has been included into master branch as well.

We have checked master branch as well but failed to malloc on PSRAM.

So, Do you have any idea that those PSRAM branch changes have been included into master branch or not? Espressif Systems Developer might have much idea for this.
									
Regards,

Ritesh Prajapati
			
Ritesh wrote:...We have checked master branch as well but failed to malloc on PSRAM.

So, Do you have any idea that those PSRAM branch changes have been included into master branch or not? Espressif Systems Developer might have much idea for this.
malloc is not yet supported, if spiram support is enabled, you can access psram region directly:
Code: Select all
buf1 = (uint8_t *)0x3f800000;
There are some problems, look at this and later posts viewtopic.php?f=13&t=2824#p13671
			
loboris wrote:
Ritesh wrote:...We have checked master branch as well but failed to malloc on PSRAM.

So, Do you have any idea that those PSRAM branch changes have been included into master branch or not? Espressif Systems Developer might have much idea for this.
malloc is not yet supported, if spiram support is enabled, you can access psram region directly:
Code: Select all
buf1 = (uint8_t *)0x3f800000;
There are some problems, look at this and later posts viewtopic.php?f=13&t=2824#p13671
Hi Loboris,

Yes of course simple malloc is not supported yet, but we tested it using pvPortMallocCaps(size, MALLOC_CAP_SPIRAM).

While using buffer = pvPortMallocCaps(10, MALLOC_CAP_SPIRAM), we got "buffer" address as 0x3f800008.

We tested it with 40MHz speed only. This works with feature/psram_malloc branch but not with current master branch.
				Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year
		Sort by AuthorPost timeSubject AscendingDescending