Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| boards:moteino [2021/11/18 17:17] – [Boot-loader] darron | boards:moteino [2024/09/02 11:26] (current) – [Issues] darron | ||
|---|---|---|---|
| Line 26: | Line 26: | ||
| input for DIO1 which may be utilised for Rx timeouts. | input for DIO1 which may be utilised for Rx timeouts. | ||
| - | On the XRobotix clone the LDO VREG has been replaced. VIN max is 6V rather than 16V and current max is 200mA instead of 600mA. | + | On the XRobotix clone the LDO VREG has been replaced. VIN max |
| + | is 6V rather than 16V and current max is 200mA instead of 600mA. | ||
| + | |||
| + | The board has been tested to work at 2.5V and will transmit at | ||
| + | this frequency even with the 16 MHz XTAL, however, the boot-loader | ||
| + | has a BOR setting of 2V7 which means it will continually reboot at | ||
| + | around 2.9V which is at the top of the BOR range for 2V7. The ATmega | ||
| + | and SX1276 can operate at 1.8V minimum. | ||
| ===Pinout=== | ===Pinout=== | ||
| <wrap right> | <wrap right> | ||
| Line 58: | Line 65: | ||
| This is a quick test that communications are working. | This is a quick test that communications are working. | ||
| - | The bootloader is probably | + | The bootloader is related to DualOptiboot_V5.0_atmega328_BlinkD9.hex, perhaps an older revision. |
| __[[: | __[[: | ||
| Line 95: | Line 102: | ||
| </ | </ | ||
| - | ISP must be performed at 3V3 and beware that cheap programmers | + | ISP must be performed at 3V3. Beware of cheap programmers |
| I/O at 5V. | I/O at 5V. | ||
| __[[: | __[[: | ||
| - | I/O pins on the Pololu have 470R in series. | + | I/O pins on the Pololu have 470R in series |
| - | __Moteino__ | + | ==Moteino== |
| PB2 must be pulled high via 100K when ISP is connected to | PB2 must be pulled high via 100K when ISP is connected to | ||
| Line 118: | Line 125: | ||
| </ | </ | ||
| - | __ISP__ | + | ==Pololu== |
| Vcc must be connected to target 3V3 because ISP will not function | Vcc must be connected to target 3V3 because ISP will not function | ||
| Line 130: | Line 137: | ||
| - | __Configure__ | + | ==Configure== |
| < | < | ||
| pavr2cmd --restore-defaults | pavr2cmd --restore-defaults | ||
| Line 137: | Line 144: | ||
| </ | </ | ||
| - | __Probe__ | + | ==Probe== |
| < | < | ||
| Line 172: | Line 179: | ||
| [[https:// | [[https:// | ||
| + | |||
| + | [[https:// | ||
