Yeah I did not know that 0.28 was out, though @rudeog mentioned something about importing a zero-crossing fix. Does that mean my kicks will stop clicking?
something happened after latest firmware update with my machine, it doesn't update anymore, no matter if i try the official build or alternative one... it is not about the card, tried with few, and machine itself functioning perfectly, just doesn't update...oh, and sample load stuck just as well, that was the reason to update in the first place...
edit:no, not functioning perfectly, sequencer doesn't start at all...
User sample load? How big are they? Cannot be more than about 480K in TOTAL. Try a single, small sample and see if that fixes stuff. This happened to me, too.
well, now it's bigger then just sample loading problem, sequencer doesn't start at all, and can't re-flash the firmware anymore...and no sign of developer responding in any form, doesn't it say 'bug reports' in the tags of this topic??
as a note: While testing I noticed the clock output is skipping a pulse sometimes. I uploaded the v0.28 regardless, because the rest is working good. This issue should be fixed untill tomorrow. I have to do some emails first before I can return to the firmware work.
same for the changelog. There are plenty of changes incorporated from rudeogs codebase, but I have not yet added them all to the changelog yet.
if somebody could confirm the skipping pulse on the clock out, that would be great! I hooked the trigger IO to the scope, and there everything looks fine. so maybe it is my 'black seq' thats skipping steps and not the trigger IO
when I have the LXR set to internal clock and sync the 'black seq' using one of the clock outs, it sometimes advances 2 steps instead of 1, thus loosing sync.
Julian, I was looking at the comment on your change (ab8c79f in your repos), and I don't think we need to break compatibility with old pattern set saves... In my newer stuff with pattern rotation, I've also put pattern length into an array with rotation amount. My plan was to stash these two values at the end of the whole pattern set (although I have not done this yet), so that if someone loads an old pattern, these values are 0 (in my code, a 0 length for pattern length means 16, and I'm stashing the rotation amount into the same byte since each quantity only needs 16 possible values).
Not sure how many folks are relying on being able to load old patterns after upgrading firmware though.
I forgot to tell you. I fixed the broken backward compatibility. I work with the track length variable, and when it is time to load or save a pattern, I just convert it back to the old track length flag. So the savefile is still the same
Yo, I have trouble updating the firmware. The SD card works in general, loading/saving/etc. works as expected. When I hold down the encoder and plug in the power supply, I always get "Bootloader 1.1" and then "Firmware Error". The Firmware version on the LXR is 0.19, this is a kit from the first batch.
fdisk -l /dev/sdb
Disk /dev/sdb: 3974 MB, 3974103040 bytes 70 heads, 5 sectors/track, 22176 cylinders, total 7761920 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
Device Boot Start End Blocks Id System /dev/sdb1 5 999949 499972+ b W95 FAT32
Make sure you downloaded the firmware correctly. You should have a file about 250k in size. There are issues with downloading from github, you need to use the "raw" link.
It doesn't include everything. Look on this page: https://github.com/rudeog/LXR Where it says "Here is a list of current changes" toward the middle of the page, it lists things that have not yet been merged into the official FW. I have updated the custom FW last night to include the pan modulation fix that was made in 0.30. The custom FW does not include the trigger kit fixes (I don't have my trigger kit yet, so can't test).
the bootloader updates where cosmetical changes. 1.0->1.1 added the binary LED pattern on the step buttons 1.1 -> 1.2 fixed some error messages (wrong alignment, more descriptive messages)
the "Firmware error" messages says: - SD card initialized proppelry - file system initialized without failure - file "FIRMWARE.BIN" not found on the SD card.
are there any other files on the SD card whose short name in 8.3 format could interfere? You did copy it to the root directory? filename is als caps?
It doesn't include everything. Look on this page: https://github.com/rudeog/LXR Where it says "Here is a list of current changes" toward the middle of the page, it lists things that have not yet been merged into the official FW. I have updated the custom FW last night to include the pan modulation fix that was made in 0.30. The custom FW does not include the trigger kit fixes (I don't have my trigger kit yet, so can't test).
Ahh, a great link for info of my questions! Thanks!
Mergin takes me a little bit longer, since I don't want to blindly merge in all the changes and have to find some time to loock over them first
Totally understandable! I'm not in a hurry! Thank you Julian for a great machine that's getting better and better!
Possible bug v0.33, tracks 6-7 are "linked", volume control effects both tracks, also the trigger outs are "linked" on 6-7 that is they play the same as each other. Example: if I have 4 steps on track 6 and 2 steps on track 7 the trigger outputs on 6 and 7 will both play all 6 steps. Hope that makes sense
Comments
https://github.com/SonicPotions/LXR/raw/master/firmware image/FIRMWARE.BIN
*SD card OK' or something like that and then it start to update, but never finishes...
I uploaded the v0.28 regardless, because the rest is working good.
This issue should be fixed untill tomorrow. I have to do some emails first before I can return to the firmware work.
same for the changelog. There are plenty of changes incorporated from rudeogs codebase, but I have not yet added them all to the changelog yet.
I hooked the trigger IO to the scope, and there everything looks fine.
so maybe it is my 'black seq' thats skipping steps and not the trigger IO
when I have the LXR set to internal clock and sync the 'black seq' using one of the clock outs, it sometimes advances 2 steps instead of 1, thus loosing sync.
Not sure how many folks are relying on being able to load old patterns after upgrading firmware though.
I work with the track length variable, and when it is time to load or save a pattern, I just convert it back to the old track length flag. So the savefile is still the same
fdisk -l /dev/sdb
Disk /dev/sdb: 3974 MB, 3974103040 bytes
70 heads, 5 sectors/track, 22176 cylinders, total 7761920 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 5 999949 499972+ b W95 FAT32
Formatted with:
mkfs.vfat -F 32 /dev/sdb1
Where it says "Here is a list of current changes" toward the middle of the page, it lists things that have not yet been merged into the official FW. I have updated the custom FW last night to include the pan modulation fix that was made in 0.30. The custom FW does not include the trigger kit fixes (I don't have my trigger kit yet, so can't test).
ls -la FIRMWARE.BIN
-rw-r--r-- 1 user user 266800 Mar 1 20:38 FIRMWARE.BIN
1.0->1.1 added the binary LED pattern on the step buttons
1.1 -> 1.2 fixed some error messages (wrong alignment, more descriptive messages)
the "Firmware error" messages says:
- SD card initialized proppelry
- file system initialized without failure
- file "FIRMWARE.BIN" not found on the SD card.
are there any other files on the SD card whose short name in 8.3 format could interfere?
You did copy it to the root directory?
filename is als caps?
ls -la
total 400K
drwxr-xr-x 2 root root 4.0K Jan 1 1970 .
drwxr-xr-x 23 root root 4.0K Mar 1 21:24 ..
-rwxr-xr-x 1 root root 261K Mar 3 15:01 FIRMWARE.BIN
-rwxr-xr-x 1 root root 11 Mar 3 14:59 GLO.CFG
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P000.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P001.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P002.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P003.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P004.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P005.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P006.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P007.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P008.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P009.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P010.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P011.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P012.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P013.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P014.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P015.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P016.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P017.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P018.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P019.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P020.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P021.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P022.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P023.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P024.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P025.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P026.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P027.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P028.SND
-rwxr-xr-x 1 root root 229 Mar 3 14:59 P029.SND
-rwxr-xr-x 1 root root 575 Mar 3 14:59 README.TXT
is there a finished bootloader.hex (ready to flash) somewhere available to download?
cheers Paul
see here: http://forum.sonic-potions.com/discussion/358#Item_5
i think i used the wrong search terms when looking for it.
Example: if I have 4 steps on track 6 and 2 steps on track 7 the trigger outputs on 6 and 7 will both play all 6 steps.
Hope that makes sense