[Gnuk-users] Seeedstudio website
NIIBE Yutaka
gniibe at fsij.org
Thu Jul 14 01:25:26 UTC 2016
On 04/18/2016 09:38 AM, NIIBE Yutaka wrote:
> On 04/17/2016 07:52 AM, Yui Hirasawa wrote:
>> Today I noticed that the Seeedstudio wiki now also blocks Tor. It used
>> to be that only the store blocked Tor but it looks like they've started
>> using CloudFlare for the wiki as well.
>>
>> I think it's against the interest of people using FST-01 for Gnuk that
>> they cannot access the wiki page or the store using Tor. It would be
>> better to sell open hardware in some store that respects the users more.
>
> Thank you for sharing the information.
>
> OK, I'll move the information of FST-01 and FSM-55 to gniibe.org.
Finally, I did for FST-01: http://www.gniibe.org/FST-01/fst-01.html
Please have a look. If you find any problem, please let me know. I
think I keep all the information of the original wiki page.
It took time than I had expected. I tried converting from MediaWiki,
but pandoc didn't work well.
I will do that for FSM-55, too.
Well, FSM-55 is still available at Seeed, but it's only 4 boards
remained:
http://www.seeedstudio.com/FSM-55-LED-Matrix-Display-p-2121.html
I made FSM-55 so that I can show/demonstrate things are now very much
complicated, and it's getting difficult to control things accurately.
For an engineer (who was a radio boy in 70's), dynamic control of LED
matrix should be done easily and accurately by a digital circuit of
TTL.
If the purpose is describing the method of LED matrix dynamic control,
writing in Verilog or VHDL would be the best (I mean, not in
procedural programming).
Ideally, once written accurately, next we can reuse it to go further,
like things in Mathematics. With procedural programming methodology,
it's an approximation, at best, to control I/O with timing. There can
be so many ways for an approximation. Then, people write every time
when they need.
Besides, technology changes. Even for such a small thing of FSM-55,
using 32-bit (!) MCU is cheaper to be a product. Using MCU means, we
need a software toolchain, including a compiler. (BTW, in this
spring, I learned younger generation learn LED blinking by BeagleBone
with Bonescript through Web.)
In the days of TTL, it was possible for me to decide IC vendor at the
last step of the design, thanks for the compatibility. Now, in many
cases, it should be done in rather early stage of a project.
Perhaps, this is one of the reasons why we see full of premature
products for I/O Things, now.
I know it's because of cars, we have good roads where I can ride
a bicycle. Yet, I don't need to prefer going everywhere by car.
Occasionally, I walk.
--
More information about the gnuk-users
mailing list