I'm using De0-nano-soc & De1-soc from Terasic .. neither has soc_system_board_info.xml & hps_common_board_info.xml included in the packages that arrived & Terasic is claiming their linux sources are proprietary (?? maybe i'll sic the EFF on them ..) so I've been using cv_soc_devkit_ghrd version is this going to be 'mostly ok' ?? has anyone fine tuned these files for these boards ? having pains trying to get a compile of linux complete&running but that is a post for another thread ...

partially functional -- now stuck at loading kernel .... just more digging involved ....

Hey Ralph, I'm interested in hearing how you go with this board. I have the DE0-nano-SoC and the Arrow SoCkit (which is also a Terasic board). I'm interested in understanding how to build everything from source, i.e, downloading source code from a git repo while not having to hack the source for these particular boards. I also noticed that the DE-nano-SoC code was not easily available and the documents were pretty vague with respect to building the SoC system and Linux code. I figured I'd start with the SoCKit, and then go back to the DE0-nano-SoC once I was familiar with the tool flows. I haven't had a chance to dive into the HPS side of things yet, I started on the FPGA-side, since I was comfortable there :) Cheers, Dave

Hey Dave, Yes, started with the FPGA side a while back (was going to be De0-Nano (Cyclone4) with a external CPU (BeagleBoard)) but flipped over the the De0-Nano-SoC due to space/timing & ram issues -- so 95% of my fpga work is done -- mostly have to worry about Fpga2sdram interface really are living in minimal documentation land here ... (or there is too much & difficult to filter ...) ... with any luck - be booting soon... (tonight ??!?) hiho R

--- Quote Start --- really are living in minimal documentation land here ... (or there is too much & difficult to filter ...) --- Quote End --- Yes, I've found there to be a lot of documentation, but most of it is not well written. For example, "How do you create pin assignments for the HPS pins?" would be an obvious question to someone familiar with FPGAs. Its not obvious that the HPS pin assignments are a result of pin settings in the component instance (and are configured by the preloader). I'm not sure whether I have ever seen it stated in an Altera doc, I think I made that realization while watching a tutorial. --- Quote Start --- ... with any luck - be booting soon... (tonight ??!?) --- Quote End --- Good luck! Cheers, Dave

update : booting . but not really or i should say not completely on my own // i can create all it parts kernel/zImage/rootfs / boot.scr, soc_system.rbf, preloader-mkpimage.bin but it only boots if i use the socfpga.dtb from the sdcard that came with it (posted on the terasic site) .. . i have followed suggestions / remove second WDT, drop/disable peripherals in the soc_system.sopcinfo i have converted / modified/ loaded generated dts files i have unconverted the working blob to text& re'blob'ed it .. & it still boots / all others hang at "loading kernel ...." I've requested any board*info.xml from Terasic -- they do provide a version for the De1-SOC so it should not be a stretch for them to pass it on --- obviously the original device tree does me no good it does not support the peripherals i've created feeling some what stymied

soc_system_board_info.xml/hps_common_board_info.xml common accross most devboards ?

13 Replies

Altera_Forum
Honored Contributor
10 years ago
--- Quote Start ---
Hey Dave,
-- mostly have to worry about Fpga2sdram interface
--- Quote End ---

Ralph-

Any luck getting the FPGA2SDRAM interface running? I found a bug in how sopcinfo files are processed from Qsys that I've reported to Altera, but I haven't been able to get it working unless there are significant preloader changes required. I'd love to know if I'm missing something simple.
Altera_Forum
Honored Contributor
10 years ago
--- Quote Start ---
Ralph-

Any luck getting the FPGA2SDRAM interface running? I found a bug in how sopcinfo files are processed from Qsys that I've reported to Altera, but I haven't been able to get it working unless there are significant preloader changes required. I'd love to know if I'm missing something simple.
--- Quote End ---

I've had to take a (3 month) break from that section of my code (family stuff ) back into it shortly //
currently working through MY modifications of the WS3DevelopingDriversForAlteraSoCLinux code to understand a bit better & to get my head back into that space
spare time is at bit of a premium these days ...
Altera_Forum
Honored Contributor
10 years ago
--- Quote Start ---
I've had to take a (3 month) break from that section of my code (family stuff ) back into it shortly //
currently working through MY modifications of the WS3DevelopingDriversForAlteraSoCLinux code to understand a bit better & to get my head back into that space
spare time is at bit of a premium these days ...
--- Quote End ---

I know that feeling...instead of debugging the interface we switched to using an on-chip FIFO until we have a week or so of time for debugging. Good luck!

Forum Discussion

soc_system_board_info.xml/hps_common_board_info.xml common accross most devboards ?

13 Replies

Recent Discussions

Dual Port Nios V BSP error

set_output_delay explained for dummies

[Test only]How to verify Agilex 3 in radiation tolerant environment

gdb server problem when debugging

Nios IDE CPU Detection