Analog.com Analog Dialogue Wiki 简体中文
EngineerZone
EngineerZone
  • Log in
  • Site
  • Search
  • Log in
  • Home
  • Blogs ⌵
    • EngineerZone Spotlight
    • The Engineering Mind
    • Analog Garage
  • Browse ⌵
    • All Groups
    • All Members
  • Support ⌵
    • 3D ToF Depth Sensing
    • Amplifiers
    • Analog Microcontrollers
    • Audio
    • Clock and Timing
    • Data Converters
    • Design Tools and Calculators
    • Direct Digital Synthesis (DDS)
    • Embedded Vision Sensing
    • Energy Monitoring and Metering
    • FPGA Reference Designs
    • Industrial Ethernet
    • Interface and Isolation
    • Low Power RF Transceivers
    • MeasureWare
    • MEMS Inertial Sensors
    • Motor Control Hardware Platforms
    • Optical Sensing
    • Power By Linear
    • Processors and DSP
    • Reference Circuits
    • RF and Microwave
    • Switches/Multiplexers
    • Temperature Sensors
    • Video
    • Wireless Sensor Networks Reference Library
  • My EZ
  • More
  • Cancel
Hardware Tools
  • Processors and DSP
  • Software and Development Tools
  • Hardware Tools
  • More
  • Cancel
Hardware Tools
Documents FAQ: Reading to/Writing From/Loading to SDRAM on older BF533 EZ-KIT Lite with VisualDSP++ 5.0 behaves incorrectly
  • Q&A
  • Discussions
  • Documents
  • File Uploads
  • Video/Images
  • Members
  • Tags
  • Reports
  • More
  • Cancel
  • New
Hardware Tools requires membership for participation - click to join
  • Documents
  • FAQ – Can’t connect to target via emulator after upgrading to CCES 1.1.0
  • FAQ – What does the Status LED on the ICE-1000 and ICE-2000 indicate?
  • FAQ – Why do the higher JTAG/SWD frequencies not work on my emulator?
  • FAQ: Can I use the Stand Alone Debug Agent board with my custom board?
  • FAQ: Can we connect EI3 SDP Breakout Board and New DSP EZ-KITs ?
  • FAQ: Can’t connect to the ADSP-BF592 or ADSP-BF506F EZ-KITs after upgrading to CCES 1.1.0
  • FAQ: Drivers for ADSP Blackfin dev kits for Windows 10
  • FAQ: EZ-KIT licensing
  • FAQ: How do I program flash on my target board using CrossCore Embedded Studio?
  • FAQ: How do you solve "EZ-ICE Driver (Fatal Firmware Error 174)" error?
  • FAQ: How to debug a target board which boots from Flash using CrossCore Embedded Studio
  • FAQ: How to set the JTAG TCLK Frequency?
  • FAQ: I cannot find the Target Configurator or ICE Test Utility in CrossCore Embedded Studio
  • FAQ: I have a faulty Emulator/EZ-Kit. What do I do?
  • FAQ: I have an EZ-KIT Lite, but cannot find any example code in the VisualDSP++ installation. Where are these examples?
  • FAQ: ICE-1000/ICE-2000 detected as an ICE-100B after working with VisualDSP++ 5.1.1
  • FAQ: My application behaves incorrectly when using SDRAM.
  • FAQ: Reading to/Writing From/Loading to SDRAM on older BF533 EZ-KIT Lite with VisualDSP++ 5.0 behaves incorrectly
  • FAQ: Target Connection Errors after writing to flash
  • FAQ: What are Board Support Packages?
  • FAQ: What examples are included in the Board Support Packages and CrossCore® Embedded Studio?
  • FAQ: What is the cause of a "Core fault detected before halt at address" error message?
  • FAQ: What is the difference between an EZ-KIT and EZ-BRD?
  • FAQ: What is the recommended temperature range for your EZ-Kits and Emulators?
  • FAQ: Where can I find more information on the ADSP-BF609 EZ-KIT Lite/EZ-Board
  • FAQ: Where can I obtain information regarding the layout and gerber files of my EZ-Kit board
  • FAQ: Where can I obtain the schematics for the BF537 STAMP board?
  • FAQ: Why do flash contents appear corrupt/incorrect within Memory Window
  • FAQ:  How can I test for faulty connections between my ICE and Target Board?
  • FAQ:  How do you connect to an ADSP-218x EZ-KIT in VisualDSP++ 3.5?
  • FAQ:  What is the cause of the Target Connection Error 0x80004005 or 0x80044005?
  • FAQ:  What is the difference between the ADDS and ADZS part numbers?
  • FAQ:  Where can the revision details of my EZ-KIT board be found?
  • FAQ:  Why are certain portions of my EZ-KIT Lite schematics missing or not shown?
  • FAQ:  Why do the ADSP-218x DSPs have their own EZ-ICE emulator?
  • FAQ:  Why does the ICE Test pass but IDDE cannot connect to target?
  • HARDWARE TOOLS SUPPORT COMMUNITY
  • Introducing the ADZS-ICE-1000 and ADZS-ICE-2000 Emulators

FAQ: Reading to/Writing From/Loading to SDRAM on older BF533 EZ-KIT Lite with VisualDSP++ 5.0 behaves incorrectly

Question

I am unable to correctly access/load to SDRAM on an older BF533 EZ-KIT Lite. Reading or writing SDRAM produces incorrect values or corrupted data, while loading code into SDRAM fails. Why is this?

==========================================

Answer

Due to high customer demand and the low cost of memory the SDRAM on the BF533 EZ-KIT changed between board revs 1.6 and 1.7. The ADSP-BF533 EZ-KIT with board revision 1.6 and older has 32MByte of SDRAM whereas board revision 1.7 and newer has 64MByte of SDRAM.

This change in size requires a change in the EBIU_SDBCTL register setting. For the older 32MB part it should be set to 0x13, while the 64MB SDRAM requires that the EBIU_SDBCTL is set to 0x25.

CrossCore Embedded Studio and VisualDSP++ 5.0 use default EBIU_SDBCTL values for the 64MB part. This means that customers using the older boards will experience issues accessing SDRAM if the EBIU configuration is not changed. VisualDSP++ 5.0 and CrossCore Embedded Studio support Custom Board Support Files. These are XML files which you associate with a particular Session within the IDDE, and allow you to define some register reset definitions to override those in the default file in "...\System\Archdef\". You can find more information about this approach in the Help system:

[VisualDSP++] VisualDSP++ Help under ‘Help’->’Contents’->’Graphical Environment’->’Custom Board Support’.

[CrossCore Embedded Studio] CCES Help under ‘Help’->’Contents’->’CrossCore Embedded Studio 1.0.x’->Integrated Debug Environment->Debugging Executable Files->Run/Debug Configurations Dialog Box->Custom Board Support Tab->Enabling Custom Board Support

Up to, and including, VisualDSP++ 4.5 the default EBIU_SDBCTL register value was for the 32MB part, and customers with revision 1.7 of the EZ- KIT who use the 'Use XML Reset Values' option must ensure that they have the correct SDRAM values set in ADSP-BF533-proc.xml. The settings for both revisions are contained in the xml file but the rev 1.6 settings are enabled by default. This file can be edited; however you should be aware that it is susceptible to being overwritten when an update is applied to your VisualDSP++ installation.

Attached are Custom Board Support files for both VisualDSP++ 5.0 and CrossCore Embedded Studio with the BF533 rev 1.6 and older (32MB) settings configured.

[VisualDSP++] In VisualDSP++ you can then associate the file with your session via 'Settings'->'Session'.

[CrossCore Embedded Studio] In CrossCore Embedded Studio you can associate the files with your session by going to the “Custom Board Support” tab for your Debug Configuration under ‘Run’->’Debug Configurations’.

Attachments:
CCES_Custom_resets.zip
VDSP_Custom_resets.zip
  • ezkit
  • xml_files
  • visualdsp++
  • build_env
  • ice_kit
  • Share
  • History
  • More
  • Cancel
Comments
Anonymous
Related
 
Social
Quick Links
  • About ADI
  • Partners
  • Analog Dialogue
  • Careers
  • Contact us
  • Investor Relations
  • News Room
  • Quality & Reliability
  • Sales & Distribution
  • Analog Garage
Languages
  • English
  • 简体中文
  • 日本語
  • Руccкий
Newsletters

Interested in the latest news and articles about ADI products, design tools, training and events? Choose from one of our 12 newsletters that match your product area of interest, delivered monthly or quarterly to your inbox.

Sign Up
Switch to mobile view
Analog Logo
© 1995 - 2019 Analog Devices, Inc. All Rights Reserved 沪ICP备09046653号
  • ©
  • 1995 - 2019 Analog Devices, Inc. All Rights Reserved
  • 沪ICP备09046653号
  • Sitemap
  • Privacy & Security
  • Privacy Settings
  • Terms of use
EngineerZone Uses cookies to ensure you get the best experience in our community. For more information on cookies, please read our Privacy & Security Statement.