Jump to content

AryA7_user

Members
  • Posts

    3
  • Joined

  • Last visited

AryA7_user's Achievements

Newbie

Newbie (1/4)

0

Reputation

  1. I just asked my supervisor, and he said that the flash he gave me had some problems ? . Anyway, thank you a lot for your response.
  2. Thank you for your answer @JColvin. Yes I am using an Arty A7 35T. I do check all the commands I send or the response I get using a logic analyzer, and they all seem correct which validates the software end. I don't do any write operations to protected areas, furthermore my status register is all zeros which means all memory areas are unprotected. And as I said, what's really weird, is the flash works fine but once I write that register, it starts sending ones. I am really stuck at this point because I don't have any ideas about further steps that should be done to debug the problem. I am thinking about writing the non-volatile configuration register directly, but I'm afraid the same problem happens and in that case turning off and on the flash will probably get it back to normal functioning.
  3. Hey everyone, I'm having a problem with pmodSF3 that uses a flash memory with FBGA code RW146 ( datasheet). The problem is once I try to modify the enhanced volatile configuration registers, the flash starts sending ones. I tried to follow the datasheet by sending a write enable, then 0x61 command and then the value to write in the register. I did check the commands using a scope, and they are sent correctly. What's weird is the flash works fine but once I try to modify that register the flash starts sending ones and nothing works until I power off and on the board. As you can see the first tests works fine, then I try to modify the volatile enhanced register and then things get messy. Someone has an idea of what's happening ?
×
×
  • Create New...