On 22-12-2013 17:24, Bas de Bruijn wrote:
> On 22 Dec 2013, at 16:50, Bas Laarhoven <s...@xs4all.nl> wrote:
>
>> On 22-12-2013 16:00, Bas de Bruijn wrote:
>>> On 2013-12-22 15:25, Bas Laarhoven wrote:
>>>> On 22-12-2013 14:48, bdebru...@luminize.nl wrote:
>>>>>> But first check whether you've loaded the proper overlay as I wrote
>>>>>> above.
>>>>> check, I have made sure the line is as follows:
>>>>>
>>>>> optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONE-EMMC-2G,cape-bebopr-brdg
>>>>>
>>>>>>> To avoid misunderstandings maybe: when the line in the uEnv.txt is
>>>>>>> like this:
>>>>>>>
>>>>>>>
>>>>>>> optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONE-EMMC-2G,cape-bebopr-brdg
>>>>>>> LinuxCNC is starting up with the BeBoPr bridge(=+) cape
>>>>>>> configuration.
>>>>> but there is no difference.
>>>>> How can I check that the pins of J6, J7 and J8 match AINx?
>>>> I'm using the following shell script that writes all AIN values to
>>>> the
>>>> console in a loop.
>>>>
>>>> #!/bin/sh
>>>> while : ; do
>>>> for i in 4 5 6 ; do
>>>> echo -n "AIN${i}: `cat
>>>>
>>>> /sys/devices/ocp.2/44e0d000.tscadc/tiadc/iio\:device0/in_voltage${i}_raw`
>>>> "
>>>> sleep 1
>>>> done
>>>> echo ""
>>>> done
>>>>
>>> I get no response from the testscript.sh when I run ./testscript.sh
>>>
>>>> Then use a jumper to short the analog input. After one or two
>>>> readings,
>>>> the corresponding AIN
>>>> value should be (close to) zero as in the output shown below:
>>>>
>>>> AIN4: 3626 AIN5: 3631 AIN6: 3630
>>>> AIN4: 3628 AIN5: 3631 AIN6: 3628
>>>> AIN4: 3628 AIN5: 3631 AIN6: 3
>>>> AIN4: 3628 AIN5: 3631 AIN6: 1
>>>> AIN4: 3628 AIN5: 3632 AIN6: 3629
>>>> AIN4: 33 AIN5: 3633 AIN6: 3630
>>>> AIN4: 40 AIN5: 3632 AIN6: 3630
>>>> AIN4: 39 AIN5: 3632 AIN6: 3629
>>>>
>>>> Note: I've only tested this with the cape-bebopr-brdg device tree
>>>> overlay loaded, but I guess
>>>> it should also work with Charles' overlay. Do check the output of
>>>> "dmesg | grep capemgr" to
>>>> make sure the proper one is loaded!
>>> did I make a typo? is cape-bebopr-brdg the right one to disable? below
>>> the results of "dmesg | grep capemgr"
>>>
>>> linuxcnc@arm:~$ dmesg | grep capemgr
>>> [ 0.000000] Kernel command line: console=ttyO0,115200n8
>>> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONE-EMMC-2G,cape-bebopr-brdg
>>> root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait fixrtc ip=
>>> [ 1.803347] bone-capemgr bone_capemgr.8: Baseboard:
>>> 'A335BNLT,0A5C,3513BBBK1445'
>>> [ 1.811134] bone-capemgr bone_capemgr.8:
>>> compatible-baseboard=ti,beaglebone-black
>>> [ 1.819013] bone-capemgr bone_capemgr.8: Skipping disabled cape with
>>> part# BB-BONE-EMMC-2G
>>> [ 1.827716] bone-capemgr bone_capemgr.8: Skipping disabled cape with
>>> part# BB-BONELT-HDMI
>>> [ 1.863879] bone-capemgr bone_capemgr.8: slot #0: No cape found
>>> [ 1.900984] bone-capemgr bone_capemgr.8: slot #1: No cape found
>>> [ 1.938093] bone-capemgr bone_capemgr.8: slot #2: No cape found
>>> [ 1.975203] bone-capemgr bone_capemgr.8: slot #3: No cape found
>>> [ 1.981465] bone-capemgr bone_capemgr.8: slot #4: specific override
>>> [ 1.988070] bone-capemgr bone_capemgr.8: bone: Using override eeprom
>>> data at slot 4
>>> [ 1.996109] bone-capemgr bone_capemgr.8: slot #4:
>>> 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
>>> [ 2.006623] bone-capemgr bone_capemgr.8: slot #5: specific override
>>> [ 2.013240] bone-capemgr bone_capemgr.8: bone: Using override eeprom
>>> data at slot 5
>>> [ 2.021279] bone-capemgr bone_capemgr.8: slot #5:
>>> 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
>>> [ 2.031324] bone-capemgr bone_capemgr.8: slot #6: specific override
>>> [ 2.037924] bone-capemgr bone_capemgr.8: bone: Using override eeprom
>>> data at slot 6
>>> [ 2.045961] bone-capemgr bone_capemgr.8: slot #6:
>>> 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
>>> [ 2.056340] bone-capemgr bone_capemgr.8: Skipping loading of
>>> disabled cape with part# BB-BONE-EMMC-2G
>>> [ 2.066018] bone-capemgr bone_capemgr.8: Skipping loading of
>>> disabled cape with part# BB-BONELT-HDMI
>>> [ 2.075800] bone-capemgr bone_capemgr.8: initialized OK.
>>> [ 2.081423] bone-capemgr bone_capemgr.8: loader: before slot-6
>>> BB-BONELT-HDMIN:00A0 (prio 2)
>>> [ 2.090277] bone-capemgr bone_capemgr.8: loader: check slot-6
>>> BB-BONELT-HDMIN:00A0 (prio 2)
>>> [ 2.119407] bone-capemgr bone_capemgr.8: loader: after slot-6
>>> BB-BONELT-HDMIN:00A0 (prio 2)
>>> [ 2.134288] bone-capemgr bone_capemgr.8: slot #6: Requesting
>>> firmware 'cape-boneblack-hdmin-00A0.dtbo' for board-name
>>> 'Bone-Black-HDMIN', version '00A0'
>>> [ 2.169086] bone-capemgr bone_capemgr.8: slot #6: dtbo
>>> 'cape-boneblack-hdmin-00A0.dtbo' loaded; converting to live tree
>>> [ 2.192143] bone-capemgr bone_capemgr.8: slot #6: #2 overlays
>>> [ 2.213163] bone-capemgr bone_capemgr.8: slot #6: Applied #2
>>> overlays.
>>> [ 2.220039] bone-capemgr bone_capemgr.8: loader: done slot-6
>>> BB-BONELT-HDMIN:00A0 (prio 2)
>>> [ 96.964424] bone-capemgr bone_capemgr.8: part_number
>>> 'BB-LCNC-BEBOPRBR', version 'N/A'
>>> [ 96.974155] bone-capemgr bone_capemgr.8: slot #7: generic override
>>> [ 96.980767] bone-capemgr bone_capemgr.8: bone: Using override eeprom
>>> data at slot 7
>>> [ 96.988868] bone-capemgr bone_capemgr.8: slot #7: 'Override Board
>>> Name,00A0,Override Manuf,BB-LCNC-BEBOPRBR'
>>> [ 96.999584] bone-capemgr bone_capemgr.8: slot #7: Requesting part
>>> number/version based 'BB-LCNC-BEBOPRBR-00A0.dtbo
>>> [ 97.010611] bone-capemgr bone_capemgr.8: slot #7: Requesting
>>> firmware 'BB-LCNC-BEBOPRBR-00A0.dtbo' for board-name 'Override Board
>>> Name', version '00A0'
>>> [ 97.032216] bone-capemgr bone_capemgr.8: slot #7: dtbo
>>> 'BB-LCNC-BEBOPRBR-00A0.dtbo' loaded; converting to live tree
>>> [ 97.046479] bone-capemgr bone_capemgr.8: slot #7: #2 overlays
>>> [ 97.081274] bone-capemgr bone_capemgr.8: slot #7: Applied #2
>>> overlays.
>>> [ 98.437787] bone-capemgr bone_capemgr.8: part_number
>>> 'cape-bone-iio', version 'N/A'
>>> [ 98.447088] bone-capemgr bone_capemgr.8: slot #8: generic override
>>> [ 98.453718] bone-capemgr bone_capemgr.8: bone: Using override eeprom
>>> data at slot 8
>>> [ 98.461769] bone-capemgr bone_capemgr.8: slot #8: 'Override Board
>>> Name,00A0,Override Manuf,cape-bone-iio'
>>> [ 98.472128] bone-capemgr bone_capemgr.8: slot #8: Requesting part
>>> number/version based 'cape-bone-iio-00A0.dtbo
>>> [ 98.482956] bone-capemgr bone_capemgr.8: slot #8: Requesting
>>> firmware 'cape-bone-iio-00A0.dtbo' for board-name 'Override Board Name',
>>> version '00A0'
>>> [ 98.500404] bone-capemgr bone_capemgr.8: slot #8: dtbo
>>> 'cape-bone-iio-00A0.dtbo' loaded; converting to live tree
>>> [ 98.513739] bone-capemgr bone_capemgr.8: slot #8: #1 overlays
>>> [ 98.541904] bone-capemgr bone_capemgr.8: slot #8: Applied #1
>>> overlays.
>> The log shows that you've successfully loaded the HDMIN, LCNC-BEBOPR and
>> BONE-IIO overlays.
>>
>> I don't have a LinuxCNC system available to test at the moment, so maybe
>> Charles
>> or someone else can comment.
>>
>> Maybe you're bitten by the ever changing device numbering scheme: Have a
>> look in
>> /sys/devices for the name of the ocp.? node. The script assumes it's
>> ocp.2, but maybe
>> it ocp.3 or something else in your situation.
> ocp.2 seems there
>
>> Or do a "find /sys/devices/ -name in_voltage4_raw" on the command line
>> and see if
>> there is a difference with the path used in the script.
> linuxcnc@arm:~$ find /sys/devices/ -name in_voltage4_raw
> /sys/devices/ocp.2/44e0d000.tscadc/tiadc/iio:device0/in_voltage4_raw
>
> It’s there, but the script doesn’t work. :(
Weird, I cut and pasted that line from the file that I've used to test
your board before shipment.
And if you enter the following command (on the command line):
cat `find /sys/devices/ -name in_voltage[346]_raw`
Doesn't that give you three values?
-- Bas
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
