We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I've been fooling around with memory settings and now I get this error when linking: CODE( 0X0000-0XFFFF , OX80) XDATA( OXOOOO-OXFFFF, OX1000) *** FATAL ERROR L236 : ADDRESS IS NOT IN ASCENDING ORDER POS: 176 arget\Lib\FX2\Ezusb.lib TO FW RAMSIZE (256) CODE (OXOOOO-0XFFFF, OX80)
What are the default settings to solve this issue?
Ok, I finally got it. Here are the settings if someone needs them. On the Target Options windows: target tab Offchip settings must be blank.
BL51 locate tab Code Range 0x80-0x0FFF XData Range 0x1000
When I read your error messages, it seems like you are mixing the digit zero with capital o.
The XDATA information isn't specified using digits...
Yeah, my zeroes are Caps os, but it is just in this post, not in my compiler. Sorry for that
"BL51 locate tab Code Range 0x80-0x0FFF XData Range 0x1000"
The figures should be arranged for each case.
- Overlap of CODE and XDATA is not allowed. For Cypress EZ-USB FX series, CODE and XDATA space share the same XRAM space.
- The boundary between CODE and XDATA space 0x1000 is not the fixed number. The required CODE size determines the boundary.
- Keil Mon51 monitor for uVision The code for Mon51 occupies CODE and XDATA spaces. The start address of the CODE range, 0x80, prevents address conflict with the monitor code. Check the map file (.M51) of the monitor code. C:\Cypress\USB\Target\Monitor\ For FX2(LP), mon-ext-sio1-c0.hex is the default monitor. If you don't use mon51, this setting for CODE is not required.
Tsuneo