• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 719 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Which linux for AM3505?

Phillip Norisez
Intellectual 710 points
Other Parts Discussed in Thread: AM3505

I'm trying to settle on a linux to use in embedded medical firmware on TI AM3505's.  I have downloaded the TI SDK for the AM35x series and have noted peculiarities. The linux in the board support labs' source tree is different than the one in the main EVM source tree.  The EVM one looks to be a variant of 2.6.37, while the labs apear to be a 3.x.y variant.  Overlaying (by tree copy) the EVM linux source with the lab source results in a source tree that does not build an EVM kernel.  However, the EVM source is missing some key pieces of V4L2 needed by some driver suppliers, but the lab source has these features as EXPERIMENTAL..  These issues make the TI SDK undesirable for medical device development.  However, I'd like to stay with it because of the one-stop-shop aspect, assuming I can resolve the other issues, either by having my impression corrected or obtaining an SDK that doesn't have the problems.  Can anyone help me with facts or opinions based in fact?  Thanks.

The Aptina driver devloper is insisting that their driver should compile for a 2.6.37 kernel.  I've tried this many times, as described above with no luck.  Some part of V4L2 that Aptina needs seems to be missing from TI's 2.6.37 SDK for AM3050/17.  Can I please get some help!

  • 0
    Intellectual 320 points

    Hi Phillip,

    We work with companies developing medical devices that contain embedded Linux.  To keep the qualification process simple, we use a product design where a failure of Linux or applications running on Linux does not  create a hazard to humans.  Is this the design approach you are using or do you need to use a version of Linux that is certified for use in medical devices?

    If you have drivers that work on 2.6.37, then I would suggest you stick with 2.6.37 unless there is a kernel feature you require that necessitates moving to a newer kernel.

    Also, what Aptina sensor are you planning on using?

    Todd

  • 0 in reply to Todd Fischer98
    Intellectual 710 points

    You are correct about the design.

    I do not (yet) have a driver for the Aptina MT9M021 chip.  I am using the AR0130 chip's driver as a pattern.  My first move with it was to compile it under TI SDK 2.6.37 for AM3505/17.  This failed due to what appears to be an incompatibility with the 2.6.37 SDK's version of V4L2.  I have detailed this in emails to Aptina without clear result.  I am locked into using an AM3505 by design and purchased parts; and the MT9M021, by client edict.

    Is the 3.0.2 kernel incompatible with the AM3505/17?  If not, how do I go about getting it to work?

  • 0 in reply to Phillip Norisez
    Guru 31670 points

    Phillip,

    The sensor module driver can be ported to the newer kernel version. That might be an easier path.

  • 0 in reply to Renjith Thomas
    Intellectual 710 points

    Renjith, I thank you for responding.  I was able to take this issue up with Aptina, directly.  I will cancel this query.  My apologies for not gettting to this earlier.