#21

I don’t personally have a strong preference one way or the other. The current setup for debug versus release and the need to run make clean is documented in the development guide:

http://archive.monome.org/docs/aleph:development

…it might make sense to change it in concert with the greater documentation migration.

#22

thanks for clearing that out ezra! Ah it’s hidden on the archive, I probably should’ve known this somehow - thanks @ngwese

#23

just done setting up the avr32 toolchain again (building from source) now on OS X 10.10, it seems to work but there where a whole bunch of warnings during the final make of gcc/toolchain, much more than I recall from last time on an earlier os version, anyone else having the same experience?

#24

did something happen to the baud rate again for debugging? this worked on my old laptop:
screen /dev/tty.usbmodemNN 57600
tried some other rates but no success, on a mac mini now, hoping to continue using the screen command, just calling out to see if anyone is doing that too.

#25

it’s in the config.mk file, currently looks like 115200

#26

thanks, that line of code got lost when I switched computers, it works now again, yey!

#27

I have developed for the Blackfin before (bootloader, kernel, and app development) and used Ubuntu (Xenial), but that was for a client who provided the PC hardware to host Ubuntu. If I can get started on Aleph, I would want to host the tools on Mac.

It is possible to have a case sensitive filesystem on macOS, but you probably need a second partition so that the boot drive can be standard mac insensitive. I have an old cvs repository that I needed to host on my new mac mini, and found that it also needs a case sensitive filesystem. I simply created a spare 100 GB partition and formatted it with Mac OS Extended (Case-sensitive, Journaled). I now place projects on that drive when needed.

I realize that this thread is eighteen months old, but I just got here.

#28

File system case sensitivity was the primary (but not sole) sticking point with getting the blackfin compiler built under macOS IIRC. Ultimately I ended up just switching to developing in full linux vm.

#29

ok, maybe i’ll give it a try on my case-sensitive partition

#30

sorry to bump this old thread, but i’ve had a great deal of trouble finding the blackfin gcc binary package for OS X. does this exist anywhere known? i can definitely afford the space for a case sensitive partition for it.

#31

I was never able to locate a prebuilt copy of the blackfin gcc toolchain for macOS nor was I successful in building it from source so I personally resorted to a Linux VM (specifically a tweaked copy of the vagrant setup mentioned above; https://github.com/bensteinberg/aleph-development).

1 Like