Honored Contributor
Honored ContributorHello guys,
thank you for the answers! @WitFed: As you recommended, I tried to use the unhosted example design. (what does unhosted in this case exactly mean?) 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 on connection Connected to running target Altera - Cyclone V SoC (Dual Core) on TCP:localhost Execution stopped at: S:0x00000900 source /v "C:\altera\14.0\embedded\ds-5\sw\debugger\configdb\Scripts\altera_target_check.py" S:0x00000900 AND r1,r1,#7 No SYSID registers could be found. Has a peripheral description file been supplied? loadfile "C:\Repos\Unhosted-CV-GNU\hello.axf" ERROR(CMD16-TAD274-NAL22): ! 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 Start --- Usual code with Baremetal-HWLIB use semihosting/debugger before call main() and requires "finishing" of Preloader codes to simulate host in boot without host from QSPI. Your program listing must not contain asm-commands "SVC 123456", used in "hard" opening "stdin/stdout" etc. --- Quote End --- 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 Start --- These theme is periodical discussed on this forum, Altera works for simplification... --- Quote End --- 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. 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 Start --- I'm not sure, but I think that semi-hosting uses debug support code present in the preloader to support serial console I/O. DS-5 must be attached for this to work. You wouldn't want semi-hosting enabled in anything that starts without DS-5 connected I.E. code loaded in QSPI. --- Quote End --- Ahhh i got it, so I just should enable the semihost feature, when I desire to debug the preloader + application with the DS-5. When I want the application to be booted stand alone from the QSPI without debugging, I should disable this feature and select different options (like SERIAL_SUPPORT, DEBUG_MEMORY_WRITE) in the bsp-editor for prints via UART, rigth? 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? Thank you so much! Kind regards, Roland
