Available as a portable and installable edition.This includes a responsive interface and progress indicators for lengthy operations. In addition memory-sectionsĭefine a foldable region and inaccessible sections are hidden by default.įurthermore a lot of effort was put into making operations fast and efficient, instead of forcing you to use specialized functions for technical reasons or arbitrarily limiting file sizes. Drives and memory can be edited the same way as a regular file including support for undo. The easy to use interface offers features such as searching and replacing, exporting, checksums/digests, insertion of byte patterns, a file shredder, concatenation or splitting of files, statistics and much more.Įditing works like in a text editor with a focus on a simple and task-oriented operation, as such functions were streamlined to hide differences that are purely technical.įor example, drives and memory are presented similar to a file and are shown as a whole, in contrast to a sector/region-limited view that cuts off data which potentially belongs together. The stlink thing seems to work better, but I've yet to find a foolproof method on the mac.HxD is a carefully designed and fast hex editor which, additionally to raw disk editing and modifying of main memory (RAM), handles files of any size. random erase failures (documented at stlink's github), the 'run' step appears unnecessary & I've had couple modules that 'appeared' correctly programmed, but would then needed to be reprogrammed. That said, I used to use the technique documented at:Īs recommended by another wiggler. I'll admit that the only way I know of making the combo file includes an upload command which fails, but the combo file is whole and seems to to work. St-flash write whatever_bootloader_combo.bin 0x8000000 I make in the mutable environment, then I open a new terminal window, CD to the appropriate folder and: I've dug pretty deep (for my shallow brain) into why STLink V2 isn't recognized in the MI Dev Environment and haven't figured it out (yet!). HipDestroyer wrote:How do you guys upload hex files via mac osx? Other files can be found here (mega kudos to hadesbox!): The binaries include both the bootloader and the firmware, whereas with the the hex files you need to load first the bootloader and then the firmware. We are still missing the files for Frames, Edges and Streams, so if you have them and feel like sharing them, please post them here or send them in private and I'll add the files to the list. Kudos to them and my heartfelt gratitude. So now with their full approval and support ( ), I am posting the compiled codes here. And some of them offered to send me the files they compiled (or had compiled by a friend) on OSX or Linux. &start=500Īnd several wigglers contacted me in private to testify that they had the very same problems and couldn't compile the code on Windows either.
Looking at the code, I came to the conclusion that the syntax wasn't compatible with Windows target commands. No matter what, I kept getting error messages and drowned into despair. I tried several softwares, read a lot of tutorials, watched some videos.
At the moment it doesn't quite make sense in my tiny mind!Īpoisontree wrote:I work on Windows 7 and I have tried for several days to compile the bootloaders and firmwares for the DIY versions of the Mutable Instr. Can this be uploaded using the STM Link programmer in one go somehow?Įssentially I'm looking for an idea of how and what order to do things in to successfully get the STM flashed please. I also see there's a bin file that includes both bootloader and firmware. I see that there are seperate bootloader and firmware files posted and looking at the bootloader code it seems to provide the firmware audio upload function.ĭoes this bootloader replace the factory one? If so, how do I then upload the firmware? Does it have to be done via the audio file? I have a Nucleo board on it's way which I believe has the STM Link programmer on board which I was planning on using to flash the STM. I'm new to the STM chips but as I understand it, they come with a factory bootloader in them that allows you to upload code via the serial port (I've seen a description of a bootloader example app that makes it look quite simple to do). I'm about to embark on a Braids build and am planning on using the hex files linked to above. Trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst Info : only one transport option autoselect 'jtag' Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/.Įrror: unable to open ftdi device: device not found Warn : Using DEPRECATED interface driver 'ft2232' Hello Im trying to upload Yarns firmware but not working i did with braids, rings warps with no problem using St-link and olimex adapter but when i try on yarns i got this message