Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quiet option switch #73

Closed
eblot opened this issue Jan 29, 2021 · 4 comments
Closed

Quiet option switch #73

eblot opened this issue Jan 29, 2021 · 4 comments

Comments

@eblot
Copy link

eblot commented Jan 29, 2021

Would it be possible to add a --quiet option switch so that openFPGALoader does neither emit:

  • = progression chars on stderr
  • completion %-age on stdout
    This would be very useful to use it in unattended context (such as CI/CD), as it generates a large amount of text which makes the output harder to parse and not useful it this kind of context.

Thanks a lot for this tool, it seems to overcome many limitations encountered with xc3sprog, it is a pity it is much harder to find for now. I hope it will soon move up in search ranks!

@trabucayre
Copy link
Owner

Would it be possible to add a --quiet option switch so that openFPGALoader does neither emit:

* `=` progression chars on stderr

* completion %-age on stdout
  This would be very useful to use it in unattended context (such as CI/CD), as it generates a large amount of text which makes the output harder to parse and not useful it this kind of context.

Yes of course. What is the required level of quiet (just progressBar or everything?)

Thanks a lot for this tool, it seems to overcome many limitations encountered with xc3sprog, it is a pity it is much harder to find for now. I hope it will soon move up in search ranks!
Thanks! I know I need to improve my communication ... :)

@eblot
Copy link
Author

eblot commented Jan 29, 2021

It think it is ok to have the info and steps, but progression (both as bars and percentage) generates a lot of lines. I'd say, everything that requires emitting a CR / \r char :-)

I know I need to improve my communication ... :)

:-) I had a hard time finding this tool w. google, which is really a pity.

BTW, unrelated question: I'm using an Arty-A7 100T, sending the bitstream to RAM (not SPI flash). I'm a newbie with FPGAs but what does the "erase" step do when using RAM?

@trabucayre
Copy link
Owner

I've pushed this feature. It's okay for you ?

:-) I had a hard time finding this tool w. google, which is really a pity.
I know except for twitter I haven't done anything to promote this tool (and to improve search rank)... @Martoni has done more in this topic (blog + french magazine) than me.

BTW, unrelated question: I'm using an Arty-A7 100T, sending the bitstream to RAM (not SPI flash). I'm a newbie with FPGAs but what does the "erase" step do when using RAM?

RAM must be blank before loading a new bitstream. This force the FPGA in a specific state and start with the new content.

@eblot
Copy link
Author

eblot commented Jan 30, 2021

Perfect! Thanks a lot.
Thanks also for the explanation of the flashing steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants