[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

PS:

>From my point of view, I as a developer should not provide the packages.

It'd be best to include libpruio in RCNs build farm, in order to get a 
fresh binary for each new update. He startet that project, but never 
finished jet. I don't know why.

Perhaps libpruio users should motivate him to continue. (I'm ready for 
supporting, if necessary.)

Regards

-- 
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/8137fe11-b28d-4643-815c-349588fd6457%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

Hi Hans!

Am Dienstag, 5. Mai 2020 00:47:22 UTC+2 schrieb Hans Leeuw:
>
> I have upgraded and I get this warning while compiling my program (using 
> rb):
>

I avoid updates, if possible. It takes too much time to optimize the boot 
time again and again.
 

> /usr/bin/ld: warning: libtinfo.so.5, needed by 
> /usr/lib/gcc/arm-linux-gnueabihf/8/../../../libpruio.so, may conflict with 
> libtinfo.so.6
>
> (4.19.94-bone44), buster.
>

This library isn't much important. It gets linked due to a single PRINT 
statement at the end of the destructor, sending a message to the error 
channel, if any. (Since the PruIo instance is destroyed after the DTOR, the 
variable Errr cannot get used in that case.)

It's much likely that you can ignore the linker warning.

Regards

-- 
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/4562aff2-01eb-4d8a-b52d-21e915494543%40googlegroups.com.

Re: [beagleboard] Dont see two partitions on SDcrad as shown in the lectures when a latest debian image is flashed on SD card

[Robert Nelson]

On Mon, May 4, 2020, 11:52 PM jennifer Dsilva 
wrote:

> I Just flashed a latest Debian image available at Beaglebone website on a
> Sdcard.
>
> When i connected the Sdcrad to PC i can see:
>
> 1. Only one partition
>
> 2. file system type: ext4
>
> 3. boot flag is set.
>
> 4. Partition named as rootfs.
>
> My questions are:
>
> ---Why there is only one partition on Sd card?
>
> ---I dont see MLO, Uboot, and dtbfiles at the root directory of the boot
> partition as shown in lecture?
>
> ---where are the above said files present? If present at different
> locations how RBL is knowing that?
>

This was changed around 4 years ago.. your lecture documents are a little
out of date.

MLO/uboot is in the MBR, right where RBL expects them.. ( look up raw mode
in the am335x manual )

Dtb/kernel under /boot/

Regards,

-- 
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/CAOCHtYi%2BAxPMRtR_LtKBoqVSb3CnjtR8NQorSNjOMQ2LzFNRzA%40mail.gmail.com.

[beagleboard] Dont see two partitions on SDcrad as shown in the lectures when a latest debian image is flashed on SD card

[jennifer Dsilva]

I Just flashed a latest Debian image available at Beaglebone website on a 
Sdcard.

When i connected the Sdcrad to PC i can see:

1. Only one partition

2. file system type: ext4

3. boot flag is set.

4. Partition named as rootfs.

My questions are:

---Why there is only one partition on Sd card?

---I dont see MLO, Uboot, and dtbfiles at the root directory of the boot 
partition as shown in lecture?

---where are the above said files present? If present at different 
locations how RBL is knowing that?


-- 
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/f5ea55f8-4fdd-4b81-926d-e77a0ec68e65%40googlegroups.com.

[beagleboard] Re: Can not connect via USB

[Rajesh Kulkarni]

Hi Ken,
I followed steps given by Drew Fustini. And was able to connect to the 
internet temporarily , but as soon as I rebooted I could not. You seem to 
have figured out the way to make BBB connect via Beaglebone. I am using 
Ubuntu as my host PC to connect to BBB. 

So if I understand correctly all I need to do is add the following lines in 
my network/interfaces file ?
iface usb0 inet static
address 192.168.137.2
netmask 255.255.0.0
network 192.168.137.0
gateway 192.168.137.1
dns-nameservers 8.8.8.8
post-up route add default gw 192.168.137.1

And this is what my netstat -rn looks like 
Destination Gateway Genmask Flags Metric RefUse 
Iface
default 192.168.7.1 0.0.0.0 UG 0  00 
usb0
192.168.6.0 0.0.0.0 255.255.255.0 U 0  00 usb1
192.168.7.0 0.0.0.0 255.255.255.0 U 0  00 usb0

1. I can successfully ping 192.168.7.1 . But whenever I ping 8.8.8.8 (once 
I reboot) , all I see in response is "*From 192.168.7.1 icmp_seq=1 
Destination Host unreachable*".
So my gateway is set correctly and ping to it, but for some reason it can 
not ping through it to 8.8.8.8.  Doesn't make sense.

2. How did you get the number 137 ? 

3. According to Drew Fustinis post (
https://gist.github.com/pdp7/d2711b5ff1fbb000240bd8337b859412 

 
)  entering the following command 
*"debian@beaglebone:~$ cat /etc/resolv.conf" *
 should get my the response *"**nameserver 8.8.8.8".*
 But the response I get is  "nameserver 127.0.0.1"  which is locat host , 
and I don't why I get this response. And I tried to edit that file manually 
but it gets overwritten after every reboot.

Any help is appreciated. Thank you for your time . :)

And you said the 137 is the 

On Monday, February 17, 2020 at 8:13:28 AM UTC-8, KenUnix wrote:
>
> Chris,
>
> If you don't have a router or Ethernet switch and only have access
> via your computers WiFi then what I did was make a change to
> one file on the BBB and one change to your P.C.'s network 
> connection for the BBB.
>
> sudo nano /etc/network/interfaces
>
> iface usb0 inet static
> address 192.168.137.2
> netmask 255.255.0.0
> network 192.168.137.0
> gateway 192.168.137.1
> dns-nameservers 8.8.8.8
> post-up route add default gw 192.168.137.1
>
> Change entry on P.C. Reboot BBB. Now access
> BBB using 192.168.137.2
> ssh to 192.168.137.2
> Firefox to 192.168.137.2
> Putty ssh to 192.168.137.2
>
> This change is persistent any only needs to be
> done once. Not complicated and works great.
>
> After changes are made you can now get the
> date / time automatically. Simply install ntpdate.
>
> sudo apt update
> sudo apt install ntpdate
>
> Then one time
>
> sudo cp -f /usr/share/zoneinfo/America/New_York /etc/localtime
> Another example
> sudo cp -f /usr/share/zoneinfo/Europe/Berlin /etc/localtime
>
> Then at boot time
>
> sudo /usr/sbin/ntpdate -b -s -u 0.north-america.pool.ntp.org
>
> The above can be put in a shell script. Check for correct
> timezone and date using
>
> date
>
> If wrong see zoneinfo directory to find YOUR time zone.
> If you are not in North America change
>
> 0.north-america.pool.ntp.org
>
> To see YOUR country. See
>
> https://www.pool.ntp.org/zone/@
>
> The above works, works great and is not over complicated.
> And only needs to be done once then your BBB will have
> the correct date / time and Internet access.
>
> I also added a small program that's been around for years
> in Linux / Unix called 'ed' a line editor. It's small and fast
> supports 'here' input and redirection. To get it
>
> sudo apt install ed
>
> See https://www.computerhope.com/unix/ued.htm
> And https://www.gnu.org/software/ed/manual/ed_manual.html
>
>
>>
>>
>>

-- 
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/36ba874e-2244-441b-a96c-794991781b08%40googlegroups.com.

[beagleboard] Re: BBAI Running TI SDK 6.03.00.106 DeviceTree File Creation

[jimvr]

John,

I love the "show-pins" script, but I cannot run that since there is a utf8 
mismatch with either perl or whatever is different/dependent on the TI SDK 
image.  The Arago image is just a different animal in so many ways

That post works great on the normal Cloud9 distro, but not on the TI SDK 
Matrix image.  There are so many changes to the Arago build over the 
original Cloud9 image that came in flash.

*But you did give me an idea* -- load up the default Cloud9 image, run that 
and use your referenced post to create my dts and compile the dtb to disk, 
copy that and then reboot with the TI SDK image, with uEnv pointing to the 
new dtb board.  *That might work!*

The documentation on the TI site is horrendous, it is out of date, just 
wrong in spots, etc.  For example:
Then, modify “uEnv.txt” on the boot partition (“/run/media/mmcblk0p1” 
directory on filesystem) to specify fdtfile with the desired dtb file name.
In the image that I have from the latest SDK, uEnv.txt is not on the boot 
partition, but the second partition /run/media/mmcblk1p1/boot/uEnv.txt.  On 
the raw TI image, that dtb line in uEnv.txt is actually commented out, so 
whatever the kernel does on boot, is how the pins are defined.

I spent countless hours researching, finding solutions, to find that they 
are outdated, wrong, don't work, or not defined well.  I don't know how you 
all develop in this world, but I am at this point where I have to define 
the pins correctly, and perhaps, this project is done!

Jim

On Monday, May 4, 2020 at 4:08:46 PM UTC-7, jimvr wrote:
>
> I have utilized the TI PinMux tool to create all of the necessary 
> functions that I need in my project.
>
> I just cannot seem to get past how to create the .dtb file from the output 
> of the PinMux tool.  I have a handful of files that are C defines and such, 
> but no clear path to the dts or dtb file.
>
> I have spend hours looking, and running scripts and pulling down git 
> repos, to find that "my build" which is just the downloaded SDK SDcard 
> image of the Matrix build from TI...
>
> All of the links to the Cloud9 distro are not working, 
> https://github.com/beagleboard/BeagleBoard-DeviceTrees.git for example is 
> not something that works at all.  The four files that I have here are ones 
> that are perhaps what I need to use, but I just don't know where to start.
>
> Thanks in advance.
>

-- 
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/fbe78af0-dada-4a1e-bb71-c5cc9573e1d5%40googlegroups.com.

Re: [beagleboard] Re: BBAI Running TI SDK 6.03.00.106 DeviceTree File Creation

[John Allwine]

I found this post helpful to get going with an overlay based on the one you 
mentioned: 
https://www.element14.com/community/community/project14/visionthing/blog/2019/11/16/beagleboard-ai-brick-recovery-procedure

-John

> On May 4, 2020, at 5:13 PM, jimvr  wrote:
> 
> 
> I do see this base file...
> a) is there a user manual for it?
> b) after I am done, how to "compile" to a .dtb using the TI SDK build?
> 
> Thanks!
> 
>> On Monday, May 4, 2020 at 4:08:46 PM UTC-7, jimvr wrote:
>> I have utilized the TI PinMux tool to create all of the necessary functions 
>> that I need in my project.
>> 
>> I just cannot seem to get past how to create the .dtb file from the output 
>> of the PinMux tool.  I have a handful of files that are C defines and such, 
>> but no clear path to the dts or dtb file.
>> 
>> I have spend hours looking, and running scripts and pulling down git repos, 
>> to find that "my build" which is just the downloaded SDK SDcard image of the 
>> Matrix build from TI...
>> 
>> All of the links to the Cloud9 distro are not working, 
>> https://github.com/beagleboard/BeagleBoard-DeviceTrees.git for example is 
>> not something that works at all.  The four files that I have here are ones 
>> that are perhaps what I need to use, but I just don't know where to start.
>> 
>> Thanks in advance.
> 
> -- 
> 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/925ac5f5-00c1-47f2-8b6b-c294b09b5043%40googlegroups.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/1C9868A5-F6E1-449A-832E-E31335872718%40pocketnc.com.

[beagleboard] Re: BBAI Running TI SDK 6.03.00.106 DeviceTree File Creation

[jimvr]

I do see this base file...
a) is there a user manual for it?
b) after I am done, how to "compile" to a .dtb using the TI SDK build?

Thanks!

On Monday, May 4, 2020 at 4:08:46 PM UTC-7, jimvr wrote:
>
> I have utilized the TI PinMux tool to create all of the necessary 
> functions that I need in my project.
>
> I just cannot seem to get past how to create the .dtb file from the output 
> of the PinMux tool.  I have a handful of files that are C defines and such, 
> but no clear path to the dts or dtb file.
>
> I have spend hours looking, and running scripts and pulling down git 
> repos, to find that "my build" which is just the downloaded SDK SDcard 
> image of the Matrix build from TI...
>
> All of the links to the Cloud9 distro are not working, 
> https://github.com/beagleboard/BeagleBoard-DeviceTrees.git for example is 
> not something that works at all.  The four files that I have here are ones 
> that are perhaps what I need to use, but I just don't know where to start.
>
> Thanks in advance.
>

-- 
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/925ac5f5-00c1-47f2-8b6b-c294b09b5043%40googlegroups.com.


am5729-beagleboneai.dts
Description: Binary data

[beagleboard] BBAI Running TI SDK 6.03.00.106 DeviceTree File Creation

[jimvr]

I have utilized the TI PinMux tool to create all of the necessary functions 
that I need in my project.

I just cannot seem to get past how to create the .dtb file from the output 
of the PinMux tool.  I have a handful of files that are C defines and such, 
but no clear path to the dts or dtb file.

I have spend hours looking, and running scripts and pulling down git repos, 
to find that "my build" which is just the downloaded SDK SDcard image of 
the Matrix build from TI...

All of the links to the Cloud9 distro are not 
working, https://github.com/beagleboard/BeagleBoard-DeviceTrees.git for 
example is not something that works at all.  The four files that I have 
here are ones that are perhaps what I need to use, but I just don't know 
where to start.

Thanks in advance.

-- 
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/50c00a61-fd7f-414d-b026-e66cd3096c5d%40googlegroups.com.
/* PinMux automatically generated generic format file dump. */


/* register_address(hex)a_delay(decimal)g_delay(decimal)
register_name(string)   ball_name(string) */

0x4844AA58  0   1900CFG_VIN2A_D10_OUT   D3
0x4844AA70  0   3400CFG_VIN2A_D12_OUT   D5
0x4844AA7C  0   3200CFG_VIN2A_D13_OUT   C2
0x4844AAAC  0   3000CFG_VIN2A_D17_OUT   D6
0x4844AAB8  0   2200CFG_VIN2A_D18_OUT   C5
0x4844AADC  0   1800CFG_VIN2A_D20_OUT   B3
0x4844AAE8  0   1900CFG_VIN2A_D21_OUT   B4
0x4844AA80  0   0   CFG_VIN2A_D14_INC3
0x4844ACF8  0   1600CFG_XREF_CLK0_OUT   D18
0x4844AD04  0   1500CFG_XREF_CLK1_OUT   E17
0x4844A3C8  0   800 CFG_MCASP1_AXR0_OUT G12
0x4844A41C  0   1400CFG_MCASP1_AXR1_OUT F12
0x4844A470  0   2000CFG_MCASP1_AXR8_OUT B12
0x4844A47C  0   800 CFG_MCASP1_AXR9_OUT A11
0x4844A3D4  0   2300CFG_MCASP1_AXR10_OUTB13
0x4844A3E0  0   600 CFG_MCASP1_AXR11_OUTA12
0x4844A3F8  0   1500CFG_MCASP1_AXR13_OUTA13
0x4844ABA8  0   0   CFG_VOUT1_D0_OUTF11
0x4844AC2C  0   0   CFG_VOUT1_D1_OUTG10
/* PinMux automatically generated generic format file dump. */


/* register_address(hex)register_value(hex) ball_name(string)   
register_name(string)   mux_mode0_name(string)  muxed_mode_name(string) */

0x4A003570  0x1000A D1  CTRL_CORE_PAD_VIN2A_D2  vin2a_d2
eCAP1_in_PWM1_out
0x4A003780  0x5000A AC4 CTRL_CORE_PAD_MMC3_CMD  mmc3_cmd
eCAP2_in_PWM2_out
0x4A0037A0  0x1000A AB5 CTRL_CORE_PAD_MMC3_DAT7 mmc3_dat7   
eCAP3_in_PWM3_out
0x4A003794  0x5000E AC8 CTRL_CORE_PAD_MMC3_DAT4 mmc3_dat4   gpio1_22
0x4A003798  0x5000E AD6 CTRL_CORE_PAD_MMC3_DAT5 mmc3_dat5   gpio1_23
0x4A00379C  0x5000E AB8 CTRL_CORE_PAD_MMC3_DAT6 mmc3_dat6   gpio1_24
0x4A00378C  0x5000E AC9 CTRL_CORE_PAD_MMC3_DAT2 mmc3_dat2   gpio7_1
0x4A003790  0x5000E AC3 CTRL_CORE_PAD_MMC3_DAT3 mmc3_dat3   gpio7_2
0x4A003510  0x5000E AH4 CTRL_CORE_PAD_VIN1A_D7  vin1a_d7gpio3_11
0x4A003624  0x5000E A7  CTRL_CORE_PAD_VOUT1_D18 vout1_d18   gpio8_18
0x4A00358C  0x5000E E6  CTRL_CORE_PAD_VIN2A_D9  vin2a_d9gpio4_10
0x4A0036F0  0xD000E F14 CTRL_CORE_PAD_MCASP1_AXR15  mcasp1_axr15
gpio6_6
0x4A00377C  0x5000E AD4 CTRL_CORE_PAD_MMC3_CLK  mmc3_clkgpio6_29
0x4A003784  0x5000E AC7 CTRL_CORE_PAD_MMC3_DAT0 mmc3_dat0   gpio6_31
0x4A003440  0x50007 R6  CTRL_CORE_PAD_GPMC_A0   gpmc_a0 i2c4_scl
0x4A003444  0x50007 T9  CTRL_CORE_PAD_GPMC_A1   gpmc_a1 i2c4_sda
0x4A0035EC  0x1000A E9  CTRL_CORE_PAD_VOUT1_D4  vout1_d4
pr1_ecap0_ecap_capin_apwm_o
/* PR1_PRU1_DIR_OUT_MANUAL */
0x4A003590  0x1010D D3  CTRL_CORE_PAD_VIN2A_D10 vin2a_d10   
pr1_pru1_gpo7
/* PR1_PRU1_DIR_OUT_MANUAL */
0x4A003598  0x1010D D5  CTRL_CORE_PAD_VIN2A_D12 vin2a_d12   
pr1_pru1_gpo9
/* PR1_PRU1_DIR_OUT_MANUAL */
0x4A00359C  0x1010D C2  CTRL_CORE_PAD_VIN2A_D13 vin2a_d13   
pr1_pru1_gpo10
/* PR1_PRU1_DIR_OUT_MANUAL */
0x4A0035AC  0x1010D D6  CTRL_CORE_PAD_VIN2A_D17 vin2a_d17   
pr1_pru1_gpo14
/* PR1_PRU1_DIR_OUT_MANUAL */
0x4A0035B0  0x1010D C5  CTRL_CORE_PAD_VIN2A_D18 vin2a_d18   
pr1_pru1_gpo15
/* PR1_PRU1_DIR_OUT_MANUAL */
0x4A0035B8  0x1010D B3  CTRL_CORE_PAD_VIN2A_D20 vin2a_d20   
pr1_pru1_gpo17
/* PR1_PRU1_DIR_OUT_MANUAL */
0x4A0035BC  0x1010D B4  CTRL_CORE_PAD_VIN2A_D21 vin2a_d21   

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[Hans Leeuw]

Hi TJF,

I have upgraded and I get this warning while compiling my program (using 
rb):

/usr/bin/ld: warning: libtinfo.so.5, needed by 
/usr/lib/gcc/arm-linux-gnueabihf/8/../../../libpruio.so, may conflict with 
libtinfo.so.6

(4.19.94-bone44), buster.

For the rest it seems to work fine.

Best, Hans.

-- 
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/480e15d1-a779-4441-851c-ac6eee59b52b%40googlegroups.com.

Re: [beagleboard] Static IP on BBB and AM3358 Debian 10.3 2020-04-06 4GB SD IoT Image

[NicolaF]

Thank you! 
Solved

-- 
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/8c3b13b3-3839-4558-b676-bc95ae9c9aa4%40googlegroups.com.

Re: [beagleboard] Re: BB AI task blocked

[John Allwine]

That did it. Thank you, Robert!

On Mon, May 4, 2020 at 7:55 AM Robert Nelson 
wrote:

> On Mon, May 4, 2020 at 8:50 AM John Allwine  wrote:
> >
> > That's the driver for Wifi chip? How can I disable that driver and
> anything trying to use it?
>
> blacklist it ..
>
> /etc/modprobe.d/brcmfmac-blacklist.conf
>
> blacklist brcmfmac
>
> 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/CAOCHtYjrXUp_BGr9sGD36EAJLmtUvgaJENaj7GPFWJdRodykxA%40mail.gmail.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/CAA9ERVrbg5vUUaFMonbVKLVjwkCG5xHkFAYPqaQ9PxSZ4yCSPA%40mail.gmail.com.

Re: [beagleboard] Re: BB AI task blocked

[Robert Nelson]

On Mon, May 4, 2020 at 8:50 AM John Allwine  wrote:
>
> That's the driver for Wifi chip? How can I disable that driver and anything 
> trying to use it?

blacklist it ..

/etc/modprobe.d/brcmfmac-blacklist.conf

blacklist brcmfmac

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/CAOCHtYjrXUp_BGr9sGD36EAJLmtUvgaJENaj7GPFWJdRodykxA%40mail.gmail.com.

Re: [beagleboard] Re: BB AI task blocked

[John Allwine]

That's the driver for Wifi chip? How can I disable that driver and anything
trying to use it?

On Mon, May 4, 2020 at 7:48 AM Robert Nelson 
wrote:

> On Mon, May 4, 2020 at 8:45 AM John Allwine  wrote:
> >
> > Does anyone know anything about this? I'm seeing similar behavior on
> kernel 4.14.108-ti-rt-r134. I can't even ssh in anymore because something
> is hung at startup (I used to be able to, but I'm not sure why). After
> booting with a known good microSD card and checking kern.log, I see this:
>
> It's our "lovely" non-mainline "brcmfmac" driver..  It' fub-bar'd for RT..
>
> v4.14.x uses this 150+ patchset:
> https://community.cypress.com/docs/DOC-19000
>
> 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/CAPEK9qbyFsy4TDYPme%2Bs4KOvxwTUFrk48NQtmcGUmRpjbDs9uw%40mail.gmail.com.

Re: [beagleboard] Re: BB AI task blocked

[Robert Nelson]

On Mon, May 4, 2020 at 8:45 AM John Allwine  wrote:
>
> Does anyone know anything about this? I'm seeing similar behavior on kernel 
> 4.14.108-ti-rt-r134. I can't even ssh in anymore because something is hung at 
> startup (I used to be able to, but I'm not sure why). After booting with a 
> known good microSD card and checking kern.log, I see this:

It's our "lovely" non-mainline "brcmfmac" driver..  It' fub-bar'd for RT..

v4.14.x uses this 150+ patchset: https://community.cypress.com/docs/DOC-19000

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/CAOCHtYgFqTQxzkVMdVnFpc%3Dinoh-%3Dw%2B%2ByjJ8AEHQTr-%3D6zer0Q%40mail.gmail.com.

[beagleboard] Re: BB AI task blocked

[John Allwine]

Does anyone know anything about this? I'm seeing similar behavior on kernel 
4.14.108-ti-rt-r134. I can't even ssh in anymore because something is hung 
at startup (I used to be able to, but I'm not sure why). After booting with 
a known good microSD card and checking kern.log, I see this:

[  242.872658] INFO: task systemd-udevd:351 blocked for more than 120 
seconds.
[  242.879698]   Tainted: GW  O4.14.108-ti-rt-r134 #1stretch
[  242.886558] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[  242.894551] systemd-udevd   D0   351332 0x0101
[  242.894623] [] (__schedule) from [] 
(schedule+0x64/0x108)
[  242.894661] [] (schedule) from [] 
(__mmc_claim_host+0xb4/0x1d0)
[  242.894700] [] (__mmc_claim_host) from [] 
(sdio_claim_host+0x2c/0x44)
[  242.894737] [] (sdio_claim_host) from [] 
(sdio_bus_probe+0x80/0x12c)
[  242.894783] [] (sdio_bus_probe) from [] 
(driver_probe_device+0x2d4/0x480)
[  242.894826] [] (driver_probe_device) from [] 
(__driver_attach+0x10c/0x128)
[  242.894867] [] (__driver_attach) from [] 
(bus_for_each_dev+0x8c/0xd0)
[  242.894907] [] (bus_for_each_dev) from [] 
(driver_attach+0x2c/0x30)
[  242.894945] [] (driver_attach) from [] 
(bus_add_driver+0x1b8/0x278)
[  242.894986] [] (bus_add_driver) from [] 
(driver_register+0x88/0x104)
[  242.895024] [] (driver_register) from [] 
(sdio_register_driver+0x34/0x38)
[  242.895082] [] (sdio_register_driver) from [] 
(btsdio_init+0x2c/0x1000 [btsdio])
[  242.895152] [] (btsdio_init [btsdio]) from [] 
(do_one_initcall+0x64/0x19c)
[  242.895196] [] (do_one_initcall) from [] 
(do_init_module+0x74/0x210)
[  242.895238] [] (do_init_module) from [] 
(load_module+0x22a0/0x29f8)
[  242.895324] [] (load_module) from [] 
(SyS_init_module+0x1a4/0x1e0)
[  242.895369] [] (SyS_init_module) from [] 
(__sys_trace_return+0x0/0x10)
[  242.895424] INFO: task connmand:526 blocked for more than 120 seconds.
[  242.902076]   Tainted: GW  O4.14.108-ti-rt-r134 #1stretch
[  242.908948] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[  242.916849] connmandD0   526  1 0x
[  242.916920] [] (__schedule) from [] 
(schedule+0x64/0x108)
[  242.916958] [] (schedule) from [] 
(__mmc_claim_host+0xb4/0x1d0)
[  242.916995] [] (__mmc_claim_host) from [] 
(sdio_claim_host+0x2c/0x44)
[  242.917206] [] (sdio_claim_host) from [] 
(brcmf_sdio_bus_txctl+0x134/0x1a0 [brcmfmac])
[  242.917551] [] (brcmf_sdio_bus_txctl [brcmfmac]) from 
[] (brcmf_proto_bcdc_msg+0xb4/0xb8 [brcmfmac])
[  242.917895] [] (brcmf_proto_bcdc_msg [brcmfmac]) from 
[] (brcmf_proto_bcdc_set_dcmd+0x38/0x100 [brcmfmac])
[  242.918234] [] (brcmf_proto_bcdc_set_dcmd [brcmfmac]) from 
[] (brcmf_fil_cmd_data+0x88/0xb4 [brcmfmac])
[  242.918572] [] (brcmf_fil_cmd_data [brcmfmac]) from 
[] (brcmf_fil_iovar_data_set+0x94/0xb8 [brcmfmac])
[  242.918909] [] (brcmf_fil_iovar_data_set [brcmfmac]) from 
[] (brcmf_fil_iovar_int_set+0x3c/0x58 [brcmfmac])
[  242.919241] [] (brcmf_fil_iovar_int_set [brcmfmac]) from 
[] (brcmf_configure_arp_nd_offload+0x50/0x70 [brcmfmac])
[  242.919754] [] (brcmf_configure_arp_nd_offload [brcmfmac]) 
from [] (brcmf_cfg80211_up+0x2ec/0x3a4 [brcmfmac])
[  242.920108] [] (brcmf_cfg80211_up [brcmfmac]) from 
[] (brcmf_netdev_open+0xac/0x128 [brcmfmac])
[  242.920319] [] (brcmf_netdev_open [brcmfmac]) from 
[] (__dev_open+0xe4/0x15c)
[  242.920368] [] (__dev_open) from [] 
(__dev_change_flags+0x1a4/0x1d0)
[  242.920412] [] (__dev_change_flags) from [] 
(dev_change_flags+0x28/0x58)
[  242.920451] [] (dev_change_flags) from [] 
(devinet_ioctl+0x704/0x7cc)
[  242.920489] [] (devinet_ioctl) from [] 
(inet_ioctl+0x1a4/0x1d0)
[  242.920532] [] (inet_ioctl) from [] 
(sock_ioctl+0x15c/0x300)
[  242.920571] [] (sock_ioctl) from [] 
(do_vfs_ioctl+0xc0/0x94c)
[  242.920604] [] (do_vfs_ioctl) from [] 
(SyS_ioctl+0x7c/0x8c)
[  242.920651] [] (SyS_ioctl) from [] 
(ret_fast_syscall+0x0/0x5c)

On Tuesday, October 29, 2019 at 2:28:07 PM UTC-6, Andrew Elder wrote:
>
>
> Similar observed with
>
> debian@ai:~$ uname -a
> Linux ai 4.19.73-ti-rt-r29 #1stretch SMP PREEMPT RT Wed Oct 9 21:13:08 UTC 
> 2019 armv7l GNU/Linux
>
> [  484.306447] INFO: task kworker/u4:0:7 blocked for more than 120 seconds.
> [  484.313237]   Tainted: GW  O  4.19.73-ti-rt-r29 
> #1stretch
> [  484.320145] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
> this message.
> [  484.329172] INFO: task kworker/1:1:66 blocked for more than 120 seconds.
> [  484.336062]   Tainted: GW  O  4.19.73-ti-rt-r29 
> #1stretch
> [  484.342924] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
> this message.
> [  484.355157] INFO: task kworker/u5:0:68 blocked for more than 120 
> seconds.
> [  484.362016]   Tainted: GW  O  4.19.73-ti-rt-r29 
> #1stretch
> [  484.368869] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
> this message.   
>
>
>
> On Friday, October 25, 

Re: [beagleboard] Static IP on BBB and AM3358 Debian 10.3 2020-04-06 4GB SD IoT Image

[Robert Nelson]

On Mon, May 4, 2020 at 8:17 AM  wrote:
>
> Hi all,
> I upgraded my BBB with the image in the object. Trying to set up the 
> /etc/network/interfaces file as following:
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> #allow-hotplug eth0
> iface eth0 inet static
>  address 192.168.1.25
>  netmask 255.255.255.0
>  gateway 192.168.1.1
>
> the BBB does not set the static ip as expected. Using the previous image 
> release (AM3358 Debian 9.12 2020-04-06 4GB SD ImgTec) the IP setting worked 
> fine.
> Please, any advice?
> Thank's in advance.

Run connmanctl services:

debian@bbb-pwr01-ser09:~$ sudo connmanctl services
*AO Wiredethernet_c8a030abf366_cable

"copy" your version of: ethernet_c8a030abf366_cable

Then run:

sudo connmanctl config  --ipv4 manual  
 --nameservers 

sudo connmanctl config ethernet_c8a030abf366_cable --ipv4 manual
192.168.1.25 255.255.255.0 192.168.1.1 --nameservers 8.8.8.8

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/CAOCHtYhSSYXudK-oUyouF%3DJnucgcbqeCdWU%2B6CkF_5Jmnqh4RQ%40mail.gmail.com.

Re: [beagleboard] Static IP on BBB and AM3358 Debian 10.3 2020-04-06 4GB SD IoT Image

[evilwulfie]

connman does all of that
Please search list for the 1000s of emails regarding this issue

On 5/4/2020 12:48 AM, nicola.fur...@gmail.com wrote:

Hi all,
I upgraded my BBB with the image in the object. Trying to set up the 
/etc/network/interfaces file as following:


# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug eth0
iface eth0 inet static
 address 192.168.1.25
 netmask 255.255.255.0
 gateway 192.168.1.1

the BBB does not set the static ip as expected. Using the previous 
image release (_AM3358 _Debian__9.12__2020-04-06__4GB SD__ImgTec 
) 
the IP setting worked fine.

Please, any advice?
Thank's in advance.
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/e3368bd3-6607-4518-9b28-031b62cc6d6a%40googlegroups.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/560335c1-5193-78a8-2ced-df1acacee68a%40gmail.com.

[beagleboard] Static IP on BBB and AM3358 Debian 10.3 2020-04-06 4GB SD IoT Image

[nicola . furlan]

Hi all,
I upgraded my BBB with the image in the object. Trying to set up the 
/etc/network/interfaces file as following:

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug eth0
iface eth0 inet static
 address 192.168.1.25
 netmask 255.255.255.0
 gateway 192.168.1.1

the BBB does not set the static ip as expected. Using the previous image 
release (*AM3358 *Debian 9.12 2020-04-06 4GB SD ImgTec 
)
 
the IP setting worked fine.
Please, any advice?
Thank's in advance.
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/e3368bd3-6607-4518-9b28-031b62cc6d6a%40googlegroups.com.

Re: [beagleboard] BBB with Debian is blocked after switching from USB power supply to battery supply.

[bernid111]

I did more tests and I withdraw from what I wrote: the problem concerns RT 
and non-RT kernels (not only RT as I wrote). 
To cope the problem i tested simple phyton script which poweroff the BBB 
after transition from USB to battery power supply. 
It works when I remove mt7601u driver sudo rmmod mt7601u   (on USB power) 
before  
running the script:
#!/usr/bin/python
## Read some values from the PMIC and print out what we find
### example i2cget -y -f  0 0x24 0x3

import time
from os import system
import subprocess

I2C_DEVICE = 0

CHIP_ADDRESS = 0x24

# register addresses we are interested in
PPATH = 0x1
CHGCONFIG0 = 0x3


STATUS = 0xA
PGOOD = 0xC

# some bitmasks

STATUS_AC = 1<<3
STATUS_USB = 1<<2

CHGCONFIG0_ACTIVE = 1<<3 # we are charging the battery

# these labels are interpreted from the TPS65217 datasheet
CHG0_LABELS = ["Temp sense error","Pre-charge Timedout","Charge 
Timedout","Active (charging)","Charge Termination Current","Thermal 
Suspend", "DPPM Reduction","Thermal Regulation"]
STATUS_LABELS=["Push Button",None,"USB Power", "AC Power"]# skip the rest
PGOOD_LABELS=["LDO2 power-good","LDO1 power-good","DCDC3 power-good","DCDC2 
power-good","DCDC1 power-good", "LDO4 power-good","LDO3 power-good"]


# get the I2C register, strip off \n and cast to int from hex
# -y means non-interactive mode (just do it!)
# -f forces the connection
def query(reg=0):
return  int(subprocess.check_output(["i2cget","-y" ,"-f", 
str(I2C_DEVICE), str(CHIP_ADDRESS), str(reg)]).strip(),16)

# display value of each bit in the register, along with its label
def describe_bits(val,labels):
for x in range(0,len(labels)):
if(not labels[x]): # skip None labels
continue
msk = 1
 
script. However when  I add line system("rmmod mt7601u") before 
system("shutdown 
-h now") the BBB doesn't want to shut down and produces known messages:
[  337.637916] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (88, 
https://stackoverflow.com/questions/24039420/turn-usb-power-off-on-with-beaglebone-black-kernel-3-8>
but receive well known: mt7601u 1-1:1.0: Vendor request req:02 off:xxx 
failed:-110
I tried also different USB wifi stick Realtek RTL8188EU but with the same 
result. 
Is it really impossible to turn off the usb wifi driver after switching 
from usb to battery power supply?
Regards, 
Bern

-- 
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/e82f1e81-67e6-45f0-a50d-72fb4c26bf40%40googlegroups.com.