c0ntr0l update

[eil]

Does anyone have a backup copy of my modified tarball of c0ntr0l in the first post? My version is sitting on the hard disk of a powered-off server somewhere and it'll take some doing to get it.

I don't know if I'll ever have the time to continue improvements to c0ntr0l (it might actually be easier to start from scratch), but I'd like to at least stop giving people the 404-finger whenever they click on the link.

[antto]

we only really want a good backup/import of EEPROM files, the rest is working fine..

[LivePsy]

Are you referring to this cause for not having usable backups?

http://forums.adafruit.com/viewtopic.php?f=7&t=8640&start=15#p74402

[antto]

the backup file seems to contain the same data that is in the eeprom (in binary form, not ascii or hex or anything else)
the problem is that the EEPROM is 4KB, but c0ntr0l doesn't extract the whole 4KB
my files are smaller and the size varies too much
also, i think importing the file to the x0x doesn't work anymore here at all (this applies to CLEAR too)
i'm not familiar with python at all, so i can't help it..

[Sokkan]

antto: The c0ntr0l app only asks the x0xb0x to send the patterns in its memory. If you have changed how the patterns are stored you need to have a look in compcontrol.c, compcontrol.h and pattern.h at least and see what you need to change to make it work with a new memory structure.

[antto]

antto: The c0ntr0l app only asks the x0xb0x to send the patterns in its memory. If you have changed how the patterns are stored you need to have a look in compcontrol.c, compcontrol.h and pattern.h at least and see what you need to change to make it work with a new memory structure.

yeah, i know
i've modified the definitions PATT_SIZE, NUM_BANKS, NUM_LOCS, BANK_SIZE and similar to the actuall values, PATT_SIZE is 21 now and so on
even if the compcontrol is reading wrong values - then why does the file size vary on every "Backup" i do?
it goes from 1.85KB to about 2KB without any reason
this tells me something is wrong, maybe the transfere f*cks up on bigger amounts of data, i have no clue
btw, even when i was with the stock firmware (1.05) and later when i tryied sokkos - the files i was able to extract were again somewhere between 1.85 and 1.89KB, which is far less than 16(banks)*8(slots)*16(bytes)=2048bytes

[Sokkan]

The c0ntr0l program will first extract information from what is received assuming everything is in the old format. Notes are build into Note objects and rests taken care of separately. This has to be completely rewritten in your case.

The size of the file will therefor depend on how many rests you have in your patterns since Note objects and rests are translated into hex-strings in different ways by c0ntr0l.

Why you get different file sizes when saving identical memory contents is most likely yet another serious bug in c0ntr0l...

For saving patterns to a computer I would write the simplest possible program in a suitable programming language(java, python...) that just extracts whatever the x0xb0x outputs and writes it in binary to a file. The c0ntr0l program could probably be stripped of lots of junk and streamlined into something suitable.


Sidenote:
I would not recommend anyone to use c0ntr0l for anything. Please note that it will not check the size of the firmware it writes with the address of the bootloader that is burnt into the fuses. I have always recommended using JAvrProg for burning the FW, it will read the fuses and check the size of the hex-file to prevent overwriting the bootloader.