Arduino

From Braindump
Jump to navigation Jump to search

arduino uno

esp32

doit esp32 dev kit v1 921600 80Mhz

robot

BN: Unknown board VID: 1A86 PID: 7523 SN: Upload any sketch to obtain it

http://learn.makeblock.com/en/makeblock-orion/


arduino generics

https://www.instructables.com/id/Arduinolyzerjs-Turn-your-Arduino-into-a-Logic-Anal/

http://www.circuitbasics.com/arduino-ir-remote-receiver-tutorial/

https://www.arduino.cc/en/Tutorial/DueSimpleWaveformGenerator

Speedo

http://karman.cc/blog/descargas/schematic.png


General

http://arduino.cc/en/Main/ArduinoBoardUno

Arduino Uno Faq

Arduino Uno

ATmega328 @ 16 MHz

1024 bytes eeprom

32 KB Flash

http://www.atmel.com/dyn/resources/prod_documents/doc8161.pdf

optiboot bootloader (115200 baud, 0.5 KB).

2.1mm center-positive plug into the board's power jack 7-12V Input Voltage (recommended) 6-20V Input Voltage (limits)

PWM outputs ICSP header

http://arduino.cc/en/Hacking/Bootloader

Etherboard

http://www.ladyada.net/learn/arduino/ethfiles.html

http://gkaindl.com/software/arduino-ethernet/dhcp

Wiznet W5100 Ethernet controller to the Arduino via the SPI bus. It uses pins 10, 11, 12, and 13 for the SPI connection to the WizNet. Later models of the Ethernet shield also have an SD Card on board. Digital pin 4 is used to control the slave select pin on the SD card.

http://www.wiznet.co.kr/Sub_Modules/en/product/Product_Detail.asp?cate1=5&cate2=7&cate3=26&pid=1011#tab

http://www.wiznet.co.kr/UpLoad_Files/ReferenceFiles/W5100_Datasheet_v1.2.2.pdf

Atmega8U2 programmed as a USB-to-serial converter

stty -F /dev/ttyUSB0 cs8 115200 ignbrk -brkint -icrnl -imaxbel -opost -onlcr -isig -icanon -iexten -echo -echoe -echok -echoctl -echoke noflsh -ixon -crtscts

ESP32 / Arduino

https://atadiat.com/en/e-esp8266-esp32-wifi-serial-bridge-converter/

JTAG

http://www.dd-wrt.com/wiki/index.php/JTAG_pinouts

JTAG Segger

CP2102

https://www.silabs.com/documents/public/software/CP210x_Universal_Windows_Driver.zip

GPS

Adafruit GPS logger shield kit - v1.1 EM-406a module

Companies

http://paeae.com/

http://www.adafruit.com/index.php?main_page=product_info&cPath=17_21&products_id=98

http://batchpcb.com/

http://www.sparkfun.com

http://toysdownunder.com/arduino/sensors/infrared-proximity-sensor.html

rfid 125khz robomaa
freetronics 433Mhz receiver

TFT Display

http://henrysbench.capnfatz.com/henrys-bench/arduino-displays/arduino-1-44-in-spi-tft-display-tutorial/

USB Troubleshooting

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 003 Device 002: ID 24ae:2000  
Bus 005 Device 002: ID 1784:0004 TopSeed Technology Corp. RF Combo Device


MS-7345:/home/# lspci | grep -i usb
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
echo -n "0000:00:1d.1" | tee /sys/bus/pci/drivers/uhci_hcd/unbind
echo -n "0000:00:1d.1" | tee /sys/bus/pci/drivers/uhci_hcd/bind
[ 8243.587443] uhci_hcd 0000:00:1d.1: remove, state 4
[ 8243.587451] usb usb6: USB disconnect, device number 1
[ 8243.587660] uhci_hcd 0000:00:1d.1: USB bus 6 deregistered
[ 8243.587708] uhci_hcd 0000:00:1d.1: PCI INT B disabled
[ 8252.532035] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 8252.532045] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 8252.532048] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 8252.532157] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
[ 8252.532184] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000a480
[ 8252.532568] hub 6-0:1.0: USB hub found
[ 8252.532572] hub 6-0:1.0: 2 ports detected
[ 8252.844012] usb 6-2: new full-speed USB device number 2 using uhci_hcd
[ 8252.964011] usb 6-2: device descriptor read/64, error -71
[ 8253.188009] usb 6-2: device descriptor read/64, error -71
[ 8253.404014] usb 6-2: new full-speed USB device number 3 using uhci_hcd
[ 8253.524009] usb 6-2: device descriptor read/64, error -71
[ 8253.748010] usb 6-2: device descriptor read/64, error -71
[ 8253.964012] usb 6-2: new full-speed USB device number 4 using uhci_hcd
lsusb -v -s 6:1
cat /sys/module/usbcore/parameters/autosuspend
cat /sys/module/usbcore/parameters/use_both_schemes
cat /sys/module/usbcore/parameters/old_scheme_first
"avrdude: stk500_getsync(): not in sync: resp=0x15"
Auto Reset capability of Arduino.

You should disable the capability by connecting 3 x 330ohm resistors (orange-orange-brown) in parallel between RESET and 5V pins of your programmer board. "A note of caution for Arduino ISP."

sudo avrdude -b 19200 -c usbtiny -p m328p -v -e -U efuse:w:0x05:m -U hfuse:w:0xD6:m -U lfuse:w:0xFF:m
sudo avrdude -b19200 -c usbtiny -p m328p -v -e -U flash:w:optiboot_atmega328.hex -U lock:w:0x0F:m
/etc/avrdude.conf
m328p

MBOT

BN: Unknown board
VID: 1A86
PID: 7523
SN: Upload any sketch to obtain it
https://www.makeblock.com/steam-kits/mbot-ranger
mbot ranger v2 / starter
Orion

https://www.mblock.cc/previous-versions/

http://docs.makeblock.com/diy-platform/en/electronic-modules/main-control-boards/makeblock-orion.html

Olimex AT Tiny85

https://www.olimex.com/Products/Soldering-Kits/OLIMEXINO-85-KIT/open-source-hardware

https://www.olimex.com/Products/Soldering-Kits/OLIMEXINO-85-KIT/resources/Olimexino-85_KIT_guide.pdf

https://www.olimex.com/Products/Duino/AVR/OLIMEXINO-85-ASM/resources/OLIMEXINO-85_manual.pdf

http://digistump.com/wiki/digispark/tutorials/connecting

https://github.com/OLIMEX/OLIMEXINO-85/tree/master/SOFTWARE

https://github.com/micronucleus/micronucleus

https://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-2586-AVR-8-bit-Microcontroller-ATtiny25-ATtiny45-ATtiny85_Datasheet.pdf


iron needs to be clean and hot (380 degrees) hot enough to melt the tin, but not too hot to burn the flux. Tin the tip of the iron and then hold the iron to the pin together with the soldering tin The flux will spread the molten tin and you wait 3 seconds to let the tin flow and make good contact, shiny cone connecting then you clean the soldering tip and start again

All you need is practice is to spot good from bad joints recognize when you have too much smoke or the tin doesn't flow, or has created a bridge

The ATTINY can be programmed with Arduino or PlatformIO

platformio

[env:attiny85]
platform = atmelavr
board = attiny85
framework = arduino
upload_protocol = micronucleus

usb driver

zadig libusb-win32 16D0 0753

https://github.com/koenvervloesem/digispark_blink_platformio http://digistump.com/products/1 digistump.com/wiki/digispark/tutorials/connecting https://github.com/digistump/DigistumpArduino/releases


https://github.com/libusb/libusb/wiki/FAQ#user-content-libusbwin32_libusbK_and_libusb_project_what_about_openusb

   If your device is a generic HID device, no extra driver is needed since it is supported. But HIDAPI is recommended for HID device rather than libusb on Windows.
   If your device uses WinUSB driver, no extra driver is needed since it is supported natively.
   If your device uses libusbK driver, you should be set as well (libusbK.dll should have been installed).
   If your device uses libusb-win32 (libusb0.sys) device driver, please try it to see if it works well. If not, try to switch to libusbK driver.
   If your device uses libusb-win32 filter driver, please switch to device driver mode. If you really need to use a filter driver, please uninstall the libusb-win32 filter driver and try usbdk instead.
   If your device uses other driver, and you do want to keep using the existing driver, then try usbdk.
   If your device uses other driver and you are okay with switching drivers, then switch to WinUSB (preferred) or libusbK driver.

V-USB

https://www.obdev.at/products/vusb/index.html