That is a question for Jason. He is the TI guy. Gerald
On Wed, May 20, 2015 at 11:15 AM, Chris Morgan <[email protected]> wrote: > Isn't 10 years just the total life of the chip/product line? This > doesn't say TI is going to be advancing that processor line. > > Consider that right now the Pi2 has a quad core processor. If TI isn't > going to be keeping up with that kind of pace of processor development > for the AM335x line (or maybe its the am3xxx line?) is a single core > 1GHz processor going to be relevant in a year or five? Is it staying > relevant right now given the other SBCs at a similar > price/capabilities standpoint? > > I can say that internal to where I work we've been eyeing the quad > core ARM processor boards that have appeared. We like the BBB a ton > and we'd love to see it go quad core and double up on the ram for a > similar price point. Maintaining cape/software compatibility would be > a big win imo. > > Chris > > > > > On Wed, May 20, 2015 at 11:43 AM, William Hermans <[email protected]> > wrote: > > Also, we're talking 10 years down the road here. Whose to say what will > > happen by then. Take a look at the MSP430 line of MCUs for example. I do > not > > know the exact history of the MCU line, but it became popular, and it is > > still with us . . . refreshes have been made, changes / variations have > been > > made. Now we have many different classes of MSP430 MCUs for different use > > cases. > > > > Lately TI even "extended" the MSP430 line by mixing in the M4F processor > . > > For "high end applications". Is it truly an MSP430 though ? Here, I think > > the more important question should be: "Does it even matter ?" > > > > On Wed, May 20, 2015 at 8:30 AM, William Hermans <[email protected]> > wrote: > >>> > >>> That's a real problem if the interface doesn't stay compatible in the > >>> future. When I look at Arduino, capes are compatible with previous > >>> versions. Same goes with the Raspberry Pi. Version 1 to version 2 > adds > >>> features, but generally keeps compatibility between them. With the > >>> Beagle's, each version has had a radically different form factor and > >>> support. White's started with an extra header, removed for the blacks, > >>> breaking some capes. > >> > >> > >> But we're not talking about an Arduino, or an rPI. We're talking about: > >> > >> a) a beagleBOARD class of system > >> b) Then trying to compare it to the beagleBONE class of system. > >> > >> They're not the same. Also, if cape compatibility is the true motivation > >> for this discussion. See this as an opportunity, not a hindrance. > >> > >> On Wed, May 20, 2015 at 8:04 AM, Gerald Coley <[email protected]> > >> wrote: > >>> > >>> BeagleBone Black needed to be cheap. something had to go. Rest of the > >>> expansion signals are the same and those signals are still there on the > >>> board.. > >>> > >>> I disagree that the changes were radical. I fact, we lowered the cost > and > >>> added features. > >>> > >>> If we change to another processor, the pin muxing changes. To comply > with > >>> your desire to keep them all the same, you have just made my case. > >>> > >>> Gerald > >>> > >>> > >>> On Wed, May 20, 2015 at 9:42 AM, Walter Schilling <[email protected]> > >>> wrote: > >>>> > >>>> That's a real problem if the interface doesn't stay compatible in the > >>>> future. When I look at Arduino, capes are compatible with previous > >>>> versions. Same goes with the Raspberry Pi. Version 1 to version 2 > adds > >>>> features, but generally keeps compatibility between them. With the > >>>> Beagle's, each version has had a radically different form factor and > >>>> support. White's started with an extra header, removed for the > blacks, > >>>> breaking some capes. > >>>> > >>>> On Tuesday, May 19, 2015 at 9:30:37 AM UTC-5, RobertCNelson wrote: > >>>>> > >>>>> On Tue, May 19, 2015 at 9:24 AM, Philip <[email protected]> > wrote: > >>>>> > On Tuesday, May 19, 2015 at 10:14:20 AM UTC-4, Gerald wrote: > >>>>> >> > >>>>> >> If I knew that, I would have mentioned that. I would say maybe > late > >>>>> >> September. We hope to have a few beta boards in about 6 weeks. > Jason > >>>>> >> is > >>>>> >> handling who gets those boards. Right now, we are going back into > >>>>> >> layout to > >>>>> >> fix yet another TI "feature". > >>>>> >> > >>>>> > > >>>>> > Will the cape interface stay the same? > >>>>> > >>>>> Nope, and don't mention stuff like that, we don't want to give Gerald > >>>>> a heart attack.. > >>>>> > >>>>> Regards, > >>>>> > >>>>> -- > >>>>> Robert Nelson > >>>>> https://rcn-ee.com/ > >>>> > >>>> -- > >>>> For more options, visit http://beagleboard.org/discuss > >>>> --- > >>>> You received this message because you are subscribed to the Google > >>>> Groups "BeagleBoard" group. > >>>> To unsubscribe from this group and stop receiving emails from it, send > >>>> an email to [email protected]. > >>>> For more options, visit https://groups.google.com/d/optout. > >>> > >>> > >>> > >>> > >>> -- > >>> Gerald > >>> > >>> [email protected] > >>> http://beagleboard.org/ > >>> http://circuitco.com/support/ > >>> > >>> -- > >>> For more options, visit http://beagleboard.org/discuss > >>> --- > >>> You received this message because you are subscribed to the Google > Groups > >>> "BeagleBoard" group. > >>> To unsubscribe from this group and stop receiving emails from it, send > an > >>> email to [email protected]. > >>> For more options, visit https://groups.google.com/d/optout. > >> > >> > > > > -- > > For more options, visit http://beagleboard.org/discuss > > --- > > You received this message because you are subscribed to the Google Groups > > "BeagleBoard" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Gerald [email protected] http://beagleboard.org/ http://circuitco.com/support/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
