• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 469 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.

Original question:

[FAQ] AM64x & AM24x: How do I tell if there is software support for a hardware feature?

AM2434: Full description of perpheral devices on chip

Martin Feltgen
Prodigy 20 points
Part Number: AM2434
Other Parts Discussed in Thread: AM2432, AM2431,

Hello,

there where some thoughts about designing a product in our office that probably match to using a AM2434 or maybe the more smaller devices AM2432 or AM2431. It is an very early stage of design development with plenty of chances to decide against it ... but I'm on the way to think already a littel bit about software.

For this is my first touch to SITARA I may have missed some information from earlier member of this chip family: I noticed that every peripheral device on the chip tells about its type with a Vendor ID and a Device ID like PCI-Bus on a PC. So very nice, implementing Linux search for neccessary drivers is easy. But it could be possible that for this product a software of type bare metal will fit much better to the requiremtnts.

Currently I didn't found an exakt description for alle peripherals of this chip in datasheet nor manual. Exact does mean here: Exact description of the meaning of every bit of registers an a real deep description of functionality so that someone like me is able to create his own adapted drivers for them.

Where to find this information?

Thanks!

Martin

  • 0
    TI__Mastermind 24743 points

    Hello Martin,

    We're glad to hear you are considering AM243x as a solution here. I would highly recommend this course of action.

    The goal of our AM243x Technical Reference Manual document is to enable a customer to do full development for a given peripheral/interface without the need for high-level drivers (eg. bare-metal development). The register descriptions can be found in the last portion of each module chapter. I have provided some example screenshots below. Please follow up if there is any information you are looking for in particular that you cannot find.

    Best Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    Prodigy 20 points

    Hello Zackary,

    thank You for Your very detailed reply.

    But I still miss something. Of course its absolutely possible that it is my problem due to just having some blockade in my brain and not seeing the location where needed information is presented:

    Let me take chapter 12.2.1 from "spruim2c.pdf" as an example. This chapter describes ethernet port. I found the description of all registers as You mentioned beginning with chapter 12.2.1.6. Looks very nice. I believe I will succeed bring up ethernet interface working.

    A plenty of statements are done in the text that data ready to send will be delivered to ethernet port by a fifo, received data will be presented in another fifo. Where to find that data/fifo structures in memory? If I succeed to assemble a packet that should go over the ethernet wire to my host what to do with that data in memory to bring it up to the buffers handled by the switch and so on until it reaches the phy?

    Another example is USB port: On page 6938 in chapter 12.2.4.5 the statement is: "Details on the USB controller registers are not provided in this TRM. The existing Linux or RTOS drivers should be used for proper USB operation. ..."

    Ok, of course I could analyse Linux USB driver. But this will take plenty of time. So where to find the detailed hardware description for this USB peripheral?

    Many thanks!

    Martin

  • +1 in reply to Martin Feltgen
    TI__Mastermind 24743 points

    Hey Martin,

    You are welcome! We want to help how we can.

    Can you create new threads for these CPSW/Ethernet and USB questions? The new questions differ from the issue mentioned in the original thread. New threads will allow us to loop in the necessary subject matter experts to find solution and allow greater searchability when other engineers may have similar questions. Thank you!

    Best Regards,

    Zackary Fleenor