I recently discovered a couple of Electronics blogs - and I love them (it also helps me to reduce the number of dumb questions that I ask here on the forum ;)).
Dave Jones (EEVblog): https://www.youtube.com/channel/UC2DjFE7Xf11URZqWBigcVOQ (https://www.youtube.com/channel/UC2DjFE7Xf11URZqWBigcVOQ)
Afrotechmods: https://www.youtube.com/channel/UCosnWgi3eorc1klEQ8pIgJQ (https://www.youtube.com/channel/UCosnWgi3eorc1klEQ8pIgJQ)
mjlorton: https://www.youtube.com/channel/UCOTPsWDzNAosVd6vc3pCPHQ (https://www.youtube.com/channel/UCOTPsWDzNAosVd6vc3pCPHQ)
The Ben Heck Show: https://www.youtube.com/channel/UChturLXwYxwTOf_5krs0qvA (https://www.youtube.com/channel/UChturLXwYxwTOf_5krs0qvA)
Dorian McIntire: https://www.youtube.com/channel/UC_O_niZqGWMOUbX37gmqGHw (https://www.youtube.com/channel/UC_O_niZqGWMOUbX37gmqGHw)
w2aew: https://www.youtube.com/channel/UCiqd3GLTluk2s_IBt7p_LjA (https://www.youtube.com/channel/UCiqd3GLTluk2s_IBt7p_LjA)
What else is there? Which ones would you recommend?
I don't follow any. Not enough hours in a day. Being an Electrical Engineer I can also figure out most things I need, and just need some occasional software help.
Electronic blogs, which, for the most part , are tutorial in nature have their place. If you are new to electronics they can help get you up to speed, however, your endgame goal should be to learn how to properly research your project , without resorting to blogs or Vlogs. Obviously, having a BSEE pretty much means you either know the information already or you know where to find it. Speaking as a technician, rather than an engineer, with only a 3-yr degree (BSEET: Bachelor of Science of Electronic Engineering Technology), I would say that close to 90% of what you need to know in electronics can be found in datasheets, and another 5% can be found in App Notes. What can't be found in datasheets and app notes can probably found with Google. As a general rule, I would say that reading tutorials and blogs is not a substitute for knowing how to read a datasheet. Tedious though it is, (especially when you get into how to read registers in an I2C chip) it is nevertheless far more productive to wade through a long datasheet (like the ATmega328 datasheet (629 pages) ) until you have overcome your fear of reading datasheets , than to spend all your time watching tutorials (unless they are about how to read datasheets). I would suggest reading the section about the Timers.
16.3 Accessing 16-bit Registers
The TCNT1, OCR1A/B, and ICR1 are 16-bit registers that can be accessed by the AVR CPU via the 8-bit data bus. The 16-bit register must be byte accessed using two read or write operations. Each 16-bit timer has a single 8-bit register for temporary storing of the high byte of the 16-bit access. The same temporary register is shared between all 16-bit registers within each 16-bit timer. Accessing the low byte triggers the 16-bit read or write operation. When the low byte of a 16-bit register is written by the CPU, the high byte stored in the temporary register, and the low byte written are both copied into the 16-bit register in the same clock cycle. When the low byte of a 16-bit register is read by the CPU, the high byte of the 16-bit register is copied into the temporary register in the same clock cycle as
the low byte is read.
Head spinning ? Getting dizzy ? Feel like your banging your head against the wall ?
Enter the Application Note (http://www.atmel.com/images/doc2505.pdf)
Still confused ?
Time to turn to Google.
Google search (https://www.google.com/#q=ATmega328+timer+example+code)
tutorial found using google (http://www.engblaze.com/microcontroller-tutorial-avr-and-arduino-timer-interrupts/)
Does this make more sense ?
We've set Timer1 to interrupt on an overflow, and let's assume we're using an ATmega328 with a 16MHz clock. Since Timer1 is 16 bits, it can hold a maximum value of (2^16 - 1), or 65535. At 16MHz, we'll go through one clock cycle every 1/(16*10^6) seconds, or 6.25e-8 s. That means 65535 timer counts will elapse in (65535 * 6.25e-8s) and our ISR will trigger in, oh… about 0.0041 seconds. Then again and again, every four thousandths of a second after that. Oops. At this rate, we probably won't even be able to detect blinking. If anything, we've created an extremely fast PWM signal for the LED that's running at a 50% duty cycle, so it may appear to be constantly on but dimmer than normal. An experiment like this shows the amazing power of microprocessors - even an inexpensive 8-bit chip can process information far faster than we can detect.
Tutorial #2 found using Google (http://www.avrfreaks.net/forum/tut-c-newbies-guide-avr-timers?page=all)
For all practical purposes you will be an electronics cripple until you have gotten to the point where you are ready and willing to jump into an unknown datasheet feet first , rather than spend all night googling for tutorials on how to use the chip.
In short, there is a special HELL for people who don't read datasheets. It is a place where nothing works and everything smokes when you turn on the power...