Chris Anderson @chrisanderson1973@librem.one

More work tonight on the audio project: I set up Windows, Mac, and Linux all for reliable builds. Windows is still somewhat of a straggler with an external make project currently required to create a compatible library. It will do, for now. On to creating the release versions of the app, just to have that part of the puzzle solved.

Work on the app's flasher plugin today - starting with the easiest environment - Linux. The whole point is to build this program in a module way from the beginning. (Also - no work on mobile platforms, for now. iOS and Android, both, make using UARTs very difficult and not worth the trouble right off.)

There was work over the last couple of days to set up the Android / Qt build environment. I last worked with this kind of development environment in 2020, and had not attempted the Qt on Android build setup in QtCreator. I finally cracked after a few hours, though, and I am now looking into serial port handling on Android using Qt. Exciting stuff!

Linux firmware updates - about 90% there! A bit of work to, first of all, try out the Linux build of the app, which was fine. The second part was rolling the serial interface library, which was a piece of cake.

More work on both Windows and Mac versions of the firmware update functionality. This two efforts are complete, minus code cleanup, etc. The project is going ahead full-steam!!

Light work to try and prove out the firmware update process. It is a success, and ultimately the procedure will involve only holding down a button to get things started! The video shows the update process in action, through most of it, anyway.

The protocol stuff is working.....basic reconnection / connection on startup works, and I have a demo packet for one "effect" here.

I pretty well have a good (re)start on the audio project, with the audio DSP development “talking” to the GUI app I had created last year.

Sitting here today, I thought of another “problem”: Users must be able to update the system!

Thanks to Analog Devices, Inc, there is also a way to make a cross platform firmware updater, which is critical.

https://github.com/analogdevicesinc/sam-audio-starter

Good amount of work tonight in getting QT 6.6 working along with the macOS QT app for the audio module. Next up: comms protocols.

More work, upgrading the bare metal framework and continuing to work on the serial protocol!

A great night for work and figuring stuff out! Between the team at Analog Devices and myself, we figured out the codec issues. I had thought the audio path was working before, but that was not the case. In any event, I did some cool jamming with these mini effects processor…. Now for much more design work!

Very good update today - I’ve made the SC589 mini viable, at least for me, as an audio development platform! I’ve managed to get the audio loop back running through one of the two SHARC cores. Now, it’s on to the races!

This is turning out to be a cool project to work on. I like the position of working on an application for an Analog Device's part, and being in contact with their engineering team. https://ez.analog.com/dsp/software-and-development-tools/sharcaudiomodule/f/q-a/573315/sc589-mini-adau1761-initialization-sampling-set-pll

Good work tonight on the SC589. I have worked to the point where I have unraveled the mystery of program lockups during debug and release mode execution. An audio device PLL(Phase Locked Loop) is not being set. I think it is a config issue, or maybe I can use a working reference to get around this. We shall see. Whatever the case, I am glad to be debugging a fairly interesting platform.

SAM starter project:
#analogdevices #sc589mini #sc589 #dsp

https://wiki.analog.com/resources/tools-software/sharc-audio-module/advanced-audio-projects/environment_setup#cld_cdc_usb_driver_setup

SAM start project:
#analogdevices #sc589mini #sc589 #dsp

https://github.com/analogdevicesinc/sam-audio-starter

Good one! After some issues trying to run a full-fledged synth straight away, I went back to the basics to make sure the ARM and DSP cores were booting at all. I found a guide for flashing and verifying the bootloaders for all three cores, and managed to run an application that was flashed via command line and a custom Analog Devices tool. Great experience, given what else I want to do with the SC 589 platform.

Setting up the development platform..... The very first thing I did was to clean up the work area and install the ESD mat, wristband, and ground. Only fools, or simply people. how haven't learned about ESD, play around when handling electronic components and open boards.

This all just became a little more real! I just received the Analog Devices SC 589 mini development board, along with the related adapter board earlier. So, I am ready to begin developing the actual DSP software and the client software (GUI) for the DSP / effects system! Exciting times!