element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
MaaXBoard Hardware Design MaaXBoard-RT: persistent SYSCFG in Hyperflash - how?
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 2 replies
  • Subscribers 323 subscribers
  • Views 405 views
  • Users 0 members are here
  • MaaXBoard-RT
  • persistent
  • Hyperflash
  • flash memory
  • non-volatile
  • maaxboard
Related

MaaXBoard-RT: persistent SYSCFG in Hyperflash - how?

tjaekel
tjaekel over 2 years ago

I want to have a persistent (non-volatile) storage for my SYSCFG:
parameters, like SPI clock speed, SPI mode, IP address of MCU... should be stored and loaded when a reset/power-up cycle is done,
from a non-volatile memory (like from an external I2C flash memory).

MaaXBoard-RT does not have an external I2C flash memory, but it has the Hyperflash.

How could I "reserve" a sector in Hyperflash (256 * 4bytes is enough, a "sector/page") and save there my SYSCFG?

I have studied the API, the FW code, SDK examples (which might not help due to a different flash device used), but I cannot find any API (code, function) which would allow me to write and read a sector (piece of memory)
to/from Hyperflash during runtime.
All seems to be related only to flash your FW (done by debugger), but not possible to create a "user sector" there, to write and read from it during runtime (when my FW is running and doing it "itself").

Options:

OK, it would be fine to have "backup" registers, so that I can do a FW Reset (restart via SW command, but not a power cycle), and these registers are
not cleared on reset. Other MCUs (STM32H7xx) have "backup registers" in RTC which are not cleared on Reset (cool). But missing here (maybe I could "hijack" the Year, Month, Date registers in RTC, but not ticking/using the RTC).

I found some "general purpose registers", e.g. GPR_SHARED[8] in CCM module.
They could help, just not so much as I need (just 8, plus PRIVATE, also 8, but I need potentially up to 64 x 32bit registers which would survive a reset):
I want to start-over entire FW from startup ("SW Reset") but with modified SYSCFG.

Let's see.
If you have any idea how to have a persistent memory which would at least "survive" a reset,,,
(not initialized SRAM, DTCM might do as well, but not SDRAM (it does not "survive" a reset)).

Other option is to use I2C and connect an external I2C flash memory. OK: just a HW extension needed (PCB, e.g. like a HAT).
To use the Hyperflash for this feature would be great:
- but no idea how to use Hyperflash when FW is running (for erase/write/read a sector from there, also to make sure the next FW flash does not rip out my SYSCFG

Do you have any idea?
Thank you.

  • Sign in to reply
  • Cancel

Top Replies

  • michaelkellett
    michaelkellett over 2 years ago +1
    A small I2C memory (often bit banged so no actual I2C peripheral on processor is needed) is my usual way to do this (not on MaaXBoard). Its always a bit high risk to dual purpose use a sector organised…
Parents
  • michaelkellett
    michaelkellett over 2 years ago

    A small I2C memory (often bit banged so no actual I2C peripheral on processor is needed) is my usual way to do this (not on MaaXBoard).

    Its always a bit high risk to dual purpose use a sector organised flash for code and data. You have to empower your code to erase and write data sectors in the same physical space as code sectors. You can devise protections but its very easy to make a mistaake.

    MK

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • tjaekel
    tjaekel over 2 years ago in reply to michaelkellett

    I agree with you. Thank you.

    Best is: to use an external I2C flash memory (I will bring up I2C soon and try),
    or: use the "general registers" which would survive a system reset (I will try as well).

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • tjaekel
    tjaekel over 2 years ago in reply to michaelkellett

    I agree with you. Thank you.

    Best is: to use an external I2C flash memory (I will bring up I2C soon and try),
    or: use the "general registers" which would survive a system reset (I will try as well).

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube