Circuitco is the manufacturer of all the BeagleBoards. They work for me. Right now, they are hosting the BeagleBoard.org Wiki. We hope to move it soon to another host.
Gerald On Mon, Oct 28, 2013 at 9:00 AM, Michael Vittiglio < [email protected]> wrote: > Thanks so much folks. I often find myself trudging through the IRC and > BeagleBoard.org site (along with google searches) to no real good results. > The circuitco site is definitely bookmarked at this point and I'll be sure > to RTFM going forward. Just curious, what's the difference between > CircuitCo & BeagleBoard.org? Seems like the wiki would be more publicly > visible on the latter. > > Either way, life is good and thanks a bunch. Just had a kid and baby brain > isn't helping. Thanks again and again and hopefully the next question will > be something tricky. :-) > > > On Sunday, October 27, 2013 4:42:23 PM UTC-4, Gerald wrote: > >> Hmm. Maybe go to the support wiki??? >> >> http://circuitco.com/support/**index.php?title=Updating_The_** >> Software#Checking_The_**Angstrom_Image_Version<http://circuitco.com/support/index.php?title=Updating_The_Software#Checking_The_Angstrom_Image_Version> >> >> Gerald >> >> >> >> On Sun, Oct 27, 2013 at 1:52 PM, Limpy <[email protected]> wrote: >> >>> # cat /etc/dogtag >>> will display the version of Angstrom installed on the device. >>> Once the eMMC is flashed successfully, the four USR LEDs will remain lit. >>> >>> >>> >>> On Sunday, October 27, 2013 7:08:11 AM UTC+5:30, Michael Vittiglio wrote: >>>> >>>> Gerald, >>>> I got the device today and I wanted to upgrade the firmware. Before I >>>> do that I wanted to ask if there's any way I can verify what's already >>>> installed and therefore know if I actually succeeded in updating the unit. >>>> Thanks for your help. >>>> >>>> On Wednesday, October 9, 2013 11:47:56 AM UTC-4, Gerald wrote: >>>>> >>>>> Yes it is covered. >>>>> >>>>> Gerald >>>>> >>>>> >>>>> >>>>> On Wed, Oct 9, 2013 at 10:08 AM, Michael Vittiglio < >>>>> [email protected]> wrote: >>>>> >>>>>> I purchased this unit at the Maker Faire (NYC a few weeks back). Does >>>>>> this unit still apply to RMA? >>>>>> >>>>>> I don't mind getting my hands a bit dirtier but it's hard to find >>>>>> documentation online. Is there a way we can blast/test it via FTDI (if >>>>>> not >>>>>> some other method)? >>>>>> >>>>>> >>>>>> On Wednesday, October 9, 2013 10:52:52 AM UTC-4, Gerald wrote: >>>>>> >>>>>>> Then I suggest you request an RMA and let the factory folks do it >>>>>>> for you. >>>>>>> >>>>>>> Gerald >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, Oct 7, 2013 at 9:53 PM, Michael Vittiglio < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Based on the instructions provided I've done everything to the >>>>>>>> letter. Unfortunately, this is all I see via the FTDI output via the >>>>>>>> terminal command "screen /dev/tty.usb... 115200": >>>>>>>> U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14) >>>>>>>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO >>>>>>>> Tx, SoftConn) >>>>>>>> >>>>>>>> On Friday, October 4, 2013 9:24:43 AM UTC-4, Gerald wrote: >>>>>>>> >>>>>>>>> That indicates there is nothing in flash and nothing on the SD >>>>>>>>> card that it can boot from. >>>>>>>>> >>>>>>>>> Gerald >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Oct 4, 2013 at 7:16 AM, Charles Steinkuehler < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> On 10/4/2013 6:46 AM, Michael Vittiglio wrote: >>>>>>>>>> > When trying to view what's happening via the FTDI the unity >>>>>>>>>> basically puts >>>>>>>>>> > out no output with the exception of the occasional "C". Is >>>>>>>>>> there any chance >>>>>>>>>> > that this can be repaired? As stated earlier in this thread, >>>>>>>>>> the "boot >>>>>>>>>> > button" option does not seem to work. >>>>>>>>>> >>>>>>>>>> The boot button completely bypasses the on-board eMMC, so if your >>>>>>>>>> 'bone >>>>>>>>>> is not booting correctly from SD card when holding the boot button >>>>>>>>>> during reset, you need to re-image the SD card. >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Charles Steinkuehler >>>>>>>>>> [email protected] >>>>>>>>>> >>>>>>>>>> >>>>>>>>> -- >>>>>>>> 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 beagleboard...@**googlegroups.**co**m. >>>>>>>> >>>>>>>> For more options, visit https://groups.google.com/**grou**** >>>>>>>> ps/opt_out <https://groups.google.com/groups/opt_out>. >>>>>>>> >>>>>>> >>>>>>> -- >>>>>> 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 beagleboard...@googlegroups.**co**m. >>>>>> For more options, visit >>>>>> https://groups.google.com/**grou**ps/opt_out<https://groups.google.com/groups/opt_out> >>>>>> . >>>>>> >>>>> >>>>> -- >>> 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 beagleboard...@**googlegroups.com. >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >> >> -- > 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/groups/opt_out. > -- 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/groups/opt_out.
