Post links and attach files for documentation here, also chat about these docs freely

User avatar
By piyush
#5018
Squonk wrote:OK, let's reconsider something about Flash memory access: first, the XTensa CPU seems to be clocked @ 80 MHz. It is fast, but nothing compared to more powerful WiSoC running at 400~800 MHz.

Then these Flash SPI chips can also run pretty fast... Not only do they support "simple" single bit wide SPI access, but also dual and quad bit wide access, at speed reaching 80~104 MHz!


Any pointer how to utilise dual or quad bit spi wide access ?
or even sdio?
User avatar
By RogerClark
#5198 Sorry to ask a really dumb question..

But do I need to reflash the SDK to ox40000 every time I recompile an app.

I had a go at only flashing the app part of a build to 0x00000 with a minor change to a debug message, in an existing working app, but the app didn't seem to work any more?

I could have done something else wrong I suppose.

But it seems odd that most make files e.g. Blinkey output the 0x40000 bin every time if there is no change, ie as its the SDK

Or does the linker only put the necessary functions used in the App section 0x00000 into 0x40000?
User avatar
By RichardS
#5204 Time also to get all this memory layout and memory questions permantently answered on the WIKI.....

Anyone????

Richard.
User avatar
By pvvx
#5494 A test version of HTTP Web to read the all memory.
Enternet Explorer reads 600 kilobytes per second ...

Found:
I/O: 0x3FF00000..0x3FFC0000
RAM: 0x3FFE0000..0x40000000
ROM: 0x40000000..0x40100000 (x2)
IRAM: 0x40100000..0x40140000
IROM: 0x40200000..0x40280000
???: 0x60000000..0x60002000