You can see the disk information using a command like !df -h. To see CPU specs, !cat /proc/cpuinfo. For memory, !cat /proc/meminfo. Here’s an example notebook: https://colab.research.google.com/notebook#fileId=1_x67fw9y5aBW72a8aGePFLlkPvKLpnBl Edit: Colab now offers a Pro version which offers double the amount of disk available in the free version.
WaveDrom is a free and open source online digital timing diagram rendering engine that uses JavaScript, HTML5 and SVG to convert WaveJSON input text description into SVG vector graphics.
RFID Standards: 125 Khz (low-frequency) tags are write-once/read-many, and usually only contain a small (permanent) unique identification number. 13.56 Mhz (high-frequency) tags are usually read/write, they can typically store about 1 to 2 kilbytes of data in addition to their preset (permanent) unique ID number. 860-960 Mhz (ultra-high-frequency) tags are typically read/write and can have … Read more
In older architectures, peripherals were accessed via a separate mechanism to memory access with special I/O instructions. On x86, there were (and still are!) “in” and “out” instructions for transferring bytes between the CPU and a peripheral. Peripherals were given addresses, for example 0x80 for the keyboard. Simplifying a lot, doing “in 0x80” would read … Read more
In short: left arrow: 37 up arrow: 38right arrow: 39down arrow: 40
I investigated the same question a while back. After chatting to people who have worked on FPGAs, this is what I get: FPGAs are great for realtime systems, where even 1ms of delay might be too long. This does not apply in your case; FPGAs can be very fast, espeically for well-defined digital signal processing … Read more