Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Thread

Re: [AVR-Chat] Mil Std 1553

Re: [AVR-Chat] Mil Std 1553

2005-03-18 by Jim White

Thanks.

I just looked at DDC and have posted them a question on the minimum number 
of I/O lines needed to interface Their ACE to a embedded controller.  The 
data sheet would indicate about 40 - as in a PCI bus or the like.  A 
nonstarter for us.

What we really need is a serial to 1553 converter sort of like the simple 
serial to RS-422 chips on the market, but which does the protocol as 
well.  Or even the CP2101 and similar RS-232 to USB converters.

Jim
Show quoted textHide quoted text
>Jim White said:
> >
> > Anybody know of a Mil Std. 1553 implementation on something like a
> > M128?  Looks like there are transceiver chips out there but you have to
> > do  the protocol in your software ??
>
>Jim,
>
>I seriously doubt anyone is doing this directly in a microcontroller (or
>any other processor for that matter).  You can buy specialized chips to do
>it from a number of vendors, but they are usually expensive.  I know that
>at least Actel has a soft IP core to put in an FPGA which has the
>advantage of providing radiation hardness too.  And it would certainly be
>doable in VHDL or Verilog if you have the time to develop it yourself.
>
>Mike W4LNA
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>

Re: [AVR-Chat] Mil Std 1553

2005-03-18 by Mike Murphree

Jim White said:
>
> Thanks.
>
> I just looked at DDC and have posted them a question on the minimum
> number  of I/O lines needed to interface Their ACE to a embedded
> controller.  The  data sheet would indicate about 40 - as in a PCI bus
> or the like.  A  nonstarter for us.
>
> What we really need is a serial to 1553 converter sort of like the
> simple  serial to RS-422 chips on the market, but which does the
> protocol as  well.  Or even the CP2101 and similar RS-232 to USB
> converters.

Jim,

You haven't said what mode of operation you need, i.e. bus controller or
remote terminal?

Assuming for a minute that you need to be a remote terminal (RT), one
method that would be easy to interface to a micro is shared (dual-port)
memory.  The 1553 bus hybrid would store and read data to buffers assigned
for each subaddress that you need.  The micro would be free to read and
write data from its port.  You may need to provide some register decoding
as well as the memory decode for the dual-port memory.  This will be the
least intrusive method to handle for the microcontroller.

Mike

Winavr Installation problem error on compile [Cross Post]

2005-03-19 by wbounce

Sorry for the Cross post but I am not sure the avr-gcc0list got my
message

I am trying to prepare an old laptop to run winavr 3.4.1. Because the
laptop only has com I am using a null modem to transfer file from my
main PC. I can not transfer the whole installation file (the comm just
drops on really big files) so I have been transferring only the pieces I
need. I have transferred programmers notepad but can not get it working
because of oleaut32.dll components missing. That is ok Ill just use
notepad to edit. But when I run make all in the project directory make
calls avr-gcc with all the same options as on my main computer and it
returns 

Avr-gcc installation problem, can not exec 'ccl': No such file or
directory C:\robot\winavr\utils\bin\make.exe *** [fire.o] error 1


I have both C:\robot\winavr\utils\bin and C:\robot\winavr\bin in my
path.

I also have searched my main computer for a file with that name and I
finally found it under the winavr\libexec\gcc\avr\3.4.1\install-tools
directory which I had not copied so I copied that whole directory and
the lib dir only the gcc subdirectory.  

So now I have the winavr\avr, winavr\bin, winavr\lib, winavr\libexec,
winavr\mfile, winavr\pn, winavr\sample, winavr\utils directories. 

Now make all gives me a long list of 

c:/robot/winavr/bin/../lib/gcc/avr/3.4.1/../../../../avr/include/avr/pgm
space.h 69:20: stdedef.h: No such file or directory And 
c:/robot/winavr/bin/../lib/gcc/avr/3.4.1/../../../../avr/include/string.
h 78:error: parse error before "size_t"


What is wrong with this set up?

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.