I don't know how to change Mode of the GPIO. Still searching lol

Le vendredi 5 mars 2021 à 14:28:08 UTC+1, Lucas SOLDA a écrit :

> Thank you, now I can add files ! 
>
> Now I try to make GPIO work
>
> Le vendredi 5 mars 2021 à 14:07:37 UTC+1, [email protected] a 
> écrit :
>
>> Add a partition or another storage device. To mount once booted.
>>
>> Add a partition to your storage, 
>> so that you have a smallish boot image partition which will be read-only 
>> and a data partition which is read/write.
>>
>> Add another storage device,
>> so that you have read/write storage which is not just volatile RAM-disk. 
>> I think we used FTP or IDE to copy files to the R/W storage and add to the 
>> PATH.
>>
>>
>> On Friday, 5 March 2021 at 10:51:37 UTC [email protected] wrote:
>>
>>> Well, we found a solution to just use the prebuilt image I attached 
>>> earlier but know it is only in read mode. I don't the username and the 
>>> password so I can't put my librairies to usr/lib...
>>> What a shame that OS
>>>
>>> Le vendredi 5 mars 2021 à 08:32:14 UTC+1, Lucas SOLDA a écrit :
>>>
>>>> Thank you all for your answers, I will try to answer you in one post.
>>>>
>>>> *"You never told us if your product was using custom hardware or 
>>>> incorporating the beaglebone board."*
>>>> If I use something else than QNX, I won't be able to port all the work 
>>>> made by my colleague. In fact, we are creating and developping our own 
>>>> electronic cards and we use QNX to programm them. We wanted to use the 
>>>> BeagleBone Black to realize some tests (test bench) on our products and by 
>>>> using QNX, we just should have ported our already existing programs. I'm 
>>>> not the person in charge of programming, builing, compiling QNX but I 
>>>> develop the product in which our cards are installed. This is why I don't 
>>>> understand everything about BSP, QNX, etc. 
>>>>
>>>> *"As you ask, what is missing from the BSP that needs building?" : *We 
>>>> want to add the IsaGraf drivers in order to make the BeagleBone Black a 
>>>> target source in which we can send programms. I think, the BSp does need 
>>>> to 
>>>> be modified in that case , doesn't it ?
>>>>
>>>> We cannot upgrade our QNX development system because it would be too 
>>>> dangerous. We have only one licence and we don't want to destroy anything.
>>>> Le vendredi 5 mars 2021 à 04:07:15 UTC+1, [email protected] a 
>>>> écrit :
>>>>
>>>>> Upgrading QNX Development System.
>>>>>
>>>>> From memory, it is more involved than downloading a SP file and 
>>>>> running it. 
>>>>> You have to unzip the download.
>>>>> Find the old files.
>>>>> Copy the old files to a backup name or folder.
>>>>> Copy the new files from the zip archive, over the old files.
>>>>>
>>>>> On Friday, 5 March 2021 at 02:59:32 UTC [email protected] wrote:
>>>>>
>>>>>> As you ask, what is missing from the BSP that needs building? If 
>>>>>> nothing, the next step is getting network setup to connect with SSH and 
>>>>>> IDE, possibly run network file system client to access files on your 
>>>>>> development PC.
>>>>>>
>>>>>>
>>>>>> Re: File System Image (I cannot remember all the details) 
>>>>>>
>>>>>> You use an IDE BSP project to build a bootable image including your 
>>>>>> application (started by boot script which also loads any needed drivers).
>>>>>> This bootable image can be copied to a flash drive or accessed from a 
>>>>>> network file system (during development).
>>>>>> The bootable image may be compressed read-only and expanded into a 
>>>>>> RAM backed 'disk' or expanded on the fly.
>>>>>>
>>>>>> During application development, the bootable image boots to "sh" 
>>>>>> command line. You can run any missed commands in the boot script.
>>>>>> You use the IDE to connect the debugger over ethernet to QNX process 
>>>>>> and temporary download your debug version application. The IDE debugger 
>>>>>> can 
>>>>>> run, pause, single-step, etc.
>>>>>>
>>>>>> In the BSP project you edit a configuration which controls what is 
>>>>>> included in the boot image. You add or remove files from the prebuilt 
>>>>>> folder. You edit the start up script to load and configure drivers. 
>>>>>>
>>>>>> In QNX drivers and file-systems are server processes/programs which 
>>>>>> respond to certain messages. Most QNX programs and applications are 
>>>>>> servers 
>>>>>> which wait on a message queue. 
>>>>>> QNX provides a POSIX wrapper server which converts system calls into 
>>>>>> send-wait-reply messages or convert signals into send-and-forget pulse 
>>>>>> messages. QNX also has time limited blocking on both send and receive 
>>>>>> messages.
>>>>>>
>>>>>> The QNX micro-kernel schedules process execution, allocates memory 
>>>>>> for messages, and transfers messages between processes.
>>>>>> It is supported server programs to implement the OS functions. 
>>>>>>
>>>>>> On Friday, 5 March 2021 at 00:22:31 UTC lazarman wrote:
>>>>>>
>>>>>>> The file system isn't the BSP. This part supplies all architecture 
>>>>>>> specific(ASP) functions like Cache,MMU and the board specific drivers 
>>>>>>> for 
>>>>>>> on chip peripherals on all cores.
>>>>>>>
>>>>>>> If I understand Lucas correctly and you look at the zip file he 
>>>>>>> provided  the support is limited as to drivers and he needs to 
>>>>>>> recompile 
>>>>>>> that and add to it.
>>>>>>> That's the only reason he can't use the binary.
>>>>>>>
>>>>>>> From your response it appears you didn't need to modify this.
>>>>>>>
>>>>>>> I would guess the x15 BSP is more inclusive and mature but doubt it 
>>>>>>> provided loading  c6x  DSP code or Cortex M4 code but it's not relevant 
>>>>>>> to 
>>>>>>> Lucas.
>>>>>>>
>>>>>>> Your experience with support below 
>>>>>>>
>>>>>>> <<We did not have gold level support, questions often take days to 
>>>>>>> be answered <<and often direct you to documentation and someone who can 
>>>>>>> program it for <<you at a cost. It might be non paying users only had 
>>>>>>> community support
>>>>>>>
>>>>>>> To me it sounds like Lucas has the tin can  support which is similar 
>>>>>>> to open source support.
>>>>>>>
>>>>>>> Ie post and pray😉
>>>>>>>
>>>>>>> Sent from Yahoo Mail on Android 
>>>>>>> <https://overview.mail.yahoo.com/mobile/?.src=Android>
>>>>>>>
>>>>>>> On Thu, Mar 4, 2021 at 4:34 PM, Robert Forsyth
>>>>>>> <[email protected]> wrote:
>>>>>>>
>>>>>>> Old product used QNX 6, had long (6 months~1 year) trial licence for 
>>>>>>> 7.0, I think I was able to build the file-system image, but could not 
>>>>>>> get 
>>>>>>> the driver for vector graphics processor to recognize the hardware, so 
>>>>>>> the 
>>>>>>> tiger demo did not work on AM5728 BB X15. (This is probably because 
>>>>>>> GC320 
>>>>>>> is a compositor, not vector-graphics like GC355.)
>>>>>>>
>>>>>>> We did not have gold level support, questions often take days to be 
>>>>>>> answered and often direct you to documentation and someone who can 
>>>>>>> program 
>>>>>>> it for you at a cost. It might be non paying users only had community 
>>>>>>> support, if you are trying to sell QNX, you need to make it easy as pie 
>>>>>>> to 
>>>>>>> switch from something free.
>>>>>>>
>>>>>>> QNX development works well, once hardware and software development 
>>>>>>> is setup, I would say it is easier to develop and debug communicating 
>>>>>>> multi-process applications on QNX than Windows, Linux or RTOS (QNX IPC 
>>>>>>> coincided with what I learned at uni); if you don't try to do it the 
>>>>>>> Linux 
>>>>>>> way. RTOS probably has the closest IPC ability to QNX, but way cruder; 
>>>>>>> QNX 
>>>>>>> has lovely variable length message passing.
>>>>>>> Technical and library problems seemed often like Windows: you know 
>>>>>>> what you want to do, and you found a function which seems like it would 
>>>>>>> do 
>>>>>>> what you want, but the documentation says something like "setWombat( x 
>>>>>>> ) 
>>>>>>> sets the wombat to x" and you find you have spent hours/days finding 
>>>>>>> how it 
>>>>>>> works. 
>>>>>>> Some drivers were based on Linux version, using QNX version 
>>>>>>>
>>>>>>> Linux and RTOS are free, process isolation with separate processors 
>>>>>>> is cheapish, but takes up PCB space. I think Qt sold infotainment, QNX 
>>>>>>> would useful for process isolation on one (multi-core) processor, so 
>>>>>>> you 
>>>>>>> could isolate the infotainment application from the air-bag monitor.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, 4 Mar 2021 at 18:41, 'Mark Lazarewicz' via BeagleBoard <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>> Hi Robert 
>>>>>>>
>>>>>>> That's good to know I saw the x15 7.0 BSP
>>>>>>> Where you able to rebuild BSP sources ?
>>>>>>> And do they actually respond to support questions for educational 
>>>>>>> users? 😉
>>>>>>>
>>>>>>>
>>>>>>> Looks like most of their revenue comes from automobile infotainmen 
>>>>>>> at least the people hiring recently 
>>>>>>>
>>>>>>> Mark
>>>>>>>
>>>>>>>
>>>>>>> Sent from Yahoo Mail on Android 
>>>>>>> <https://overview.mail.yahoo.com/mobile/?.src=Android>
>>>>>>>
>>>>>>> On Thu, Mar 4, 2021 at 12:35 PM, [email protected]
>>>>>>> <[email protected]> wrote:
>>>>>>> 7.0 worked on X15 except vector graphics
>>>>>>>
>>>>>>> On Thursday, 4 March 2021 at 17:51:42 UTC lazarman wrote:
>>>>>>>
>>>>>>> Page 15 of the pdf you sent we need that document
>>>>>>>
>>>>>>> . Please refer to the QNX SDP 6.6.0 BSPs guide, available as part of 
>>>>>>> the QNX Software Development Platform OS Core Components documentation
>>>>>>>
>>>>>>> I also need you to see if you can get the latest BSP referenced in 
>>>>>>> my previous post I think it was 7.0
>>>>>>>
>>>>>>> I have uncovered at least 5 problems with your original posting its 
>>>>>>> a QXX documentation mismatch not you. I am concerned this stuff you 
>>>>>>> started 
>>>>>>> with is very old and probally not supported by Blackberry
>>>>>>>
>>>>>>> You have to start simple and slowly and logically so be patient 
>>>>>>> before we start with 7.0 we need the document above
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, March 3, 2021, 12:58:16 PM CST, 'Mark Lazarewicz' via 
>>>>>>> BeagleBoard <[email protected]> wrote: 
>>>>>>>
>>>>>>>
>>>>>>> These commands you entered  are where? uboot?
>>>>>>>
>>>>>>> --> fatload mmc 0 0x81000000 prebuilt-bsp-ti-beaglebone.ifs
>>>>>>> --> go 0x81000000
>>>>>>>
>>>>>>> Why not automate these commands ?
>>>>>>>
>>>>>>> <<<if I compile the BSP without modifying anything, I should get the 
>>>>>>> prebuilt image, right ?
>>>>>>>
>>>>>>> In theory if you have a license BUT 
>>>>>>> some RTOS companies dont supply BSP source code unless you paid fees 
>>>>>>>
>>>>>>> So do you need to modify BSP>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, March 3, 2021, 09:03:22 AM CST, Lucas SOLDA <
>>>>>>> [email protected]> wrote: 
>>>>>>>
>>>>>>>
>>>>>>> Mark,
>>>>>>>
>>>>>>> I have a BeagleBone Black REV C.
>>>>>>> There was nothing on the SD before. I did not touch to the EMC so I 
>>>>>>> think there is nothing inside.
>>>>>>> My company has a QNX 6.5.0 SP1 licence and here is the list of the 
>>>>>>> tools installed on my computer: 
>>>>>>>
>>>>>>> [image: 1.png]
>>>>>>> [image: 2.jpg]
>>>>>>>
>>>>>>> First, I formated my SD card in FAT32, I made it active by using 
>>>>>>> diskpart and I copied the MLO and then the u-boot files. I took them 
>>>>>>> from 
>>>>>>> here : 
>>>>>>> https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone
>>>>>>> Bootloader modules# 
>>>>>>> <https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone#section-TiAm335Beaglebone-BootloaderModules>
>>>>>>>  --> 
>>>>>>> *"Click here 
>>>>>>> <http://community.qnx.com/sf/frs/do/viewRelease/projects.bsp/frs.texas_instruments_am335_beaglebo.mlo_and_u_boot_binaries_for_beag>
>>>>>>>  to 
>>>>>>> download the MLO and u-boot binaries for the new Beaglebone Black 
>>>>>>> platform. 
>>>>>>> "*
>>>>>>>
>>>>>>> After that, I downloaded the BSP files: QNX Neutrino 6.5.0 SP1# 
>>>>>>> <https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone#section-TiAm335Beaglebone-QNXNeutrino6.5.0SP1>
>>>>>>>  -->  *Download *Project Downloads 
>>>>>>> <http://community.qnx.com/sf/frs/do/viewRelease/projects.bsp/frs.texas_instruments_am335_beaglebo.qnx_650_bsp_beaglebone_1_00_zip>
>>>>>>>  --> bsp-nto650-ti-beaglebone-sp1-trunk-201209071340.zip 
>>>>>>> <https://community.qnx.com/sf/frs/do/downloadFile/projects.bsp/frs.texas_instruments_am335_beaglebo.qnx_650_bsp_beaglebone_1_00_zip/frs36857?dl=1>
>>>>>>> (I attach MLO, u-boot and BSP to this mail)
>>>>>>> After extracting, I copied the file "prebuilt-bsp-ti-beaglebone.ifs" 
>>>>>>> in the "image" folder to my sdcard and I could succesfully launch QNX 
>>>>>>> on my 
>>>>>>> BBB by typing these commands :
>>>>>>> --> fatload mmc 0 0x81000000 prebuilt-bsp-ti-beaglebone.ifs
>>>>>>> --> go 0x81000000
>>>>>>>
>>>>>>> That worked perfectly. 
>>>>>>>
>>>>>>> When I try to compile the image by myself it gets complicated.
>>>>>>>
>>>>>>> if I compile the BSP without modifying anything, I should get the 
>>>>>>> prebuilt image, right ?
>>>>>>> The problem is that, when I do that, I have the message I gave in 
>>>>>>> the first post and it says that I compile with QNX 6.5.0 and not with 
>>>>>>> QNX 
>>>>>>> 6.5.0 SP1 (whereas it is installed).
>>>>>>>
>>>>>>> *"I'm guessing you have no support forum or no ones replying at 
>>>>>>> QNX?" *I don't have support anymore and the only thing the told me 
>>>>>>> is that I don't use QNX 6.5.0 SP1
>>>>>>>
>>>>>>> I don't know what to do anymore and the QNX SDP is not on my 
>>>>>>> computer so I can't use it whenever I want
>>>>>>>
>>>>>>> Le mercredi 3 mars 2021 à 15:03:47 UTC+1, lazarman a écrit :
>>>>>>>
>>>>>>> Let's start with some history about what rev board you have , what 
>>>>>>> was on SD before and whats in  the emc now and details about tools you 
>>>>>>> installed to build BSP and QNX and exactly the BSP file's you are 
>>>>>>> compiling 
>>>>>>> as well as your goals. Are you trying to eventually modify the BSP 
>>>>>>> source?
>>>>>>> I'm guessing you have no support forum or no ones replying at QNX?
>>>>>>> I need a clear picture of what you did exactly installing tools as 
>>>>>>> in did you install multiple times etc etc 
>>>>>>>
>>>>>>> I'll look at the pdf you supplied and ponder whether it worthwhile 
>>>>>>> and practical to find my Beagleboard,Whites,blacks or even Pandaboard.
>>>>>>> power supplies may be hard to match I've moved a lot. I guess a 
>>>>>>> black would be easy for me to find but may be in storage.
>>>>>>>
>>>>>>>  Also maybe they will let me reeducate myself as I'm not working on 
>>>>>>> a commercial product and give me access otherwise it's harder to help.
>>>>>>>
>>>>>>> Hopefully I can get you on the right path 
>>>>>>>
>>>>>>> Mark
>>>>>>>
>>>>>>>
>>>>>>> Sent from Yahoo Mail on Android 
>>>>>>> <https://overview.mail.yahoo.com/mobile/?.src=Android>
>>>>>>>
>>>>>>> On Wed, Mar 3, 2021 at 1:15 AM, Lucas SOLDA
>>>>>>> <[email protected]> wrote:
>>>>>>> I can send you the files if you don't have an account.
>>>>>>>
>>>>>>> I use the MLO and u-boot files for beaglebone black from this link : 
>>>>>>> "Click *here 
>>>>>>> <http://community.qnx.com/sf/frs/do/viewRelease/projects.bsp/frs.texas_instruments_am335_beaglebo.mlo_and_u_boot_binaries_for_beag>*
>>>>>>>  to 
>>>>>>> download the MLO and u-boot binaries for the new Beaglebone Black 
>>>>>>> platform.".
>>>>>>>
>>>>>>> The fact you pointed is troubling. I don't understand why the BSP is 
>>>>>>> unchanged  between beagleboard and BBB.
>>>>>>>
>>>>>>> "*Perhaps if you disassemble the binary and look at the bone memory 
>>>>>>> map and the linker map and the u boot load address for QNX there's a 
>>>>>>> mismatch *
>>>>>>> *do you have access to BSP users guide? " *
>>>>>>>
>>>>>>> I will try to do that but I'm not an expert. I have access to the 
>>>>>>> user guide yes... 
>>>>>>> Le mercredi 3 mars 2021 à 08:09:38 UTC+1, Lucas SOLDA a écrit :
>>>>>>>
>>>>>>> @lazarman, in fact I'm not a student and I have a company account 
>>>>>>> with a QNX 6.5.0 SP1 licence. I have also already registered to the" 
>>>>>>> QNX 
>>>>>>> Software Development Platform 6.5.x (registration)" link that you gave 
>>>>>>> me. 
>>>>>>> The problem is not the fact that I can't download and install the SDP 
>>>>>>> but 
>>>>>>> the fact that when I build the image thanks to the BSP, I don't have 
>>>>>>> the 
>>>>>>> same result as the prebuilt image
>>>>>>>
>>>>>>> Le mercredi 3 mars 2021 à 00:24:34 UTC+1, lazarman a écrit :
>>>>>>>
>>>>>>> Hi Robert I think Lucas is saying he's only trying to build the BSP 
>>>>>>> not QNX.
>>>>>>>
>>>>>>> I did this 10 years ago and I also had the latest  BSP guides I 
>>>>>>> tried getting these and you need a customer login. It says it's free 
>>>>>>> for 
>>>>>>> education but again BlackBerry bought this.
>>>>>>>
>>>>>>> What's funny is this link below takes you to another page which says 
>>>>>>> we support these processors. It also says you should lose the latest 
>>>>>>> version's 
>>>>>>>
>>>>>>> QNX SDP 7.0 BSP for Texas Instruments AM335x (Beaglebone Black)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>  https://blackberry.qnx.com/en/support/qnx-board-support-packages
>>>>>>>
>>>>>>> Clicking on the above link  next to the BSP you see another page 
>>>>>>> saying 
>>>>>>>
>>>>>>>
>>>>>>> The QNX Software Center enables you to download and manage QNX 
>>>>>>> Software Development Platform version 7.x and related products. PDF 
>>>>>>> documentation and Licensing information relating to QNX SDP 7 and 
>>>>>>> related 
>>>>>>> products can also be found here. *IMPORTANT: SDP 7.x licenses are 
>>>>>>> initially delivered within the myQNX License Manager 
>>>>>>> <https://www.qnx.com/account/dashboard/%22> and MUST be assigned to 
>>>>>>> users 
>>>>>>> via the license manager in order for them to access the product.*
>>>>>>>
>>>>>>> And no code just a login.
>>>>>>>
>>>>>>> That BSP Lucas references is over 6 year's old.
>>>>>>>
>>>>>>> Even 10 year's ago you needed a valid company domain and email 
>>>>>>> address for QNX I know GreenHills and  maybe WindRiver as well wouldn't 
>>>>>>> even reply to a free email domain and definitely won't give you a 30 
>>>>>>> day 
>>>>>>> level  license key that the license manager needed 
>>>>>>>
>>>>>>> Lucas is this for education 😉?? I know it's frustrating you might 
>>>>>>> have to reach out them about
>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> 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].
>>>>>>> To view this discussion on the web visit 
>>>>>>>
>>>>>>> https://groups.google.com/d/msgid/beagleboard/0059314a-4779-4d14-90c4-72f26aa34996n%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/beagleboard/0059314a-4779-4d14-90c4-72f26aa34996n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>> -- 
>>>>>>> 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].
>>>>>>> To view this discussion on the web visit 
>>>>>>>
>>>>>>> https://groups.google.com/d/msgid/beagleboard/1258199165.156495.1614797442235%40mail.yahoo.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/beagleboard/1258199165.156495.1614797442235%40mail.yahoo.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>> -- 
>>>>>>> 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].
>>>>>>> To view this discussion on the web visit 
>>>>>>>
>>>>>>> https://groups.google.com/d/msgid/beagleboard/5af047c4-77bc-4151-8ab8-72601505a84fn%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/beagleboard/5af047c4-77bc-4151-8ab8-72601505a84fn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>> -- 
>>>>>>> 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].
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/beagleboard/134662134.438935.1614883309815%40mail.yahoo.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/beagleboard/134662134.438935.1614883309815%40mail.yahoo.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> Robert Forsyth BEng (Hons) MIET
>>>>>>>
>>>>>>> 14 Bywater Way
>>>>>>> Donnington
>>>>>>> Chichester
>>>>>>> West Sussex
>>>>>>> PO19 8RW
>>>>>>>
>>>>>>> tel:+44-7958-621-653 <+44%207958%20621653>
>>>>>>> mailto:[email protected]
>>>>>>> http://www.purple-bobby.org.uk
>>>>>>>
>>>>>>> -- 
>>>>>>> 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].
>>>>>>>
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/beagleboard/CAPkKDSLA8aWLWkrjX1WmP2Cobktc-x%2BcuZkAtnz-k8gwykXL3Q%40mail.gmail.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/beagleboard/CAPkKDSLA8aWLWkrjX1WmP2Cobktc-x%2BcuZkAtnz-k8gwykXL3Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c6e246b7-ac21-4365-97b2-00657eab9c7dn%40googlegroups.com.

Reply via email to