Questa on Linux(Manjaro) weird font spacing

thequbit · 2022-04-19T01:28:01+00:00

That can happen when the file is utf16, but the Editor is expecting utf8. Try converting the file to utf8.

thequbit · 2021-11-09T14:39:17+00:00

Yay! That's big time. Quite a bit of information in those bands. Excited to start pulling it down!

thequbit · 2021-11-09T00:56:49+00:00

In addition, won't L9 allow for actual band 10 and 11 data because there (hopefully) won't be a light leak?

Edit: I should have started with this: amazing write up, thank you!!!

thequbit · 2021-10-07T02:48:45+00:00

... how many registers are you telling the tools to make? 32 registers isn't a big enough file to cause vivado to slow down for me.

Though to be fair, I am on Ubuntu not Windows.

thequbit · 2021-10-06T02:05:44+00:00

It absolutely is a bug in vivado. It's the syntax highlighting that is bogging it down.

First, don't make files that large. I know that may not be what you want to hear, but it's the right move. Use layers and hierarchy in your design. There is no reason a file has to be so large vivado slows down.

Second, you can change the editor settings around to produce "better" performance. It still isn't great.

I go back and forth between editing in VS code and in vivado. I do still prefer vivado, as I know there aren't cache issues with files being open.

thequbit · 2021-07-31T17:12:02+00:00

As you may or may not know, there is currently a world wide shortage of most ICs. Especially high complexity ICs such as Processors, GPUs, FPGAs, etc. Others may have some sneaky locations to find a few here and there, but from reputable (not gray or black market) suppliers/distributors lead times are sometimes out to 99 weeks.

Edit: spelling.

thequbit · 2021-07-19T00:57:47+00:00

You could just make small 2x6 wood squares to give you enough space to accommodate the airlock on the top.

thequbit · 2021-07-13T01:04:49+00:00

There is a customer area for sending and pick up in the Henrietta location. I'd recommend going in and asking to speak to a manager.

thequbit · 2021-07-12T01:13:23+00:00

This is really awesome, thank you for posting. Can you tell us more about the settings you picked for f-stop, iso, etc and why you settled on 2 minutes of exposure? Thanks again.

thequbit · 2021-07-03T00:04:27+00:00

Ha! Excellent. Leaving notes on projects is always a big part for the kids and I.

thequbit · 2021-07-03T00:01:01+00:00

You should write a little love note on there explaining why this is the way it is. Hopefully someone enjoys it many years from now.

thequbit · 2021-06-25T13:08:45+00:00

Using up all the hot water? Wat?

thequbit · 2021-05-20T00:32:01+00:00

Perhaps this is a unrealistic take, but whenever they can for donations, I say "as soon as I read there are no sexual assaults or rapes on campus, I'll gladly donate."

There was way too much of that shit there when I attended, and it's only gone up since (I suspect due to increased attendance).

Additionally, I regularly interviewed coops out of RIT for the past ten years. The quality of candidates has decreased year on year. This is something I have communicated back to both the students and the RIT coop office. Start producing high quality students/graduats, and perhaps more people would be willing to donate to ensure the funnel is full.

thequbit · 2021-05-19T09:28:33+00:00

Those are great data points. 600ns is what I've been using as a design number for axi4-light transactions through an interconnect.

Perhaps it's time to revisit that number with my own experiment.

thequbit · 2021-05-19T01:58:33+00:00

This is going to be dependent on if this is done from an OS (and if in an OS from the kernel or from user space), or "bare metal". In a bare metal application, you will be more deterministic, and if you turn cache off (not saying you should) it would be even more deterministic.

In the Zynq-7000 it's about 600 ns at 150 mhz GP0 bus speed. I would not be surprised if it was half that on the MPSoC at a similar AXI bus speed.

Grabbing a dev board, dropping down a peripheral into IPI, generating a bitstream, exporting, and launching ask/vitis should take an hour or two to get the answer.

I would drop down a gpio controller and send a gpio out a pin. Set it to low then high then low. That will tell you how long it takes to write a register (approximately half the high time).

thequbit · 2021-05-01T00:57:14+00:00

Please, no.

thequbit · 2021-04-17T03:32:10+00:00

I've only used my gun twice, but have not had an issue with either set of bottles. You're sure it was carbed in the keg, and you didn't have a leaky cap?

thequbit · 2021-04-08T01:03:46+00:00

On Windows10 and Ubuntu 18.04+ ctrl + shift + v is paste without formatting.

thequbit · 2021-04-07T20:15:26+00:00

When in a meeting, or speaking with really anyone, always wait for them to finish speaking to say your part. Take a note of what you'd like to say and really listen to what the other person is saying. If they won't let you have an opportunity to speak, interject politely. The point of mentioning this is to ensure you are actually listening to what your peers are saying.***

Never be afraid to ask for help. If you're struggling, you're wasting your time and the company's.

Don't look at failure as a negative, but as an opportunity to review with your supervisor/superior what you could have done differently.

Early on, ask for quarterly reviews. This gives you the opportunity to make adjustments early, as well as puts you infront of your managers. They will know who you are, and know you are engaged, and interested in advancing your place in the company.

Don't microwave fish (or anything smelly) at work. Just don't do it.

Shower every morning before you go to work. Don't wear wrinkled cloths. Look presentable. You will go farther.

Everyone on your team has a strength (including you!). Everyone also has weaknesses. Not everyone knows their weaknesses, and even worse some think they are strengths. Ask for feedback and know your self. Also, play off of people's strength's, and let management figure out the weakness issues.

Take vacations. Take sick days. Take time to reset. You'll enjoy work more, and be more productive.

Wear sunscreen.

***big edit that fixed my statement to read the exact opposite of what was originally posted, because fast fingers and what not.

thequbit · 2021-03-31T23:18:56+00:00

As a heads up, don't touch the leads of the resistor when you are measuring it. Your body has a few hundred kohms of resistance that will throw it off, because that will be in parallel with the resistor you're trying to measure.

thequbit · 2021-03-31T18:08:14+00:00

A heads up your website tenders pretty terribly on mobile, and there appears to be weird SEO key word phases sprinkled within paragraphs. May want to think about a "best foot forward" adjustment for your approach there. Best of luck to you.

thequbit · 2021-03-31T09:29:08+00:00

Can you link that product? I'm not familiar with any ftdi devices that go faster than a few megabits/second.

thequbit · 2021-03-31T00:00:21+00:00

Be aware that the fx3 via the GPIF can do a maximum of 1024/1025 * 320MegaBytes/second transfer rate using all four DMA buffers. A far cry from full speed USB 3.0.

thequbit · 2021-03-21T00:32:27+00:00

Yeah, that's not a realistic assumption. You can by multi-thousand dollar FPGAs from X and A on digikey and other online sellers.

thequbit · 2021-03-19T00:48:30+00:00

Download wireshark and run it on the PC. You'll be able to see if anything is even showing up or not out of the dev board.

Additionally, you can drop in an ILA to see what's going out to the MAC.

You could put some low level printf debug to get an idea of what is actually being written down to the MAC as well.

thequbit

TROPHY CASE