[TriEmbed] Using SPI

[Carl Nobile]

Pete,

Great, this is what I think I needed to know. So from what you said I can
just write my specific SPI code and not worry about it interfering with the
programmer when I'm uploading a revised HEX file. I have noticed that
programmers don't use the SS pin which I will need for my own code. So if
the programmer never pulls down the SS pin then my code is not going to see
any action on the SPI bus. Why I didn't see this before I don't now, but
that why we have this group.

Thanks all,
Carl



On Wed, Apr 2, 2014 at 12:57 PM, Pete Soper <pete at soper.us> wrote:

>  No sweat, Carl. I do this very frequently, assuming we're talking about
> Atmel chips. For programming purposes the reset line is yanked in specific
> ways that invokes the chip's low level programming protocol, while for SPI
> devices there is a specific chip select line for each device that avoids
> interference with either the programming scenario or some other SPI
> peripheral.
>
> -Pete
>
>
> On 04/01/2014 09:40 PM, Carl Nobile wrote:
>
> Hi all,
>
>  Is it possible to use the SPI pins on a mircorcontroller for two
> purposes? For example used to burn the hex image and when not burning the
> image then in normal running mode used to control motor speed, etc. or
> something similar. My guess is yes, but I haven't figured out how to do it.
>
>  Carl
>
>
>
> _______________________________________________
> Triangle, NC Embedded Computing mailing listTriEmbed at triembed.orghttp://mail.triembed.org/mailman/listinfo/triembed_triembed.org
> TriEmbed web site: http://TriEmbed.org
>
>
>
> _______________________________________________
> Triangle, NC Embedded Computing mailing list
> TriEmbed at triembed.org
> http://mail.triembed.org/mailman/listinfo/triembed_triembed.org
> TriEmbed web site: http://TriEmbed.org
>
>


-- 
-------------------------------------------------------------------------------
Carl J. Nobile (Software Engineer)
carl.nobile at gmail.com
-------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.triembed.org/pipermail/triembed_triembed.org/attachments/20140402/50d0a041/attachment.htm>