1284P boatloading

Hi everyone,

Im trying to use a 1284P chip with Arduino and iv found a couple guides online but Im needing help setting up with adding files to show up under the boards drop down to select it. Im using a mac and using Arduino 1.6.12.

Thanks for the help

or

MightyC

Juraj:
GitHub - MCUdude/MightyCore: Arduino hardware package for ATmega1284, ATmega644, ATmega324, ATmega324PB, ATmega164, ATmega32, ATmega16 and ATmega8535

Linkified - this is the core you want to use.

Also. 1.6.12 is really old. I would consider upgrading.

I’v used that link for trying to install the boot loader onto the 1284p but it comes up with an error. I’v attached the files I’m working off of and a screen shot of the tools menu showing the info for the chip. Heres the error code

Arduino: 1.6.12 (Mac OS X), Board: “ATmega1284, Standard, 1284P, 2.7v, Disabled (default), 16 MHz external”
avrdude: Version 6.3, compiled on Sep 12 2016 at 17:22:25

  • Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/*
  • Copyright (c) 2007-2014 Joerg Wunsch*
  • System wide configuration file is “/Users/ashe/Library/Arduino15/packages/MightyCore/hardware/avr/2.0.1/avrdude.conf”*
  • User configuration file is “/Users/ashe/.avrduderc”*
  • User configuration file does not exist or is not a regular file, skipping*
  • Using Port : /dev/cu.usbmodem1411*
  • Using Programmer : stk500v1*
  • Overriding Baud Rate : 19200*
  • AVR Part : ATmega1284P*
  • Chip Erase delay : 55000 us*
  • PAGEL : PD7*
  • BS2 : PA0*
  • RESET disposition : dedicated*
  • RETRY pulse : SCK*
  • serial program mode : yes*
  • parallel program mode : yes*
  • Timeout : 200*
  • StabDelay : 100*
  • CmdexeDelay : 25*
  • SyncLoops : 32*
  • ByteDelay : 0*
  • PollIndex : 3*
  • PollValue : 0x53*
  • Memory Detail :*
  • Block Poll Page Polled*
  • Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack*
  • ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------*
  • eeprom 65 10 128 0 no 4096 8 0 9000 9000 0xff 0xff*
  • flash 65 10 256 0 yes 131072 256 512 4500 4500 0xff 0xff*
  • lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00*
  • lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00*
  • hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00*
  • efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00*
  • signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00*
  • calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00*
  • Programmer Type : STK500*
  • Description : Atmel STK500 Version 1.x firmware*
  • Hardware Version: 2*
  • Firmware Version: 1.18*
  • Topcard : Unknown*
  • Vtarget : 0.0 V*
  • Varef : 0.0 V*
  • Oscillator : Off*
  • SCK period : 0.1 us*
    avrdude: AVR device initialized and ready to accept instructions
    Reading | ################################################## | 100% 0.02s
    avrdude: Device signature = 0x000000 (retrying)
    Reading | ################################################## | 100% 0.02s
    avrdude: Device signature = 0x000000 (retrying)
    Error while burning bootloader.
    Reading | ################################################## | 100% 0.02s
    avrdude: Device signature = 0x000000
    avrdude: Yikes! Invalid device signature.
  • Double check connections and try again, or use -F to override*
  • this check.*
    avrdude done. Thank you.
    This report would have more information with
    “Show verbose output during compilation”
    option enabled in File → Preferences.

thanks for the help guys

tools.jpg

Are you sure that the crystal is connected properly and working? Check all connections to/from crystal. The wires should be short. Make sure the caps are making good contact and that their other side is connected to ground.

0x000000 sig frequently indicates that fuses are set for external crystal, but said crystal is not present or not working.

Also check ISP wiring

When you bootload, it will set the fuses, exit and reenter programming mode (latching the fuses) and then write the bootloader. If the clock source you chose (crystal) wasn't present, the first - and only the first - time you bootload it, you'd see it successfully writing the fuses, and then failing with 0x000000 sig (this is a 100% guarantee as to the nature of the problem, if you catch it at the time!). After that, it fails immediately, since now the fuses are set to use the non-working clock source