which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

User avatar
rudi ;-)
Posts: 1727
Joined: Fri Nov 13, 2015 3:25 pm

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby rudi ;-) » Fri May 19, 2017 10:52 am

ESP_Sprite wrote:
We plan to release the branch that supports psram eventually;
I'll also make a post (or we'll integrate a document in esp-idf) detailing the ins & outs of what's going on and what to watch out for at that time.

Jeroen, sry
since 37KW 2016 the pSRAM is here.

i must ask: why eventually ?
honest - why?

is this protect and only with NDA to get?
is this not public for community?
is this going on only public to pycom team?

if i can't work this weekend here corectly
then i will send back the batch on monday - and the theme pSRAM and other is dead for me,
sry


edit:
i have wrote
-> support uno
-> sales
-> stanza
-> john
-> ivan
-> angus
-> you

is there any guy further who can help and answere?
no

why you guys let stand the community ( they have bring out you big ) now in the rain
and turns you to commercial targets and us the back?

You forgot that some time ago you became community....
sry


we wait now long long time for this
and i read "eventually" ?

my emotionaly is on the highest now.
sry
-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪

ESP_Sprite
Posts: 9708
Joined: Thu Nov 26, 2015 4:08 am

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby ESP_Sprite » Fri May 19, 2017 11:17 am

Yes, that stuff happens. We have internal engineering samples we can show off to people to give them an indication what will happen in the future: these engineering samples sometimes internally are put together with the metaphorical ducttape and spit, but you don't see this if you look at just a picture. If we would hand out software and hardware that falls over as soon as you look at it too long, we would be publicly known as that that company that releases shitty hardware and software. It's similar with the psram thing: we are having some trouble to get it up and running. If we work together with a single customer who has a single application to run on his hardware, we can happily see to it that the bits of the esp-idf he uses do work as needed, and maybe apply quick fixes if it doesn't. If we however release an esp-idf like that in public, we'll get flooded with people saying it breaks whatever they try to do with it. So yes, Pycom gets to play with all the fun stuff early on. Pycom also pays us; they order a metric shitload of ESP32s and that way we can keep the lights on here at Espressif, so it's in our interest that we get them what they need ASAP.

Believe me, we're working hard to get our chips in the hands of even the people who only order one or to to play around with. But doing that in such a way that we don't bury ourselves in support requests takes time. I think that if you look at other companies in our segment, we're already pretty open to hobbyists; we have this forum, you can talk directly to the developers and they even are willing to write half a novel when you're irritated instead of just applying the banhammer. But do understand that the people on this forum aren't and cannot be our main focus, company-wise, if we want to keep the lights on. We do it because we believe creating goodwill to the community is important, and by large the community hasn't disappointed us there. Complaining when you find out that the docs that an engineer posted out of goodwill aren't right and they don't react within 24 hours, is very good for making that goodwill disappear, at least for this engineer.

Believe me, I know how it feel when you can't play with your latest toy/chip/..., but I can tell you that acting in this way won't help you get it working any sooner.

User avatar
rudi ;-)
Posts: 1727
Joined: Fri Nov 13, 2015 3:25 pm

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby rudi ;-) » Fri May 19, 2017 11:25 am

ESP_Sprite wrote:
So yes, Pycom gets to play with all the fun stuff early on. Pycom also pays us;

thank you for your cooperate with us in the last years.
we send back the 100 pcs and other things

have a good rest time on espressif

it is the best to close - if the time is good.
bad times there all over the globe

best wishes
rudi ;-)

https://twitter.com/eMbeddedHome/status ... 7348389892
-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪

WiFive
Posts: 3529
Joined: Tue Dec 01, 2015 7:35 am

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby WiFive » Fri May 19, 2017 11:53 am

I share the sadness that we can't yet be comfortable to build and ship esp32 designs.

Building a platform is hard. But I think it is reasonable to expect any feature listed in the datasheet has published status information and to have published lead times for hardware. And more transparency on internal bug trackers.

Imagine how bad it would be without ivan, jeroen, angus, few others.

Still hopeful for wrover soon. Must be the masochist in me.

User avatar
rudi ;-)
Posts: 1727
Joined: Fri Nov 13, 2015 3:25 pm

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby rudi ;-) » Fri May 19, 2017 12:10 pm

WiFive wrote: Imagine how bad it would be without ivan, jeroen, angus, few others.
confirm, but they now not more community
they are now in the business with payment.
WiFive wrote: Still hopeful for wrover soon. Must be the masochist in me.
wrover shematic is not public,
cause there is pSRAM on it
you must wait for the service to know how the pSRAM is connect and shematic looks
and if you want know more that you can use the pSRAM - you must pay for the service.

@jeroen
the data and table and info you give here for pSRAM
is wrong like you can see, copy paste mistake?

no info 1.8 or 3.3
no info SPI mode what to do with /WP /HOLD
no simply "hello world" check code for corect connect
1/2 year guys!!
so bad.

simple spi driven things not give the response.

sry - you are not more the guy before you gone from community to business.
esp8266 began with fun
esp31b began with fun
esp32 brings fun - but you must now pay for the service - bad things
community bring you big out - now you make invoice to the community?

I have canceled my affairs on paypal to espressif parcel now,
and send my engineers this weekend home.

have good weekend!
have a good rest time.
-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪

ESP_Sprite
Posts: 9708
Joined: Thu Nov 26, 2015 4:08 am

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby ESP_Sprite » Fri May 19, 2017 12:19 pm

For what it is worth, we are very close to releasing the WROOM and PSRAM stuff now. (And no, I'm not going to name a date, you'll have to take my word for that.) The thing is that as long as we don't know things for sure, we're going to get burned... either we don't put anything in the datasheet initially and no one is going to remember us when they're going to make a product, or we do put it in the datasheet but do not release the stuff that's needed for it (psram datasheet, ...) until it's done, leading to issues like this, or we release everything as soon as we have built it internally and we get shit for errors in the stuff we released. (If you want an example, we gave out some early psram samples and I gave out some screenshots from an early datasheet of the chip... and here we are...) So for the PSRAM thing, we will be releasing everything at the same time, when we're confident that most of the people grabbing the chips, toolchain, SDK and datasheet will not have any problems getting them up to date, and we won't have sour faces that people can't do interesting stuff with their hardware yet. That does mean that we have to be 1. sure that there aren't too many breaking bugs around, and 2. that the documentation is OK and consistent, and that takes time.

ESP_Sprite
Posts: 9708
Joined: Thu Nov 26, 2015 4:08 am

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby ESP_Sprite » Fri May 19, 2017 12:21 pm

Also, WiFive, what do you mean wrt 'transparency on internal bug trackers'?

User avatar
rudi ;-)
Posts: 1727
Joined: Fri Nov 13, 2015 3:25 pm

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby rudi ;-) » Fri May 19, 2017 12:43 pm

ESP_Sprite wrote:
(If you want an example, we gave out some early psram samples and I gave out some screenshots from an early datasheet of the chip... and here we are...)
the screenprint does show 0x03 for write and does show 0x03 for read,
but the table looks difference. perhabs you check this
_first_try_same_cmd_fails.jpg
_first_try_same_cmd_fails.jpg (127.08 KiB) Viewed 11211 times
if you can check the testing code, ( more we can not test cause we have no info what we must do )
so you can edit to run a simple

-> write
-> read
-> READ_ID

here is my help to you if you are not start this
you can edit by your knowledge to start here

it is a simple SPI Master code
taken from the esp-idf repo
and edit for using it with pSRAM
and i am sure - there are many mistakes
in it - but we do not know more -

/WP
/HOLD
Were connected to presumption
Whether it is correct - no idea
I have no data sheet of the "manufacturer" available - but you Jeroen.

Simple task to write and read fails
- there must be wrong info about CMD
- there must be wrong info about connect
- there must be wrong / bug in rev 0 silicon? ( i think not so cause rigol response some things right way )
- CLK is 10MHz - so SPI read write must be work ( support is do 33 )
...
...

we play now 14 days on this without a result

Code: Select all

#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "esp_system.h"
#include "driver/spi_master.h"
#include "soc/gpio_struct.h"
#include "driver/gpio.h"

#define PIN_NUM_MISO 25		/* 	DO  (2) */
#define PIN_NUM_MOSI 23		/* 	DI  (5) */
#define PIN_NUM_CLK  19		/* 	CLK (6) */
#define PIN_NUM_CS   22		/* 	CS  (1) */
/*								/HOLD 	-> VCC ( pulled up )
 * 								/WP 	-> GND ( pulled dwn)
 */


/*
 *  pSRAM
 *  knowed CMD
 *
 */

#define PSRAM_SPI_FREQ	33000000
#define PSRAM_SPI_READ	0x03  // 3
#define PSRAM_SPI_WRITE 0x02  // 2
#define PSRAM_RESET		0x99
#define PSRAM_READ_ID	0x9F


//This function is called (in irq context!) just before a transmission starts. 
void pSRAM_spi_pre_transfer_callback(spi_transaction_t *t) 
{
   // nothing to do 
}

void app_main()
{
    esp_err_t ret;
    spi_device_handle_t spi;
    spi_bus_config_t buscfg={
        .miso_io_num=PIN_NUM_MISO,
        .mosi_io_num=PIN_NUM_MOSI,
        .sclk_io_num=PIN_NUM_CLK,
        .quadwp_io_num=-1,
        .quadhd_io_num=-1
    };
    spi_device_interface_config_t devcfg={
        .clock_speed_hz=10000000,               //Clock out at 10 MHz 10000000
        .mode=0,                                //SPI mode 0
        .spics_io_num=PIN_NUM_CS,               //CS pin
        .queue_size=7,                          //We want to be able to queue 7 transactions at a time
        .pre_cb=pSRAM_spi_pre_transfer_callback,  //Specify pre-transfer callback  not need for pSRAM
    };

    //Initialize the SPI bus
    ret=spi_bus_initialize(HSPI_HOST, &buscfg, 1);
    assert(ret==ESP_OK);

    //Attach the LCD to the SPI bus
    ret=spi_bus_add_device(HSPI_HOST, &devcfg, &spi);
    assert(ret==ESP_OK);

    /*=====================================================================*/

    printf("try to do see Logical\n");

/*    int cmd = PSRAM_READ_ID;
    // int was = 0x255;

    	// esp_err_t ret;
        spi_transaction_t t;
        memset(&t, 0, sizeof(t));       //Zero out the transaction
        t.length=8;                     //Command is 8 bits
        t.tx_buffer=&cmd;               //The data is the cmd itself
        t.user=(void*)0;                //D/C needs to be set to 0
        ret=spi_device_transmit(spi, &t);  //Transmit!
        // printf("Return: %2X", ret);
        assert(ret==ESP_OK);            //Should have had no issues.

        // was = spi_device_get_trans_result(spi,&t);

*/

        int len = 5;
        uint8_t data[5] = {PSRAM_READ_ID, 0x00, 0x00, 0x00, 0x00};

            // esp_err_t ret;
            spi_transaction_t t;
            if (len==0) return;             //no need to send anything

            for (int doing=0; doing <2; doing++)
            {
            memset(&t, 0, sizeof(t));       //Zero out the transaction
            t.length=len*8;                 //Len is in bytes, transaction length is in bits.
            t.tx_buffer=data;               //Data
            t.user=(void*)1;                //D/C needs to be set to 1
            ret=spi_device_transmit(spi, &t);  //Transmit!
            assert(ret==ESP_OK);            //Should have had no issues.
            }


       // write

       len = 5;
       // uint8_t wdata[15] = {PSRAM_SPI_WRITE, 0x00,0x00,0x00,'h','e','l','l','o',' ','w','o','r','l','d'};
       uint8_t wdata[5] = {PSRAM_SPI_WRITE, 0x00,0x00,0x00,'h'};

       spi_transaction_t tw;
       if (len==0) return;             //no need to send anything
       memset(&t, 0, sizeof(tw));       //Zero out the transaction
       tw.length=len*8;                 //Len is in bytes, transaction length is in bits.
       tw.tx_buffer=wdata;               //Data
       tw.user=(void*)1;                //D/C needs to be set to 1
       ret=spi_device_transmit(spi, &tw);  //Transmit!
       assert(ret==ESP_OK);            //Should have had no issues.

       // read
       len = 5;
       // uint8_t wdata[15] = {PSRAM_SPI_WRITE, 0x00,0x00,0x00,'h','e','l','l','o',' ','w','o','r','l','d'};
       uint8_t rdata[5] = {PSRAM_SPI_READ, 0x00,0x00, 0x00, 0x00};

       spi_transaction_t tr;
       if (len==0) return;             //no need to send anything
       memset(&t, 0, sizeof(tr));       //Zero out the transaction
       tr.length=len*8;                 //Len is in bytes, transaction length is in bits.
       tr.tx_buffer=rdata;               //Data
       tr.user=(void*)1;                //D/C needs to be set to 1
       ret=spi_device_transmit(spi, &tr);  //Transmit!
       assert(ret==ESP_OK);            //Should have had no issues.

       printf("..ok\n");

}

this is code without payment - not empty promissings.
there is not in the code " a return" i look on rigol what happens.
and there is shit on the given infos -

this is community we like
we talk open on problems - and hope for answeres to bring further info.

i start this theme now -

some guys know better SPI master and edit the code to go on
some guys know better pSRAM and edit clk cykle and so on
some guys know better to handle electronic HW ( pullups, pulldowns, values )

this is community!
and the "payment guys" steal this infos here more and more for they business
sry !

now i will see that here is community go on and not payment business for services
Last edited by rudi ;-) on Sun May 21, 2017 1:54 am, edited 1 time in total.
-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪

ESP_Sprite
Posts: 9708
Joined: Thu Nov 26, 2015 4:08 am

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby ESP_Sprite » Fri May 19, 2017 1:18 pm

I'm not going to drop any more nuggets of information here, because I don't want to get into trouble with that a second time, but I highly suggest you drop the project for now and wait until the datasheet is out; at the moment, you run the risk of breaking your chips and without trying to sound disrespectful, but with code like that I do not think you are going to get it to run. Feel free to ignore that advice if you want to, but I'm just saying.

User avatar
rudi ;-)
Posts: 1727
Joined: Fri Nov 13, 2015 3:25 pm

Re: which new "esp" 8 pin ic is this on the new esp32 modul? ;-)

Postby rudi ;-) » Fri May 19, 2017 1:19 pm

ESP_Sprite wrote:I'm not going to drop any more nuggets of information here, because I don't want to get into trouble with that a second time, but I highly suggest you drop the project for now and wait until the datasheet is out; at the moment, you run the risk of breaking your chips and without trying to sound disrespectful, but with code like that I do not think you are going to get it to run. Feel free to ignore that advice if you want to, but I'm just saying.

i send back the parcel

end of story
-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪

Who is online

Users browsing this forum: Google [Bot] and 113 guests