[beagleboard] Enable I2C-1

[namrathamenon10]

I am using beaglebone black rev-c, with pins 19 and 20, i am able to detect 
the ADC connected on I2C-2.
How can i detect it with connection given to 17 and 18 because i am not 
able to detect it normally

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/95dc53fe-d029-4381-876d-07d22513657d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Blue; Pinout diagram / System Reference Manual ?

[nmsps10]

On Sunday, July 9, 2017 at 4:23:09 AM UTC+1, Jeff Albrecht wrote:
>
> I'm looking for a detailed pinout of the BBBlue. Hopefully similar to 
> this, or the many similar ones, for the BBB.
>
>
>
> The BBBlue FAQ has a Pinouts 
> section with 
> this picture. For instance I found the SPI connector but I don't know the 
> pin numbers and pin names on the connector to hook up the hardware.
>
> [image: Image result for beaglebone blue pinout]
>
> I found Pin Multiplexing  on 
> the Strasown Design site. It's getting closer but not a definitive 
> reference for me. Perhaps this could be added to the Pinouts of the BBBlue 
> FAQ.
>
> I have a 6-wire JST-SH connector. Not sure where pin 1 is on the connector 
> or which pin is SCLK, MOSI, MIS0 SS* etc...
>
> Does a detailed pinout for the BBBlue exist?
>
> The BeagleBone Blue  page refers to the 
> System Reference Manual on the github page but I'm not finding it. Does the 
> System Reference Manual for the 'blue exist?
>
> Browse the BeagleBone Blue Github page 
>  to find all available 
> hardware specifications such as:
>
>
>- Bill of materials
>  - PCB source files
>  - Manufacturing files
>  - Schematic (PDF and source)
>  - System Reference Manual
>   
>  
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f877900c-d1f3-4886-9275-d346215f58b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Blue; Pinout diagram / System Reference Manual ?

[nmsps10]

Hello Jeff,

See if this helps. I did it using the schematics and a multimeter. It's 
kind of hand made but





On Sunday, July 9, 2017 at 4:23:09 AM UTC+1, Jeff Albrecht wrote:
>
> I'm looking for a detailed pinout of the BBBlue. Hopefully similar to 
> this, or the many similar ones, for the BBB.
>
>
>
> The BBBlue FAQ has a Pinouts 
> section with 
> this picture. For instance I found the SPI connector but I don't know the 
> pin numbers and pin names on the connector to hook up the hardware.
>
> [image: Image result for beaglebone blue pinout]
>
> I found Pin Multiplexing  on 
> the Strasown Design site. It's getting closer but not a definitive 
> reference for me. Perhaps this could be added to the Pinouts of the BBBlue 
> FAQ.
>
> I have a 6-wire JST-SH connector. Not sure where pin 1 is on the connector 
> or which pin is SCLK, MOSI, MIS0 SS* etc...
>
> Does a detailed pinout for the BBBlue exist?
>
> The BeagleBone Blue  page refers to the 
> System Reference Manual on the github page but I'm not finding it. Does the 
> System Reference Manual for the 'blue exist?
>
> Browse the BeagleBone Blue Github page 
>  to find all available 
> hardware specifications such as:
>
>
>- Bill of materials
>  - PCB source files
>  - Manufacturing files
>  - Schematic (PDF and source)
>  - System Reference Manual
>   
>  
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/edb4c85a-a34d-4a21-96e0-0a8673375974%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] recommendation for a symbolic debugger

[John Syne]

You need arm-linux-gnueabihf-gdb and it needs to be the same as your compiler 
version used to build your executable. 

Regards,
John




> On Aug 1, 2017, at 1:44 PM, clarkbriggs...@gmail.com wrote:
> 
> William etal,
> Pointing to Molloy was a good hint. I watched him do it and around minute 31 
> he starts into remote debugging. He uses Eclipse and some cross tool chain, 
> but I didn't watch that. I am using the TI CCS v7.2 on Windows 7x64 which is 
> Eclipse based, but not cross compiling with their included tools.
> My configuration is somewhat different from Molloy's. He is cross compiling 
> so the sources AND the binary are present on the dev machine with Eclipse. I 
> have only the sources on my dev machine since I compile on the BBB.
> Issue 1. When creating a remote debug configuration in CCS/Eclipse the Main 
> tab field "C/C++ Application:" apparently wants the local binary on the dev 
> machine. It isn't happy without it and won't move forward at all. If I drag 
> the binary from the BBB back to the dev workspace and point at it, it will go 
> on.
> What is the correct way to configure this environment (source and dbg on Win 
> dev host; source, binaries and gdbserver on BBB)?
> Issue 2. So with a copy of the application binary on the dev host, launching 
> a remote debugging session leads to a gripe from the gdbserver about not 
> understanding the MI command list-features.  The console shows the connection 
> on the BBB target successfully launches gdbserver with the configured port, 
> the absolute path to the executable and the arguments. After the "listening 
> on port 2345" echo it terminates with the gripe about the MI command.
> Groping der google suggests this is often due to not having the correct 
> architecture gdb on the dev host selected. When installing CCSv7 I picked 
> only the arm tools for the AM33xx family processor. In the debug 
> configuration debugger tab main tab GDB debugger is the default setting 
> "gdb".  There is a Browse button to go looking through the installed 
> ti/ccsv7/tools/compiler, but the only gdb in the TI tools I can find is 
> C:\ti\ccsv7\tools\compiler\gcc-arm-none-eabi-6-2017-q1-update\bin\arm-none-eabi-gdb.exe.
>  that gdb echoes as it starts "This GDB was configured as 
> "--host=i686-w64-mingw32 --target=arm-none-eabi"." then warns "warning: A 
> handler for the OS ABI "GNU/Linux" is not built into this configuration of 
> GDB. Attempting to continue with the default arm settings." It then quits 
> with a complaint that no source was available.
> Maybe this is really a TI CCS specific setting. Earlier John pointed to CCS 
> so maybe he can provide some direction.
> Thanks,
> Hugh
> 
> On Thursday, July 27, 2017 at 4:14:58 PM UTC-7, William Hermans wrote:
> 
> 
> On Thu, Jul 27, 2017 at 4:13 PM, William Hermans  > wrote:
> This is probably the best guide you're going to find on the subject.
> 
> https://www.youtube.com/watch?v=T9yFyWsyyGk 
> 
> 
> Never used it myself( I do not cross compile ), but I'm confident DR Molly's 
> instructions work.
> 
> Just in case it's not clear, R Molly shows how to setup remote debugging 
> towards the end I think. Been a while since I've watched this. 
> 
> 
> -- 
> 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+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/fa591c36-14bb-4237-8286-0076e36c4407%40googlegroups.com
>  
> .
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/587433A3-9E03-428E-A642-A003BB9EF79D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Reading analog in on the stretch (9.1) images

[clarkbriggs101]

I have lived on BBB + Robotics Cape in James' world for some time. While I 
haven't done this with a Blue, I suspect what I did can work there too. I 
did do his installation (for a Rev C BBB and a Rev D Robotics Cape). With 
Robert's help I put the Capemgr back in the DTs and added the capemgr 
partno boot line for BB-ADC.  This seems to be a workable combination of 
the two worlds. My premise is that I don't try to do both at once.  That 
is, I don't run any of the rc_* apps or services while trying to read the 
ADCs from /sys/bus/iio. So far it seems to work for me.
Hugh

On Monday, July 31, 2017 at 11:44:09 AM UTC-7, Mark A. Yoder wrote:

> Yup, this is the Blue.
> In there short term is there an easy way to turn off the robotics stuff 
> and get easy access to the analog in?
>
> In the long term, what will it take to convert James' robot stuff to 
> libiio?  I might take a shot at it if it isn't too hard.
>
> --Mark
>
> On Friday, July 28, 2017 at 5:56:30 PM UTC-4, RobertCNelson wrote:
>>
>> On Fri, Jul 28, 2017 at 4:40 PM, Mark A. Yoder  
>> wrote: 
>> > How do I read AIN on the latest images?  I don't know where to find it 
>> in 
>> > /sys/ 
>>
>> Hi Mark, 
>>
>> This is with the Blue right? 
>>
>> James' got the ADC tied up in mmap for the Robotic's cape library.. 
>>
>>
>> https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/libraries/mmap/rc_mmap_gpio_adc.c
>>  
>>
>> We need to convert his library to use libiio, then we can just enable 
>> the ADC's as an iio device and share usage with the library.. 
>>
>> https://analogdevicesinc.github.io/libiio/ 
>>
>> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e2d3829f-6af9-4c00-b63d-4ec891db2be7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] recommendation for a symbolic debugger

[clarkbriggs101]

William etal,
Pointing to Molloy was a good hint. I watched him do it and around minute 
31 he starts into remote debugging. He uses Eclipse and some cross tool 
chain, but I didn't watch that. I am using the TI CCS v7.2 on Windows 7x64 
which is Eclipse based, but not cross compiling with their included tools.
My configuration is somewhat different from Molloy's. He is cross compiling 
so the sources AND the binary are present on the dev machine with Eclipse. 
I have only the sources on my dev machine since I compile on the BBB.
Issue 1. When creating a remote debug configuration in CCS/Eclipse the Main 
tab field "C/C++ Application:" apparently wants the local binary on the dev 
machine. It isn't happy without it and won't move forward at all. If I drag 
the binary from the BBB back to the dev workspace and point at it, it will 
go on. 
What is the correct way to configure this environment (source and dbg on 
Win dev host; source, binaries and gdbserver on BBB)?
Issue 2. So with a copy of the application binary on the dev host, 
launching a remote debugging session leads to a gripe from the gdbserver 
about not understanding the MI command list-features.  The console shows 
the connection on the BBB target successfully launches gdbserver with the 
configured port, the absolute path to the executable and the arguments. 
After the "listening on port 2345" echo it terminates with the gripe about 
the MI command.
Groping der google suggests this is often due to not having the correct 
architecture gdb on the dev host selected. When installing CCSv7 I picked 
only the arm tools for the AM33xx family processor. In the debug 
configuration debugger tab main tab GDB debugger is the default setting 
"gdb".  There is a Browse button to go looking through the installed 
ti/ccsv7/tools/compiler, but the only gdb in the TI tools I can find is 
C:\ti\ccsv7\tools\compiler\gcc-arm-none-eabi-6-2017-q1-update\bin\arm-none-eabi-gdb.exe.
 
that gdb echoes as it starts "This GDB was configured as 
"--host=i686-w64-mingw32 --target=arm-none-eabi"." then warns "warning: A 
handler for the OS ABI "GNU/Linux" is not built into this configuration of 
GDB. Attempting to continue with the default arm settings." It then quits 
with a complaint that no source was available.
Maybe this is really a TI CCS specific setting. Earlier John pointed to CCS 
so maybe he can provide some direction.
Thanks,
Hugh

On Thursday, July 27, 2017 at 4:14:58 PM UTC-7, William Hermans wrote:

>
>
> On Thu, Jul 27, 2017 at 4:13 PM, William Hermans  > wrote:
>
>> This is probably the best guide you're going to find on the subject.
>>
>> https://www.youtube.com/watch?v=T9yFyWsyyGk
>>
>> Never used it myself( I do not cross compile ), but I'm confident DR 
>> Molly's instructions work.
>>
>
> Just in case it's not clear, R Molly shows how to setup remote debugging 
> towards the end I think. Been a while since I've watched this. 
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/fa591c36-14bb-4237-8286-0076e36c4407%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Ubuntu 14.04 image

[cjt0027]

Hi, could someone point me to the latest Ubuntu 14.04 image for BBB. Thanks.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ff16cb2e-1f58-4c5f-bd12-7ba04d62296f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] JTAG beagle bone black with buspirate and openocd

[Jeff Andich]

There are some TI training videos on building/debugging u-boot/spl via JTAG 
and Code Composer Studio, which appear to be useful, thus far.  Granted 
they appear to be a few year's old:

https://training.ti.com/linux-board-porting-series-module-5-installing-code-composer-studio?cu=399066.
 
 

There you can also find the links to the other applicable training modules.


On Monday, July 31, 2017 at 3:45:16 PM UTC-5, john3909 wrote:
>
> I haven’t heard of anyone successfully using Openocd on BBB even though I 
> have seen many users try it. I would recommend using Blackhawk USB200 with 
> Code Composer Studio (CCSV7) as it has everything you need to get started. 
>
> Regards,
> John
>
>
>
>
> On Jul 31, 2017, at 5:20 AM, devar...@gmail.com  wrote:
>
> Hello
>
> I am very new to JTAG and i am trying to do the setup for jtag in 
> beaglebone black(BBB) rev c board using buspirate(BP) and openocd.
> I have installed the P2 header in BBB manually. I have connected the BBB 
> and BP as follows
>
> JTAG BP BBB 
> TMS CS P2(1) P2 header pin 1 
> TDI MOSI P2(3) 
> VTREF VPU P2(5) 
> TDO MISO P2(7) 
> TCK CLK P2(11) 
> TRST AUX P2(2) 
> GRND GND P2(10)
>
>
> I am using my user configuration file(BP_userconfig.cfg) for openocd which 
> has following content.
>
> source [find interface/buspirate.cfg]
>
> buspirate_vreg 0
> buspirate_mode open-drain
> buspirate_pullup 1
> reset_config srst_only
> buspirate_port /dev/ttyUSB0
>
> source [find board/ti_beaglebone_black.cfg]
>
> Now while running the command *sudo openocd -f  BP_userconfig.cfg* I am 
> getting following error.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *lenova@lenova-ThinkPad-T410:~/jiten/JTAG$ sudo openocd -f 
> BP_userconfig.cfg Open On-Chip Debugger 0.10.0+dev-00167-g29cfe9c 
> (2017-07-20-14:08)Licensed under GNU GPL v2For bug reports, read
> http://openocd.org/doc/doxygen/bugs.html 
> Warn : Adapter driver 'buspirate' 
> did not declare which transports it allows; assuming legacy JTAG-onlyInfo : 
> only one transport option; autoselect 'jtag'srst_only separate 
> srst_gates_jtag srst_open_drain connect_deassert_srsttrst_and_srst separate 
> srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srstadapter 
> speed: 1000 kHztrst_and_srst separate srst_gates_jtag trst_push_pull 
> srst_open_drain connect_deassert_srstInfo : Buspirate Interface ready!Info 
> : This adapter doesn't support configurable speedInfo : JTAG tap: 
> am335x.jrc tap/device found: 0x2b94402f (mfg: 0x017 (Texas Instruments), 
> part: 0xb944, ver: 0x2)Info : JTAG tap: am335x.dap enabledError: JTAG-DP 
> STICKY ERRORError: Could not initialize the APB-AP*Does anyone have any 
> idea about this error? and do i need to do anything else in BBB apart from 
> installing P2 header?
> Please let me know if i am doing anything wrong.
>
> Thanks in advance.
>
> Regards
> jitendriya
>
>
> -- 
> 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 .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/94f1fafb-03d7-43cc-80d1-8249e2735bcd%40googlegroups.com
>  
> 
> .
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c7068f7e-8e48-4826-b1cf-d7aff8545fc4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] disable usb tethering

[Sebastián Sáez]

Hi!,

It's posible disable tethering on USB0 and USB1?

I do not use this and I'm not sure but I think it causes me problems with 
DNS.


regards,
Sebastián

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/61db1667-9d2e-4884-b82a-b16c6248ec45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Load Cell & HX711 Board with Beaglebone Black

[Graham]

Well, the interface for the HX711 is not I2C, so you can stop messing with 
that.
It is a unique custom serial interface.
Most likely solution is to bit bang the interface using several GPIO pins.

You should bring it up in layers.
Start by learning to read the raw value from the part at a low level, 
before you start trying to process the results.

Write some diagnostic code, so you can dump the bits as they come in.

Get an oscilloscope, so you can watch the bits wiggle and read them on the 
scope.

--- Graham

==




On Tuesday, August 1, 2017 at 6:40:59 AM UTC-5, prad wrote:
>
> Hi all,
>
> I'm trying to interface a load cell strain gauge with the HX711 breakout 
> board (Sparkfun) and the Beaglebone Black using Python. I haven't been 
> successful in getting any readings from GPIO or I2C and am truly stuck. I 
> was trying to copy/implement code I found for reading a load cell on 
> Raspberry Pi, but that was also unsuccessful, despite the code working just 
> fine on my Raspberry Pi. 
>
> https://gist.github.com/Richard-Major/64e94338c2d08eb1221c2eca9e014362#file-hx711-py-L25
> This is the code I'm trying to use and I adapted it to the Beaglebone 
> using Adafruit's BBIO library, to no avail. 
> I'm not sure if I'm skipping some step or anything but no research I've 
> done has proved to be successful in aiding me accomplish my task. 
>
> Thanks for any help!
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d01633ff-98ab-4fec-9b91-6e28142cef5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Load Cell & HX711 Board with Beaglebone Black

[prad]

Hi all,

I'm trying to interface a load cell strain gauge with the HX711 breakout 
board (Sparkfun) and the Beaglebone Black using Python. I haven't been 
successful in getting any readings from GPIO or I2C and am truly stuck. I 
was trying to copy/implement code I found for reading a load cell on 
Raspberry Pi, but that was also unsuccessful, despite the code working just 
fine on my Raspberry Pi. 
https://gist.github.com/Richard-Major/64e94338c2d08eb1221c2eca9e014362#file-hx711-py-L25
This is the code I'm trying to use and I adapted it to the Beaglebone using 
Adafruit's BBIO library, to no avail. 
I'm not sure if I'm skipping some step or anything but no research I've 
done has proved to be successful in aiding me accomplish my task. 

Thanks for any help!

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/371f7f03-f32a-4996-ab53-2ca26e2a31d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] DHCP issues

[Kurt Talke]

Hi Jason, James,

I’m running Debian 8.8 from 7/1/17, and I’m having an issue where the BBB no 
longer shows up as the default IP 192.168.7.2

I’ve narrowed it down to the script which enables the device tree overlay, or 
installing the robotics cape from source code.

Once I reboot, my BBB shows up as a self assigned IP 169.254.44.139, and I 
can’t connect to it.  

The DT script works for 8.7, but not 8.8 or the 9.1 versions.

Any ideas?



-Kurt

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7E50F170-746E-4725-8C94-0E7183C9C4F5%40eng.ucsd.edu.
For more options, visit https://groups.google.com/d/optout.