No announcement yet.

Need to Know the Mehod to get the actuatl Firmware of Picaso Programatically

  • Filter
  • Time
  • Show
Clear All
new posts

  • ESPsupport
    Please collect the information I asked for. I cannot possibly speculate anything until I see what that information contains.

    Leave a comment:

  • jorge contreras Ramirez
    The Sd is purchase from Mouser but under 4Dsystem tag. I'f already chek the ID of the uSD throw your uSD test and I can confirm that is Pyshon 4GTB same version that we already have and comming from you.

    ┬┐Maybe is a problem woth the firmware?. The extrange thing is that for those failed the uSD is formatting by your Program 1Gb og Fat and thencopy all the content to that. Then I attach to your TFT and no mor writes are done. In fact we remove all the writes for the program. But in 15ddays the content of the Fat has changed again.

    In regards to Know the version, I contact to sign the Nda, Thanks a Lot.

    Leave a comment:

  • ESPsupport
    As tonton says, for Picaso, the only way to find the PmmC version is via the bootloader. This means you will need another 'system' to acquire this information, it is not clear from your post why this is needed. This information is available under NDA, please make a technical enquiry via the contact pages on the web site if you want to go down that route.

    I am very surprised that you are seeing read disturb with a Phison Industrial purchased from us. Can you confirm that you did, indeed purchase it from us? Regardless, can you start RMpet and post a screencopy of the details about the uSD as it is at the moment (i.e. don't use RMpet to change anything), can you also use the uSDTester utility and post a screenshot from that?

    Here's a snippet of code that will calculate a 16 bit CRC on Picaso, it will most likely need many changes to use it in your code, as it is not 'stand alone' as it is.

    Note that running this doesn't prove that read disturb is not happening as the disturbance can change from 'read to read', in the beginning it might be only one bit in a large file occasionally, as you continue reading the same data the number of bits in error and the frequency of them being in error increases.

        word CRC_Table 0x0000,0x1021,0x2042,0x3063,0x4084,0x50A5,0x60C6,0x70E7,0x8108,0x9129,0xA14A,0xB16B,0xC18C,0xD1AD,0xE1CE,0xF1EF,0x1231,0x0210,0x3273,
    func crc_CCITT(var DataPtr, var DataLen, var crc)
    //crc contains either the initial CRC value or the CRC result from previous data block
    //DataPtr is a byte pointer to the data block, with the data to be checked. Data can be divided in several blocks, and processed one after the other
    //DataLen is the length of the data block in bytes
    //561 bytes, 30 us per character
            crc := CRC_Table[str_GetByte(DataPtr++) ^ (crc>>8)] ^ (crc<<8);
        return crc;
    func GetFileChecksum()
        // C
        var hndl, crc, rd ;
        com_GetStr(fname) ;
        print("Get CRC ", [STR] fname) ; nextline() ;
        hndl := file_Open(str_Ptr(fname), 'r') ;
        if (hndl != 0)
            crc := 0xffff ;
            rd := file_Read(buf1, RX_BUFFER_SIZE_BYTES, hndl) ;
            while (rd)
                crc := crc_CCITT(str_Ptr(buf1), rd, crc);            // given a pointer to a buffer, byte count and seed, calculate the 16bit CRC for seed
                rd := file_Read(buf1, RX_BUFFER_SIZE_BYTES, hndl) ;
            file_Close(hndl) ;
            com_PutWord(crc) ;
            com_PutWord(0) ;
        print("Finished get CRC") ;      nextline() ;

    Leave a comment:

  • tonton81
    did you try sniffing the UART data while going to the PmmC loader page? If the loader is able to know the version number, (havnt checked), then it's reading it off the bootloader, you'd need to capture the TX channel to see what the loader is sending and capture the RX channel to see the responses

    Leave a comment:

  • Need to Know the Mehod to get the actuatl Firmware of Picaso Programatically

    Sorry. There is anyway to get the actual PICASO firmware version number (Example 4.4) from the programing way. We need also to know if there is also a method to compute the actual CRC of a file over the Fat.

    The problem arise because we have already deploy 1000units of Picaso around the world. These is so much hardware, but a lot of them are experience a "read disturbance problems". That is, even if we use your own uSD of 4GB from Pyshion Industrial Grade (buy to you), and even if I'm not write to the uSd in anyway, after 15days the content of the fat from uSD are changing or degrading, and then the display failed completely and we need to send a person to any location to replace a uSD.

    As you see is a very important problem tha cause a lot of money waste.

    Thanks a Lot.