--- Quote Start ---
@WitFed:
As you recommended, I tried to use the unhosted example design.
(
what does unhosted in this case exactly mean?)
--- Quote End ---
In Unhosted not used semihosting: ARM standard for using host resources (stdin, stdout, filesystem through JTAG), search ARM site for API for "SVC 123456":
http://infocenter.arm.com/ with "What is semihosting?".
--- Quote Start ---
I have built the project as it is, configured the debugger and tried to debugg the "hello World", but a weired error occurs (I have added the MAX V in the JTAG chain - but it should have no influence in debugging the HPS, it is just for monitoring and configuring the FPGA, right? ) :
"Stopping running target Altera - Cyclone V SoC (Dual Core) on TCP:localhost !
...
Failed to load "hello.axf"
! Failed to write 15.048 bytes to address S:0x00100040 while writing block of 4.096 bytes to address S:0x00100040
! General error on memory or register access."
--- Quote End ---
Last error may be for situation if onboard SDRAM is not initialized in Preloader and is inaccessible.
MAX V not used by my (this only FPGA-boot mechanism, current project works without FPGA configuring), only DS-5 debugger direct to HPS-JTAG, FPGA-JTAG is in chain "just in case".
Try set jumpers C-B-SELs to R-R-L-R-L, my board debugs this example successful.
You use COM-port to see output of Preloader and "Hello World!\n" from Linux, Preloarers and Unhosted example ?
--- Quote Start ---
I am not exactly sure what you mean by this statement. Do you mean that the preloader is loaded into the OCRAM by the debugger, then the debugger waits for the preloader to be finished. That is all that i get, sry.
--- Quote End ---
I "kill" 2 months to get the understanding of boot process in this perversion-maded SoC.
Semihosting is awry maked interface used in HWLIB by inherit ARM works, without host and debugger it demand homemade instruments for hold "SVC 123456" in Preloader and bypassing it back without hang.
Debugger of DS-5 "wonderful" hold interrupt 2 from "SVC 123456" command without call handler, send request through JTAG and back, and without "semihostong true" or debugger (from power-up working) if Preloader not handle 2th line, all is hang.
--- Quote Start ---
I really can image that, but I could not find any step-by-step user guide for my case. My problem is that I am new to the ARM and Eclipse world and I am used to work with Visual Studio and AVR Studio, so generally I don't care about linker scripts and writing/modifing Makefiles in first place.
--- Quote End ---
I have analogical problems, scream here very long -- a wild democracy will continued ! :)
--- Quote Start ---
so i am interessted in the steps that i need after generating the preloader with the bsp-editor to a running "hello world" on the arm-0 processor.
that should not be that difficult, right? --- Quote End ---
Yes, only I forget my June-works, if need be retry, will tri again :)
Mafiable system hide good knows and shove to Linux !
--- Quote Start ---
...and select different options (like SERIAL_SUPPORT, DEBUG_MEMORY_WRITE) in the bsp-editor for prints via UART, rigth?
--- Quote End ---
This is settings only for Preloader, to running application of 3rd stage is not influenced.
Key options is boot from QSPI and no wathDog -- if planned Debugger connection "to live".
--- Quote Start ---
As I already mentioned, I am still facing the problem with debugger... Might it be a problem with my board setup?
Or do I have to do some adaptions in the "unhosted" example?
--- Quote End ---
For beginning try without modifications and with "normal" default jumpers for boot from SD-card.
You must see in Disassembler window effect of "semihosting false" for any HWLIB-application and hang.
I "cure" a Preloader with add "while (1) ;" before starting 3th stady, connect to it after power-on, shift PC to next line and debug further process of hangs. In Russian my results present in
electronix.ru (
http://electronix.ru/forum/index.php?showtopic=121400).
In Unhosted no calls of "SVC 123456", it will only binarize to 200000 asress, fill right to QSPI and see output to UART.
Honored Contributor
