I have already briefly discussed this in a thread, but I am wondering
again how viable it would be to get Csound working on a dsPIC. I am
about to start writing a little sythn project for it, so I need to
figure out if it'll be less hassle to write my own audio code from
scratch, or to try to build Csound for dsPIC.

I don't know many of the factors I would need to consider to get this
working, but what I do know is that I have access to exactly 512kB of
program memory. Would that be enough to get a basic Csound built up
and running? I have access to both a C and C++ compiler for my dsPIC
device.

What else would I need to bare in mind for this? I read a recent post
regarding a baremetal RPi Csound build, and it discussed pthreads and
other functions that rely on the OS. Does that mean I would need to
modify or remove bits of the code, or write a bit of my own OS, or
something like that?

The other option I considered, is that I could write my own program,
but I could copy and modify the source for Csound opcodes into my
project to save time. This is not any kind of commercial venture, so I
assume there's no reason I can't do that right?

Cheers in advance for any thoughts you guys might have on this,

Pete

It looks like there are a couple of minimal linux builds out there,
but they look like they're pretty old, and I'm working on a much newer
dsPIC. I could give it that a shot, though I feel a little overwhelmed
with the idea :)

Forgetting about the OS for a second, is 512kB enough space for Csound then?

So my options are:

 - Get pre-existing minimal linux working
 - Build my own basic linux OS
 - Rewrite Csound for baremetal
 - Create all code from scratch

The option that daunts me the least is the last one. Is that ridiculous?

On Tue, Apr 26, 2016 at 1:50 PM, Rory Walsh  wrote:
> Can you get a minimal linux running on it?
>
> On 26 April 2016 at 13:29, Peter Burgess 
> wrote:
>>
>> I have already briefly discussed this in a thread, but I am wondering
>> again how viable it would be to get Csound working on a dsPIC. I am
>> about to start writing a little sythn project for it, so I need to
>> figure out if it'll be less hassle to write my own audio code from
>> scratch, or to try to build Csound for dsPIC.
>>
>> I don't know many of the factors I would need to consider to get this
>> working, but what I do know is that I have access to exactly 512kB of
>> program memory. Would that be enough to get a basic Csound built up
>> and running? I have access to both a C and C++ compiler for my dsPIC
>> device.
>>
>> What else would I need to bare in mind for this? I read a recent post
>> regarding a baremetal RPi Csound build, and it discussed pthreads and
>> other functions that rely on the OS. Does that mean I would need to
>> modify or remove bits of the code, or write a bit of my own OS, or
>> something like that?
>>
>> The other option I considered, is that I could write my own program,
>> but I could copy and modify the source for Csound opcodes into my
>> project to save time. This is not any kind of commercial venture, so I
>> assume there's no reason I can't do that right?
>>
>> Cheers in advance for any thoughts you guys might have on this,
>>
>> Pete
>>
>> --
>> http://algorythmradio.com
>> https://soundcloud.com/algorythmradio
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

How much data memory (RAM) is on the device?  That may be the more limiting factor.

48KB

It seems there is a more recent linux, Unison RTOS and POSIX RTOS from
http://rowebots.com

Apparently their OS can run on as little as 1.2KB of RAM and use as
little as 6KB of program memory.

Best case scenario, 46KB of RAM for Csound.

On Tue, Apr 26, 2016 at 2:36 PM, Dale Stewart
 wrote:
> How much data memory (RAM) is on the device?  That may be the more limiting
> factor.
>
> Sent using CloudMagic Email
> On Tue, Apr 26, 2016 at 8:32 AM, Peter Burgess
>  wrote:
>
> It looks like there are a couple of minimal linux builds out there,
> but they look like they're pretty old, and I'm working on a much newer
> dsPIC. I could give it that a shot, though I feel a little overwhelmed
> with the idea :)
>
> Forgetting about the OS for a second, is 512kB enough space for Csound then?
>
> So my options are:
>
> - Get pre-existing minimal linux working
> - Build my own basic linux OS
> - Rewrite Csound for baremetal
> - Create all code from scratch
>
> The option that daunts me the least is the last one. Is that ridiculous?
>
> On Tue, Apr 26, 2016 at 1:50 PM, Rory Walsh  wrote:
>> Can you get a minimal linux running on it?
>>
>> On 26 April 2016 at 13:29, Peter Burgess 
>> wrote:
>>>
>>> I have already briefly discussed this in a thread, but I am wondering
>>> again how viable it would be to get Csound working on a dsPIC. I am
>>> about to start writing a little sythn project for it, so I need to
>>> figure out if it'll be less hassle to write my own audio code from
>>> scratch, or to try to build Csound for dsPIC.
>>>
>>> I don't know many of the factors I would need to consider to get this
>>> working, but what I do know is that I have access to exactly 512kB of
>>> program memory. Would that be enough to get a basic Csound built up
>>> and running? I have access to both a C and C++ compiler for my dsPIC
>>> device.
>>>
>>> What else would I need to bare in mind for this? I read a recent post
>>> regarding a baremetal RPi Csound build, and it discussed pthreads and
>>> other functions that rely on the OS. Does that mean I would need to
>>> modify or remove bits of the code, or write a bit of my own OS, or
>>> something like that?
>>>
>>> The other option I considered, is that I could write my own program,
>>> but I could copy and modify the source for Csound opcodes into my
>>> project to save time. This is not any kind of commercial venture, so I
>>> assume there's no reason I can't do that right?
>>>
>>> Cheers in advance for any thoughts you guys might have on this,
>>>
>>> Pete
>>>
>>> --
>>> http://algorythmradio.com
>>> https://soundcloud.com/algorythmradio
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>>
>> Csound mailing list Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and features
>> can
>> be posted here
>
>
>
> --
> http://algorythmradio.com
> https://soundcloud.com/algorythmradio
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

That is, 46KB of RAM for Csound and the processing of any knobs and
buttons I want to rig up. Am I likely to need to add some external
RAM? That is a totally viable option

On Tue, Apr 26, 2016 at 2:49 PM, Peter Burgess
 wrote:
> 48KB
>
> It seems there is a more recent linux, Unison RTOS and POSIX RTOS from
> http://rowebots.com
>
> Apparently their OS can run on as little as 1.2KB of RAM and use as
> little as 6KB of program memory.
>
> Best case scenario, 46KB of RAM for Csound.
>
> On Tue, Apr 26, 2016 at 2:36 PM, Dale Stewart
>  wrote:
>> How much data memory (RAM) is on the device?  That may be the more limiting
>> factor.
>>
>> Sent using CloudMagic Email
>> On Tue, Apr 26, 2016 at 8:32 AM, Peter Burgess
>>  wrote:
>>
>> It looks like there are a couple of minimal linux builds out there,
>> but they look like they're pretty old, and I'm working on a much newer
>> dsPIC. I could give it that a shot, though I feel a little overwhelmed
>> with the idea :)
>>
>> Forgetting about the OS for a second, is 512kB enough space for Csound then?
>>
>> So my options are:
>>
>> - Get pre-existing minimal linux working
>> - Build my own basic linux OS
>> - Rewrite Csound for baremetal
>> - Create all code from scratch
>>
>> The option that daunts me the least is the last one. Is that ridiculous?
>>
>> On Tue, Apr 26, 2016 at 1:50 PM, Rory Walsh  wrote:
>>> Can you get a minimal linux running on it?
>>>
>>> On 26 April 2016 at 13:29, Peter Burgess 
>>> wrote:
>>>>
>>>> I have already briefly discussed this in a thread, but I am wondering
>>>> again how viable it would be to get Csound working on a dsPIC. I am
>>>> about to start writing a little sythn project for it, so I need to
>>>> figure out if it'll be less hassle to write my own audio code from
>>>> scratch, or to try to build Csound for dsPIC.
>>>>
>>>> I don't know many of the factors I would need to consider to get this
>>>> working, but what I do know is that I have access to exactly 512kB of
>>>> program memory. Would that be enough to get a basic Csound built up
>>>> and running? I have access to both a C and C++ compiler for my dsPIC
>>>> device.
>>>>
>>>> What else would I need to bare in mind for this? I read a recent post
>>>> regarding a baremetal RPi Csound build, and it discussed pthreads and
>>>> other functions that rely on the OS. Does that mean I would need to
>>>> modify or remove bits of the code, or write a bit of my own OS, or
>>>> something like that?
>>>>
>>>> The other option I considered, is that I could write my own program,
>>>> but I could copy and modify the source for Csound opcodes into my
>>>> project to save time. This is not any kind of commercial venture, so I
>>>> assume there's no reason I can't do that right?
>>>>
>>>> Cheers in advance for any thoughts you guys might have on this,
>>>>
>>>> Pete
>>>>
>>>> --
>>>> http://algorythmradio.com
>>>> https://soundcloud.com/algorythmradio
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>>
>>> Csound mailing list Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and features
>>> can
>>> be posted here
>>
>>
>>
>> --
>> http://algorythmradio.com
>> https://soundcloud.com/algorythmradio
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and features can
>> be posted here
>
>
>
> --
> http://algorythmradio.com
> https://soundcloud.com/algorythmradio