Go Down

Topic: ATmega1284P: End to End using 1.0 IDE (Read 81480 times) previous topic - next topic

CrossRoads

#315
Apr 11, 2012, 06:48 am Last Edit: Apr 11, 2012, 06:51 am by CrossRoads Reason: 1
Sounds like this one.
http://www.mdfly.com/index.php?main_page=product_info&cPath=5_6&products_id=415

I have programmed lots of '1284's with it.

Add this to programmers.txt to use it:

usbasp.name=MDFLY
usbasp.protocol=usbasp

Based around this:
http://www.fischl.de/usbasp/
Designing & building electrical circuits for over 25 years.  Screw Shield for Mega/Due/Uno,  Bobuino with ATMega1284P, & other '328P & '1284P creations & offerings at  my website.

theloon

Thanks for the info, I'll try my hand at boot loading them later this week. 

Constantin


I've got 3 ProMightys assembled and ready to program.  :D


Please let me know which bootloader worked for you. I am wondering if some of my issues related to my TQFP 1284p have to do with the bootloader files out there that seem to be designed for the DIP version of the chip. For example, the pin assignments vary significantly from the DIP version, with additional pins available, etc.

In the past, I used the brewtroller IDE successfully. However, for some reason the current distribution lacks the bootloader files that are needed for the 1284p TQFP. Maniacbug, any interest in supporting the TQFP version as well?

cowasaki



I've got 3 ProMightys assembled and ready to program.  :D


Please let me know which bootloader worked for you. I am wondering if some of my issues related to my TQFP 1284p have to do with the bootloader files out there that seem to be designed for the DIP version of the chip. For example, the pin assignments vary significantly from the DIP version, with additional pins available, etc.

In the past, I used the brewtroller IDE successfully. However, for some reason the current distribution lacks the bootloader files that are needed for the 1284p TQFP. Maniacbug, any interest in supporting the TQFP version as well?



I've just bought a 1284p-au to try, I have been using the 1284p with some success so here's to the SMD version.  I want it for a project which I was going to use 1280 ICs for but I just don't need all the IO just the memory.  Such a shame they don't do a 648p.

The SMD version, although it has more pins has pins with the same designations. What happens when you upload the DIP version's boot loader ?

If they are different I will have a look and if I can't suss it I will offer to make Maniac bug a 1284p-au board for him to sort it with :)

Constantin

#319
Apr 11, 2012, 08:51 pm Last Edit: Apr 11, 2012, 08:53 pm by Constantin Reason: 1
The v4.5 optiboot bootloader uploads fine and the pins that I can access easily seem to work OK using sketches like AnalogIn. So it may very well work. I just note that the pin numbers are different from chip to chip and that the TQFP versions of the ships typically offer more input/output pins than the DIP versions.

Given how much more stable the 1.0 IDE is, I am inclined to continue to use it rather than try and get the 022 version running again (for some reason, the 022 serial monitor is very flaky by comparison and frequently locks up the IDE...)

Later today I hope to hook up a logic analyzer to RX1 and TX1 to see if the two are behaving as intended. FWIW, I am in the throes of trying to implement RS485 connections between chips and my success thus far can only be described as terrible. I really wanted to implement RS485 because of its many merits vis-a-vis serial for Arduino-Arduino connections but I may just lower my sights and go with straight Serial-Serial connections instead.  


westfw

Quote
I just note that the pin numbers are different

Bootloaders SHOULD be OK.  The serial port is still the serial port.

Note however, that there's quite a lot of variation with the "onboard LED" that's supposed to blink when the bootloader starts.  Even with the DIP, different boards connect the (if any) different places (Sanguino, Mighty, and Bobuino, are all different.)  So you can have a bootloader that is probably working, and not see the comforting blinks...

cowasaki


Quote
I just note that the pin numbers are different

Bootloaders SHOULD be OK.  The serial port is still the serial port.

Note however, that there's quite a lot of variation with the "onboard LED" that's supposed to blink when the bootloader starts.  Even with the DIP, different boards connect the (if any) different places (Sanguino, Mighty, and Bobuino, are all different.)  So you can have a bootloader that is probably working, and not see the comforting blinks...



That doesn't worry me at all I had some off cuts of board and made a pile of data bus checkers :)  Basically a board about 1"x2" with a 90 degree 8 way pin header on one end and a 2 pin header on the other.  Each pin on the header goes through an SMD 1K resistor then an SMD LED and then all go to the 2 pin header which are connected together so I can plug it into 8 ports with a flying GND lead and test all 8 ports at the same time.  By plugging in multiple boards and daisy chaining the GND pins I can check all 32 outputs of a 1284p etc quite easily......  Always like finding uses for offcuts.

theloon

3 in the hand but no joy, I tried a PM to Manicbug 2 days ago but no reply, even offered him a board for his troubles. He must be away or busy.



Uploaded with ImageShack.us

theloon

Got a reply from Manicbug, I'll send him out a ProMighty tomorrow hopefully we'll get the TQFN package boot loaded.

cowasaki


Got a reply from Manicbug, I'll send him out a ProMighty tomorrow hopefully we'll get the TQFN package boot loaded.


Might have to have a play too.  I take it it is just wired pin to pin with clock, clock caps, decoupling cap and reset resistor.


Constantin

FWIW, my TQFP 1284P is working... blinking on demand, putting out serial0 messages, etc. I believe I used the Bahbots descriptor file (though with a different clock speed of 16MHz, not 18.x MHz) and the hex file from Mr. Sproul.

I am contemplating a loop-back test with Serial1 to see if it's behaving.

theloon



Got a reply from Manicbug, I'll send him out a ProMighty tomorrow hopefully we'll get the TQFN package boot loaded.


Might have to have a play too.  I take it it is just wired pin to pin with clock, clock caps, decoupling cap and reset resistor.




Yep just standard Arduino stuff except for LED is on pin B1 as not to take up a PWM pin.
My new design has reusable break off tabs for boot loader adapter and FTDI at opposite ends.

theloon


FWIW, my TQFP 1284P is working... blinking on demand, putting out serial0 messages, etc. I believe I used the Bahbots descriptor file (though with a different clock speed of 16MHz, not 18.x MHz) and the hex file from Mr. Sproul.

I am contemplating a loop-back test with Serial1 to see if it's behaving.


Could you put something together for others here to try out?

cowasaki




Got a reply from Manicbug, I'll send him out a ProMighty tomorrow hopefully we'll get the TQFN package boot loaded.


Might have to have a play too.  I take it it is just wired pin to pin with clock, clock caps, decoupling cap and reset resistor.




Yep just standard Arduino stuff except for LED is on pin B1 as not to take up a PWM pin.
My new design has reusable break off tabs for boot loader adapter and FTDI at opposite ends.



It'll be the same as one of the boards I've designed.  It pushes into a 28 pin socket to replace a 328p and is electrically and program compatible, all you do is change the board name :-)

I tried making it today but it is just toooooo intricate with such tiny tracks so going to have to send it out.

theloon

Not at all, my design brings out all the usable pins and includes optional external pull up resistors like the R3 ProMini by Sparkfun, but your design is a good idea also.
BTW how do you plan to connect all the additional tx/rx and input/output pins when confined to 28 pins?

Go Up