Forum Replies Created
January 7, 2019 at 7:49 PM in reply to: Hobby Components Altera USB Blaster frequently causing bsod during flashing #24647
Boosting this in the hope for generic or specific advice from the community.December 30, 2018 at 8:08 PM in reply to: Hobby Components Altera USB Blaster frequently causing bsod during flashing #24534
Suggestions on a non ‘cheap’ model I should purchase if that’s the case?
I am having exactly the same issue.
I have compiled the v.80 firmware, with the ENABLE_AUDIO=y flag, yet on my tv I get no audio over hdmi.
There appears to be activity over the I2s, Can anybody suggest some points to check on the v1.6 board? I can’t find that board’s documentation (I am just returning to this project after some time off). Please help!
Can you answer the specific questions ?
Q1/How should I know that I could use those pins, given the schema in my first post and the pin planner in the ossc project. I find it very hard to determine that those pins are indeed free.
Pin 28 for example says SD_DAT2 — What does this mean? Why is it there? If they are not used in SPI mode, then why are they labelled as in use on the schema? Are you now saying Should I just ignore that? How am I supposed to know what is what?
How should I know that I could use those pins, given the schema in my first post and the pin planner in the ossc project, I find it very hard to determine that those pins are indeed free. Pin 28 for example says SD_DAT2 — What does this mean? Why is it there? Should I just ignore that? How am I supposed to know what is what?
Am i right in saying marqs:
6 – input/output
12 – input
13 – input/output
24 – input
126 – input
Are those pins OK? Any others?
Any thoughts on this? Does it look right?
Understood nmalinoski. But I really still would like to see it, of course in a new OSSC board revision. Please help @marqs, I can help design it.
Hi nmalinoski, I understand and here you, but all of your suggestions completely undermine the purpose and simplicity the ossc delivers.
@marqs what are your thoughts on this one?
Thanks for your help borti, moving forward now.
I am now almost getting the project compiled by using the codelite workspace. Near the end of the makefile, it tries to run:
#ifneq ($(DISABLE_STACKREPORT),1) # @bash -c "$(STACKREPORT) $@" #endif
(Note i had to comment it out). If left uncommented, I get :
"/usr/bin/bash: nios2-stackreport: command not found"
The /intelFPGA_lite/17.1/nios2eds/bin/ directory with file nios2-stackreport is on my path, but maybe appears to be a perl script, perl is also on my path! Any ideas?
Ok thanks for your help – got the JTAG working.
Now my question is…..if i make a change in say software/sys_controller/ossc/av_controller.c, what steps do I need to do to compile this change into the firmware which I will flash to my device?
I have done:
1/Make coding change
2/Go into Quartus Prime and select Start Compilation
3/Compilation completes, open programmer and flash
Doing this — I do not see my coding change taking place. I feel like perhaps I need to compile the C software. I have seen there is a makefile in the software dir, however when I run make on this, I get the following error – suggesting that Quartus Prime does indeed handle the compilation of the c source….any thoughts?
Info: Building ../sys_controller_bsp/
make –no-print-directory -C ../sys_controller_bsp/
Makefile not up to date.
../../sys.sopcinfo has been modified since the BSP was generated.
Generate the BSP to update the Makefile, and then build again.
To generate from Eclipse:
1. Right-click the BSP project.
2. In the Nios II Menu, click Generate BSP.
To generate from the command line:
nios2-bsp-generate-files –settings=<settings file> –bsp-dir=<target bsp files directory>
make: *** [public.mk] Error 1
make: *** [../sys_controller_bsp/-recurs-make-lib] Error 2
When it didn’t work for you – did you get the same error I did?
As far as I can see this version of Quartus Prime is just the Signal Tap Logic Analyzer, is that the equivalent of the Quartus Prime Lite Edition 17.1 I had downloaded?
I am also running this under Ubuntu, so I could try an older version there I suppose.