Greetings everyone! I'll start:
Which CPU is being targeted?
I think I know, but I'd like to come up to speed on the datasheet and
TRM, so knowing which part(s) to review would be helpful.
AM57xx. Datasheet and TRM not yet available externally. Still working the issue for availability. Should have it once we have boards.
Gerald
AM57xx. Datasheet and TRM not yet available externally. Still working the issue for availability. Should have it once we have boards.
Two things:
- The Reply-To: isn’t working so when I hit the reply, I get the person, not the group
- Will TI provide processor details under an NDA?
Regards,
John
From: Gerald Coley <gerald@beagleboard.org>
Date: Thursday, July 3, 2014 at 1:25 PM
To: Charles Steinkuehler <charles@steinkuehler.net>
Cc: <beagleboard-x15@googlegroups.com>
Subject: Re: Which CPUAM57xx. Datasheet and TRM not yet available externally. Still working the
issue for availability. Should have it once we have boards.Two things:
The Reply-To: isn’t working so when I hit the reply, I get the person, not
the group
I noticed that too. We probally set that up 6 years ago on the
beagleboard group and forgot about it. 
Will TI provide processor details under an NDA?
From the doc's i've seen, it's an omap5 + another couple years of
tweaks/enhancements.
So that's one reason i started publishing this image:
http://elinux.org/BeagleBoardDebian#OMAP5432_uEVM
Regards,
As I understand it, NDA will not be required to get the documents. What will be required is to get the documents ready.
What is different here is that the X15 will be the base board of the new TI EVM. So TI is providing direct support of the kernel and drivers. Plan is to release a 3.14 kernel as it is slated for LTS. TI has a 3.15 so back porting is going on now to get the 3.14 ready. We are in the middle of bring up now.
We only have four Alpha boards at the moment. We plan to build another 10. The beta boards will be the ones that we provide more of.
A snapshot is below showing what is working so far:
BASIC FUNCTIONALITY
Power Yes
Clocks Yes
Processor Yes
DDR1 Yes
DDR2 Yes
uSD Yes
eMMC Yes
Ethernet 1 Yes
Ethernet 2 Yes
HDMI Yes
LEDs Yes
eSATA Yes
Debug Serial Yes
Power Button Yes
Reset Button Yes
JTAG Yes
Temp Sensor Yes
Audio
USB Client
USB Host
USB1
USB2
USB3
USB4
PCIe 1
PCIe 2
RTC
Gerald
Hi Gerald,
Can you check with the TI kernel developers if they are going to add RPMSG
and RemoteProc support for the AM57xx. This is an RPC between the
processors on this chip. This is important because when TI decided not to
add DM3730 support, there was no way to develop DSP applications after
Linux Kernels V3.2. RPMSG is similar to SYSLINK and some refer to it as
SYSLINK V3, but the benefit is that it is in mainline.
There is some support for the OMAP5 so I¹m hoping that it isn¹t a big deal
to add support for the AM57xx. This is needed to load the code onto the
CortexM4 or DSP processors, start and stop the applications running on
these processors and for messaging between the CortexA15, CortexM4 and
DSP.
Regards,
John
From: beagleboard-x15@googlegroups.com [mailto:beagleboard-
x15@googlegroups.com] On Behalf Of John Syn
Sent: Wednesday, July 09, 2014 3:04 PM
To: beagleboard-x15@googlegroups.com
Subject: Re: Which CPUHi Gerald,
Can you check with the TI kernel developers if they are going to
add RPMSG
and RemoteProc support for the AM57xx. This is an RPC between the
processors on this chip. This is important because when TI decided
not to
add DM3730 support, there was no way to develop DSP applications
after
Linux Kernels V3.2. RPMSG is similar to SYSLINK and some refer to
it as
SYSLINK V3, but the benefit is that it is in mainline.
This will be available in the 3.14 LTS kernel released from TI.
From: beagleboard-x15@googlegroups.com [mailto:beagleboard-
x15@googlegroups.com] On Behalf Of John Syn
Sent: Wednesday, July 09, 2014 3:04 PM
To: beagleboard-x15@googlegroups.com
Subject: Re: Which CPUHi Gerald,
Can you check with the TI kernel developers if they are going to
add RPMSG
and RemoteProc support for the AM57xx. This is an RPC between the
processors on this chip. This is important because when TI decided
not to
add DM3730 support, there was no way to develop DSP applications
after
Linux Kernels V3.2. RPMSG is similar to SYSLINK and some refer to
it as
SYSLINK V3, but the benefit is that it is in mainline.This will be available in the 3.14 LTS kernel released from TI.
That is really good news. Thank you.
Is there any update on what progress has been made and anticipated dates for doc release, beta testing etc?
What is the state of the kernel. I’ve seen some patches for AM57xx on the Linux-ARM mailing list, but nothing comprehensive.
Regards,
John
Kernel work is in mainline. Robert can help there. I have a handful of platforms, but not many. We are going for our second spin as we speak so it will be a while before we have the second version. I sent Robert the first board out yesterday. I am not sure who will get the remaining two boards that I have.
It will be a while longer, at least a month, before I release any sort of documents. There is still a lot of work to do in that area and I am totally swamped getting the boards through layout and up and running.
Gerald
Kernel work is in mainline. Robert can help there. I have a handful of platforms, but not many. We are going for our second spin as we speak so it will be a while before we have the second version. I sent Robert the first board out yesterday. I am not sure who will get the remaining two boards that I have.
It will be a while longer, at least a month, before I release any sort of documents. There is still a lot of work to do in that area and I am totally swamped getting the boards through layout and up and running.
Gerald
Thanks for the update. Good to hear you are making progress.
BTW, have you given any thought to using a plugin eMMC5.0 like that on the ODROID board:
http://hardkernel.com/main/products/prdt_info.php?g_code=G140448267127&tab_idx=2
http://hardkernel.com/main/products/prdt_info.php?g_code=G140470746714
This achieves significant speed improvement:
http://www.samsung.com/global/business/semiconductor/file/media/Samsung_eMMC_2013_Final_HR-0.pdf
Regards,
John
No consideration at all.
Gerald
No consideration at all.
No problem, but please consider adding it to the wish list for next time. Currently, I think you have PCIe and SATA, so those interfaces will work fine also.
Regards,
John
As you say I have SATA so I am not sure why I would need this.
Gerald
As you say I have SATA so I am not sure why I would need this.
Space and power. Adding a 2.5 inch hard disk is way bigger and needs far more power. I was going to say cost, but looking at Amazon for 64GB SSD, cost is actually less.
Maybe there would be a way to accommodate SSD in a M.2 form factor. Seems like the cost for M.2 SSD is way less than eMMC5.0 of a similar size.
http://en.wikipedia.org/wiki/M.2
Regards,
John
I am not changing the design. I have too far to go with what I have to make that happen without having to do a complete new layout.
Gerald
Space and power. Adding a 2.5 inch hard disk is way bigger and needs far
more power. I was going to say cost, but looking at Amazon for 64GB SSD,
cost is actually less.Maybe there would be a way to accommodate SSD in a M.2 form factor. Seems
like the cost for M.2 SSD is way less than eMMC5.0 of a similar size.
We just need a cape for that!
(and just wrap a small 4 inch sata cable..)
Regards,
I am not changing the design. I have too far to go with what I have to make that happen without having to do a complete new layout.
Sorry, I never meant to imply changing your board. I was thinking about some adapter board.
Regards,
John
I am not interested in talking about capes or enabling capes until cape manger is dead. Capes would have 240 pins as well which equals plug it in and leave it…
Gerald
Yep, that would work.