MultiModule help

here is a video done with the slo-mo camera on my iphone showing the initial programming attempt with a brand new ATTiny24A chip. I did this after moving the ground back to the module this morning, with a brand new ATTiny chip in my multi-module board. If I repeat the programming steps now, I get the same "Verified" result as before. only on the initial programming do I get the "erasing, programming, done" sequence as can be seen here. (you need to slow pan the video, but it can be seen).

One other thing that I can think of. On two occasions, when I incorrectly saved a model config file to my DEVO model folder, it became corrupted and it could not be overwritten, edited, or erased from the DEVO drive no matter what I tried. To fix it, I had to format the DEVO root drive and copy all of the files back to the DEVO drive (except of course the .dfu file and debug folder), then I could rewrite, edit, and save that model config file again.

You might try to format the root drive and copy the files back to it again, and see if that works.

The only other thing that I can think of is maybe you have a wiring error somewhere that you are repeating on all of your attempts at connecting everything together.

Other than that, I am out of ideas.

Now I have learned better than to ever think anything I do is perfect, but I am pretty sure at this point that I have had things together correctly. I would find it hard to believe that I can disassemble the multi-module and re-connect any two of the three modules directly to my 7e and have it work fine with them, in any two combination, that I then am making the same wiring mistake when I re-assemble it into the multi-module. I have re-built the module 4 times now, during this project attempt. I've been using the wiring chart shown on the wiki page bitbucket.org/PhracturedBlue/deviation/wiki/ModuleList and I've used two full sets of components.

I figured out where to order v1.3 boards, and I hope to have them sometime soon. I'll give it another try with the 1.3 board, maybe my luck will be better.

I am assuming that the image on the wiki is a 1.3 board, as it is different from the v1.2 board i have. I also assumed the pinout was the same, as it's obviously the same order on the other two boards, just in a different orientation. I have posted pics of the board I have for reference.

thanks

My guess is that your avr.hex file is corrupt. The programmer seems to be working properly - but you're not burning enough bytes on the ATTiny for it to be the proper code.

I can't tell from either video what it actually is. Can you get a checksum of some kind of it? gmd5sum, maybe?

Also, your first test should be with just the multimodule. Take all the RF modules out of the MM, and only enable the MM in hardware.ini. The Tx should see the MM and boot, but with no extra protocols. If that's not working adding the RF modules will just confuse things.

i believe someone earlier said that I needed all the modules installed and the hardware.ini file configured for them in order to program the ATTiny24A. I will try removing the modules, and config, and programming that way.

I have no experience with these chips, as far as a checksum. How do I do that to verify my AVR.hex file? (i have re-downloaded it several times, but i accept it might be corrupt.)

thanks

ok, with all modules removed, and their config removed. (multimodule is still connected, and the single line is enabled in hardware.ini.

At first I got this error that is shown as a known issue on the wiki:
ERR: No switch found -- avr didn't initialize. this one is common and you need to try several times before giving up. Itoculd be improper wiring or just that the code isn't working properly. I'm still working on this

I repeated the power-on cycle three times, and I then received the usual output that I get:
1.Init
then
Found AVR: 0b911e53
hex: 17bytes
2. Verified

I can now repeat the power-on cycle as many times as i want, and I continue to get the second output on the screen.

i'm still looking into how to checksum the AVR.hex file i used.

Just post or open avr.hex in notepad. Should look like this....

:1000000010C020C01FC057C01DC01CC01BC01AC0DC
:1000100019C018C017C016C015C014C013C012C034
:1000200011C011241FBECFEDCDBF10E0A0E6B0E09F
:10003000EAE1F1E002C005900D92A836B107D9F7C8
:1000400040D069C0DDCFCF93DF9300D0CDB7DD279F
:1000500012BE83E083BF8FEA8ABB88E18DB980E45A
:100060008EB985EA8FB9FE013196CE01039620E460
:1000700032E00BC042B74D3710F01DB817C0769B69
:10008000F9CF4FB141932EB93FB9E817F90791F76E
:100090001DB88FE88ABB89818BBB8981869586953F
:1000A0008695867088BB0981FA800BBBCE5FCDBF79
:1000B000DF91CF910895E02EB09BEF2CEBBA10E0CA
:1000C000189510E00FE08FE0F82E8FE88ABB86E0ED
:1000D00087BB8FE08BBB80E182BB81E080BD80E28B
:1000E0008BBF80E38ABF8FB780688FBFC0E1D0E24B
:1000F000B09B0FC00AB604FEFBCFCC9B04C0B09BE4
:1001000008C011E006C0112319F01BBE9CDFDBBF45
:0A01100010E0CABFEDCFF894FFCF56
:08011A000001020307818200CD
:00000001FF

here is my best attempt at a photo showing the wiring to the multi-module with no modules installed. There are two white wires because i only have a 6-color set. You have to trust me that the reset white wire goes to the TCK port on the backboard, and the SCK white goes to the SCK spot.

just to explore every option, I tried flashing the AR with the 1.3 board AVR.hex. I get the identical output the first time, where it shows, erasing, programming, done, but it shows 20bytes not 17bytes. It still shows the same module missing error, but it's clearly indicating a difference in the AVR file it can recognize.

just in case that helps anything....

I'm not sure if you need the modules installed to program the DFU or not. I was talking about after you've programmed it, to see if the multimodule is working at all. I've had issues with modules interfering with each other. Everything worked perfectly with zero, one or two modules installed, but adding the third one caused module missing errors. I've been told it's a timing problem do to using long wires, but I'm not a hardware person so never really chased it down.

You can get an md5 checksum utility from winmd5.com/ . I don't do much windows, so can't help with it. But installing it and then posting the md5 sum for everything (the two dfu's and the avr.hex file) would give us a quick check for corrupt files.

If you look at SebyDocky's tutorial on installing the MM, you'll see that it says "hex: 338bytes". That's the kind of size you want to see.

using the tool from winmd5.com;

from my current copy of the nightly build:
749bcc12db4c1e161f65debce2294665

from the programmer DFU:
c6603b400f11e329ddb45a84d7db0f4a

and from the AVR.hex file v1.2:
5cd33bcd2c300e17e39e135801baba5e

thanks

One other thing to check would be continuity from the ATtiny pins to their proper points on the Tx board and its other points on the MM board. You can download the MM circuit board design files from OSH Park and view them with a gerber file viewer, like gerbv, to figure out where they should all terminate.

Out of interest do you own Arduino Uno? Just you could flash attiny with one.

no, i don't have any Arduino stuff or experience. I looked for an ATTiny programmer online, but they seem to be hit or miss kind of things, and another $30 for something that I have no idea how to use.

when he does the programming with the Devo10 he gets the AVR at 0b911e53. My Devo 7e shows a different location 0c931e53. Is this expected?

He also gets clear lettering on the screen. The lettering on my 7e display is muddled and not clear for the last line.

Yes, I accept something is going wrong with the programming, I just don't understand what it could be. I am positive I have everything connected correctly, and am following the same instructions he did in his video, the only difference is Devo 10 to Devo7e.

thanks

foer what it's worth. If i remove the hex file I get a "bad hex file" error. If I cut the text in half from the hex file i've been trying, i get the same output, but it shows 11 bytes. I can say for sure the file is affecting the reported byte size. has anyone been able to verify the checksums I posted earlier, i didn't see any to verify against posted on the wiki.

Did you try the re-format of the DEVO drive?

yes, i have tried formating the devo before re-loading the nightly build after flashing the AVR.

m.banggood.com/USBASP-USBISP-3_3-5V-AVR-...EGA128-p-934425.html

Get the 3.3v / 5v one and very cheap.

Well from what I've seen posted you've done it all very well. So barring software issue.
Number one issue flashing AVRs is dry soldering. Re flux and re heat till nice and shiny solder.
Swapped miso / mosi or miss connected but you just get errors.