YRabbit @yrabbit@mastodon.sdf.org

``Jean-Yves Le Drian denounces "a blow in the back" after Australia broke its submarine contract.''
``France Calls U.S.-Australia Submarine Deal a Betrayal''...

What's the hysteria about, dude? Breathe deeply, it's your own routine, what are you unhappy about?
Remember the Mistrals in 2015?

I'm just kidding 😜

The guys understand security, it's good that I don't care about these keys, I'm looking for something else entirely;)

Use spell checkers when you print your books, it's easy, or there's always the possibility of running into an insane person who sees these things :)
"Linkers & Loaders" by John R. Levine

aws.amazon.com service terms
``However, this restriction will not apply in the event of the occurrence (certified by the United States Centers for Disease Control or successor body) of a widespread viral infection transmitted via bites or contact with bodily fluids that causes human corpses to reanimate and seek to consume living human flesh, blood, brain or nerve tissue and is likely to result in the fall of organized civilization.''

OK, OK, deal --- I'll take you home for the winter🙂
#plants

After the death of the NVME drive, I'm back on the air again🙂

Gee, I found that nasty unlit LED!!!

Yes, I still use paper and pen. That's more visible:)
Although it's plastic and the pen is erasable ;)

I think I'll go and paint the stools while the weather is sunny.

No, the star segment is still not lit. This probably has nothing to do with packing different registers into the same slice, but I was hoping deep down that it would be fixed:)
#yosys #fpga #gowin #apycula

Registers like DFFNPE and DFFNCE coexist in the same #gowin #fpga slice!
I'm happy:)
Need to check in the hw, it would be very unpleasant to break already working designs.

Back to DFF for a minute, my eye is hooked on something that is not quite right here :)
#fpga #gowin

Having finished with the IO buffers I am now just looking at the bits of the DFF thing I don't know. Without getting into it and without much thought I just scroll through the #fpga bit dump. And yet I have a hunch that I'm about to see the truth through these bits.

Insanity😜

Jesus! You can't write documentation like that. People from #gowin hire me, I'll proofread all the documents, I have this kind of thing:)

and, by the way, another reason why I immediately get sad at the keyboard without the number pad: the 0 key in #vim works as a jump to the beginning of the line, and since I use arrows anyway rather than hjkl, having 0 so close is just incredibly convenient😜

Victory! All these IOTs belong to bank 3 although they are on the top side of #fpga.
The previous version of the unpacker didn't understand this:)

This thing also contains errors.
Hell is real😜

The IOT pins (top) should belong to bank 0 #fpga, but some of them are marked as belonging to bank 3, which is where all the left IOL pins are located.
So I can not rely on pin coordinates, but have to use a matching table, which is not in the chip database.

I think it's time to take a break and go for a walk and see what's ripe from the veggies.
:)

Took a chance to try these blue tomatoes.
What can I say, they taste like an ordinary tomato. Not that I was expecting it to taste like an aspen mushroom, but a little disappointed:)

Gee, this is how gowin_unpack reconstructs a constraint file from a bitstream compiled with a vendor IDE :)
Never mind IOL7 --- it's a clock.
I was upset when I didn't see DRIVE attribute for R1C4, because the program should recognize all attributes, but it was smarter than me: with open collector DRIVE is out of the question :)