I ran into this and had absolutely no freaking clue what the hell was going on.
**** Build of configuration Debug for project spw_int_test ****
make all
Building target: spw_int_test.elf
Invoking: PowerPC gcc linker
powerpc-eabi-gcc -Wl,-T -Wl,../src/lscript.ld -L../../hello_world_bsp_0/ppc440_0/lib -mcpu=440 -mfpu=dp_full -o"spw_int_test.elf" ./src/helloworld.o ./src/platform.o ./src/spacewire_driver.o
../src/lscript.ld:228 cannot move location counter backwards (from fffff170 to 00000170)
collect2: ld returned 1 exit status
make: *** [spw_int_test.elf] Error 1
I ended up finding a solution here Link
Simply Change the stack and heap size to 0x400!
Sunday, October 26, 2014
lscript.ld:228 cannot move location counter backwards
Xilinx SDK Processor Folder with Includes Dissapears from BSP!
So, Just as a quick reference, if your BSP does not seem to be building the files for the processor and the normal things you have in the include folder, one of the reasons this happened to me is I was remoted in and lost connection to the license server
Thursday, September 25, 2014
Hilarious Xilinx Capitalization Error
So funny story, ran into this crazy xilinx error:
ERROR:EDK - IPNAME:[IPName] INSTANCE:IPNAME_0 - C:\Users\[location]\l.srcs\sources_1\edk\module_1\dump.mhs line 518 - Invalid ip name. IP name cannot have upper case characters.
This is that your actual IP core name cannot have any capital letters when you actually use the peripheral creation wizard. GAH!
ERROR:EDK - IPNAME:[IPName] INSTANCE:IPNAME_0 - C:\Users\[location]\l.srcs\sources_1\edk\module_1\dump.mhs line 518 - Invalid ip name. IP name cannot have upper case characters.
This is that your actual IP core name cannot have any capital letters when you actually use the peripheral creation wizard. GAH!
Sunday, September 14, 2014
14.7 PlanAhead - [Constraints 18-5] Cannot loc terminal "XX_n" at site XX; loc is blocked
So this is a pretty annoying error. The solution is detailed
here:AR# 43315
and here also discusses it: Xilinx Forums
Under the [Project Manager] on the Left side of plan ahead, go to "Implementation Settings"
Under the Section for [Translate (ngdbuild)] go to "More Options*" and type in:
-uc filelocation
^ use forward slashes / for the location like C:/Users/Xilinx/system.ucf
You MUST remove the constraints file from the project too to get the warnings to disappear.
here:AR# 43315
and here also discusses it: Xilinx Forums
Under the [Project Manager] on the Left side of plan ahead, go to "Implementation Settings"
Under the Section for [Translate (ngdbuild)] go to "More Options*" and type in:
-uc filelocation
^ use forward slashes / for the location like C:/Users/Xilinx/system.ucf
You MUST remove the constraints file from the project too to get the warnings to disappear.
Monday, September 8, 2014
Error Launching PTC Windchill Quality Solution
Error:
Could not connect to net.tcp://[host]:[port]/Relex.Security/IAccessManager. The connection attempt lasted for a time span of ##:##:##.#######. TCP error code 10061: No connection could be made because the target machine actively refused it.
When I was googling around for this error all I could get were comments on SQL server. The solution is to restart some PTC services that have been turned off:
Could not connect to net.tcp://[host]:[port]/Relex.Security/IAccessManager. The connection attempt lasted for a time span of ##:##:##.#######. TCP error code 10061: No connection could be made because the target machine actively refused it.
When I was googling around for this error all I could get were comments on SQL server. The solution is to restart some PTC services that have been turned off:
Saturday, August 16, 2014
Error: [Common 17-36] Cannot write file [project_constraints.ucf]
http://forums.xilinx.com/t5/Hierarchical-Design/PlanAhead-cannot-write-to-ucf-during-runs/td-p/271092
I ran into this when I was copying over projects and just modifying the constraints. The solution is to: A workaround for this specific issue is to uncheck "Read- only" for the UCF file that resides in the folder <project_name>.runs/impl_1/.constrs
>> 11/25 Update
Okay this also sometimes happens to me even when the Read-Only IS unchecked, when that happens, I saw one poster that deleted the folder for the run (impl_1 typically) I just made a new run and it will go.
I ran into this when I was copying over projects and just modifying the constraints. The solution is to: A workaround for this specific issue is to uncheck "Read- only" for the UCF file that resides in the folder <project_name>.runs/impl_1/.constrs
>> 11/25 Update
Okay this also sometimes happens to me even when the Read-Only IS unchecked, when that happens, I saw one poster that deleted the folder for the run (impl_1 typically) I just made a new run and it will go.
Friday, August 15, 2014
UART not responding on working SDK project and Bitstream
When you need UARTs to connect to peripheral devices as well as UARTs to the terminal, you can run into many confusing situations. In my case I was getting no UART output. One of the things that worked for me was modifying the bsp settings
See the steps below:
See the steps below:
Subscribe to:
Comments (Atom)



