SPRACU8B August   2021  – January 2023 AM68 , AM68 , AM68A , AM68A , AM69 , AM69 , AM69A , AM69A , DRA821U , DRA821U , DRA829V , DRA829V , TDA4VM , TDA4VM

 

  1.   Abstract
  2.   Trademarks
  3. 1Introduction
    1. 1.1 Features
      1. 1.1.1 Supported Features (version 0.10.0)
      2. 1.1.2 Unsupported Features (version 0.10.0)
    2. 1.2 Spreadsheet Overview
      1. 1.2.1 Input Worksheets
      2. 1.2.2 Output Worksheets
      3. 1.2.3 Other Worksheets
    3. 1.3 Default SDK Configurations
  4. 2Customizing DDR Configuration
    1. 2.1 Config Worksheet
      1. 2.1.1 System Configuration
      2. 2.1.2 Memory Burst Configuration
    2. 2.2 DRAMTiming Worksheet
      1. 2.2.1 Latency Parameters
      2. 2.2.2 Non-Latency Parameters
    3. 2.3 IO Control Worksheet
      1. 2.3.1 Determining IO Settings
      2. 2.3.2 Processor/DDR Controller IO
      3. 2.3.3 DRAM I/O
  5. 3Software Considerations
    1. 3.1 Updating U-Boot
      1. 3.1.1 Updating DDR Register Settings
      2. 3.1.2 Updating Source to Set Available Memory Size
    2. 3.2 Updating RTOS PDK
      1. 3.2.1 Updating DDR Register Settings
  6. 4Troubleshoot Guide
    1. 4.1 Topics/Issues
      1. 4.1.1 Topic 1
      2. 4.1.2 Topic 2
      3. 4.1.3 Topic 3
  7. 5References
  8.   Revision History

4.1.1 Topic 1

Issue: When I try to save the register output, I receive an error that states "Run-time error '13': Type mismatch". I also observe "#N/A" for some of the register values (as shown in Figure 4-1).

GUID-423AE400-1EFC-444D-8D91-C27ED352DB1E-low.png Figure 4-1 Type Mismatch Error

Solution: Double check that all parameters which have dependencies on other parameters are set to a valid value. Dependencies are documented with "Notes" for each parameter in Section 2.

Explanation: A type mismatch error is likely due to an error in the user input. Some inputs are dependent on other inputs of the spreadsheet. As an example, the drop-down options for "Write Latency" on the "DRAMTiming" worksheet are dependent on the input of "Write Latency Set". Thus, the value selected for "Write Latency" may not be valid if the value for "Write Latency" is configured, and then the value of "Write Latency Set" is changed. As shown in Figure 4-2, the previous "Write Latency" value of "34" is no longer valid after changing the "Write Latency Set" value from "WL set B" to "WL set A".

GUID-D61A1964-E639-46A6-8ECF-E32E366793B9-low.png Figure 4-2 Type Mismatch Source