Alt. firmware and GUI for Thanos's AMC1.5 & AMC1.6

[prilad]

I want to ask for clarification ... DIP-SW ON = actually connected to [ ground in AMC1.6 board ] and is logical OFF = low state = 0V ...
Dip-SW OFF = actually disconnected from [ ground in AMC1.6 board ] and is logical high ON = high state = 5V ...

Yes, my friend.

When I described the position of the switch, I mean the logic levels of the signals at PORTB pins. When I said that the switch in the OFF position - it meant that at ports pin is low level (the switch is closed to ground).

I'm sorry that I made ​​a mess ...

Regards,
Ale

[speedy]

Hi prilad:
My friend ... Pls. don't be sorry ... it's a common error ... nothing happened.

That reverse the case entirely upside down ... because when I was testing from the first beginning I used the Dip-SW on the opposite condition ... That make sense now why it wasn't working with the USB ... I wonder how it worked some time and some time not ? could that happen ?

BTW... what do you think of this result of the H-bridge ? vicpopo did a quite good job ?
viewtopic.php?f=43&t=246&start=70#p2850

[prilad]

Hi, Speedy!

what do you think of this result of the H-bridge ? vicpopo did a quite good job ?
viewtopic.php?f=43&t=246&start=70#p2850

Yes, yes and yeees!!! Very good job for you and vicpopo!!!

And I want to ask you one more time - can you create some videos about working AMC in test modes?
In test mode 1 (when RX is disabled) microcontroller CANT'T receive any data. Only generate new positions by himself.

Regards,
Ale

[speedy]

Sorry Prilad ... just a screen capture as I don't have good camera ... let me fix the AMC first and see if the on/off issue makes any deference with me or not ... today I'll give you results ...

[prilad]

Hi, Guys!!!

I think, I found one problem with my FTISP files for atmega8535. And it is not only my problem. As I see Thanos has the same problem in FTISP for atmega8535. The problem has the name - the FUSE in *.bat files.

When Thanos was make FTISP files for atmega8535, hi (and I) get fuse data for atmega644. But that is not correct. I think, bat file must be next:

ftisp.exe -B 100000 -E -fw A22_v21.bin -Fw 0xC1FF -fv A22_v21.bin

pause

Tomorrow I will try to solve this problem... But now I'm ill I'm sorry

Regards,
Ale

PS: Many thanks Thanos, that drew my attention to this problem...

[tronicgr]

As I said in the AMC1.6 thread, I have no way to test the correct fuse settings with ATmega8535, I don't have any available. If anyone has one can try it with Prilad's suggestion above.

Thanos


PS. Prilad... get well soon!

[prilad]

PS. Prilad... get well soon!

Thank you, Thanos, I will try

Thanos! Can you give me a URL to page, where you tell about fuses for you firmware?

Regards

[tronicgr]

The fuse values can be found in AVR datasheets. They are different for some microcontrollers even if they are pin-compatible.

I found the correct fuses for mine using the AVR studio4 as it gives the fuses options in pull-down menu.

The most important fuse to set is the crystal source and should be set to the following setting:
"External oscillator, 8MHz+, Startup Time 16K CK + 65ms" that translates to "0xFF" for fuse.

Other fuse that needs to be set correctly (for ATMega644) is the "Disable JTAG" fuse!


The fuses consist of 2 byte and a 3rd sometimes, called extended byte.

ftisp.exe -B 100000 -E -fw fw11g18.bin -Fw 0xFFDCFF -fv fw11g18.bin

For the ATmega644 example above (with the FTISP command line):
Fuse Low Byte =0xFF
Fuse High Byte = 0xDC
Fuse Extended Byte = 0xFF

Thanos

[prilad]

For the ATmega644 example above (with the FTISP command line):
Fuse Low Byte =0xFF
Fuse High Byte = 0xDC
Fuse Extended Byte = 0xFF

Yes,I understand this. But high byte = 0xDC (binary = 11011100) is strange for me. And I wont to ask - why you PROGRAM (set to 0) bit BOOTRST (bit 0)?
What do you mean?

When the BOOTRST Fuse is programmed, the device will jump to the Boot Loader address at reset, (c) from Atmega644 datasheet


Regards,
Ale

[tronicgr]

I know that I have the bootloader active. But if there is nothing stored in the bootloader area it jumps down to the start of the code.

I have some of my chips with "stk500" bootloader for special cases when I don't want to use the FTDI ISP connection. But the thing with the bootloader is that you have to actually install it using AVR studio4 and actual hardware programmer.

Other than that I see no problem leaving this functionality enabled.

Thanos