[SOLVED] Issues to erase a Micron N25Q512A Flash Memory using JFlashSPI v618d.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Issues to erase a Micron N25Q512A Flash Memory using JFlashSPI v618d.

    Hello,

    I am experiencing issues to flash a Micron N25Q512A Flash Memory using JFlashSPI v618d.

    JFlashSPI can auto detect the flash memory (pls see autodetect.jpg attachment).
    But
    then it's not able to erase (F4 shortcut) the chip ( erase lasts less
    than 2 secondes ! ) by using the auto detect parameters (read status
    0x05, readybit=0 , etc).

    This behaviour is not a surprise for me
    because I wrote a few weeks a test program to flash this component (with
    other materials, before to discover JFlashSPI) and i had to use the
    0x70 command (READ FLAG STATUS REGISTER) and the bit 7(Program or erase
    controller) of this status register instead of 0x05 (READ STATUS
    REGISTER) and bit 0 (Write in progress) to manage the erase phase
    correctly.

    So i made manual modifications in Project Setting \
    Flash Tab by unchecking the auto detect checkbox (see project_settings.jpg)
    without success : I get a "time out occured" message .
    I test also 0x80 as busybit : none improvement, action seems to well finished but a readback shows some non-0xFF bytes.

    Pls
    can you help me to set correctly this project and understand the field
    in settings panel in order to use the capability of JflashSPI to write
    only the affected sectors to reduce programming duration.

    Thanks .
    Best Regards
    Stéphane
    Images
    • jflashspi_autodetect.JPG

      33.98 kB, 189×398, viewed 408 times
    • project_settings.JPG

      47.05 kB, 424×452, viewed 531 times
  • Hello Stephane,

    Thank you for your inquiry.

    We are currently investigating the reported issue and will tell you the results as soon as possible.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hello Stephane,

    Thank you for your patience.

    We have found the reason for this issue and a fix will be applied in the next official release version (V6.20e)

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hi Stephane,


    thanks for the feedback and great to hear that you are up and running again!

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.