Interface and Connectivity ICs
MEMS and Sensors
Analog and Audio
EMI Filtering and Signal Conditioning
Power Management and Motor Control
SPC5 Automotive MCUs
ST25 NFC/RFID Tags and Readers
Switches and Multiplexers
STM32 MCUs Community
MEMS and Sensors Community
Automotive MCUs Community
STM8 MCUs Community
Help the community
Share your activities
Contribute your knowledge
About this community
to create and rate content, and to follow, bookmark, and share content with other members.
Question asked by
on Jun 12, 2006
on May 17, 2011 by 17926
Show 0 Likes
No one else has this question
Mark as assumed answered
This content has been marked as final.
Show 1 comment
(Required, will not be published)
May 17, 2011 11:50 AM
We are using the PSD 4256G6V and are having a few problems.
The first problem is that when the SRAM standby voltage is above VCC, the chip goes into standby mode which means no memory may be accessed. Since our VCC voltage is 3.3V and the battery is 3V (or typically 3.3V when new) this causes major problems. I would have thought the SRAm would be valid so long as VCC is above 2V or the SRAM valid voltage level.
Problem2 is we cannot read back PSD memory data using our ST flashlink programmer. Upload only gives a .obj file.
Problem3 is we cannot program flash using the memory interface method (as opposed to JTAG). The erase sector command does not work at all, the erase all command takes many seconds to complete and returns before fully erased (shoudl wait and check polled status), and the flash program with poll or toggle does not work effectively. Someone here suggested that maybe the state machine is not kicked off.
Another minor issue is that with our Hitachi chip, the bytes are swapped by PSDsoft express.
Help with all these problems would be much appreciated since the help files appear to have no info about these problems.
Show 0 Likes
Retrieving data ...
2018 STM32 Wish List
STM32-C2C (Cellular to Cloud) Web Concierge Portal
STM32F769I-DISCO: No audio output from wm8994
STM32CubeMX V4.24.0 code generation failure (bug report)
CubeMX SDIO DMA FatFS configuration