Re: [beagleboard] How to automatically set system time of BBB by external DS3231

[Niresh]

Hi,
Sorry, i did mistake in copy paste, actually it is echo ds3231 0x68 >
/sys/class/i2c-adapter/i2c-2/new_device

I've tested BB-I2C2-RTC-DS3231.dtbo in the new image 4.19.94-ti-r42, they
mount rtc1 in /dev but system time is not updated with rtc1.  Attached
dmesg with and without DS3231 overlay in uEnv.txt .

Following message with  DS3231 overlay enabled.

root@beaglebone:/dev# hwclock -r -f /dev/rtc1

2000-01-01 00:49:21.771707+00:00


root@beaglebone:/dev# timedatectl

   Local time: Tue 2020-09-01 04:34:29 UTC

   Universal time: Tue 2020-09-01 04:34:29 UTC

 RTC time: Tue 2020-09-01 04:34:29

Time zone: Etc/UTC (UTC, +)

System clock synchronized: no

  NTP service: active

  RTC in local TZ: no


debian@beaglebone:/dev$ dmesg | grep rtc

[1.280996] rtc-ds1307 2-0068: registered as rtc0

[1.283636] omap_rtc 44e3e000.rtc: already running

[1.284312] omap_rtc 44e3e000.rtc: registered as rtc1

[1.574739] [drm] Cannot find any crtc or sizes

[1.604280] rtc-ds1307 2-0068: setting system clock to 2020-09-01
04:30:36 UTC (1598934636)

[2.600387] [drm] Cannot find any crtc or sizes

[   56.285738] PM: bootloader does not support rtc-only!


debian@beaglebone:/dev$ dmesg | grep i2c

[0.315725] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 100 kHz

[0.317402] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz

[1.286054] i2c /dev entries driver

[1.590657] input: tps65217_pwr_but as
/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0

[1.592768] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz



Thanks,
NK



On Mon, Aug 31, 2020 at 4:53 PM Tarmo  wrote:

> Hi Niresh,
>
> On Monday, 31 August 2020 14:14:05 UTC+3, Niresh wrote:
>>
>> Hi,
>>
>> debian@beaglebone:/dev$ i2cdetect -r -y 2
>>
>>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>>
>> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
>>
>> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>
>> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>
>> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>
>> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>
>> 50: -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- --
>>
>> 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- --
>>
>> 70: -- -- -- -- -- -- -- --
>>
>
> Looks like your RTC is connected to I2C bus number 2 (counting starts from
> 0).
>
> I'm a bit confused. How could the command in your initial post pass and
> create a working RTC device? You were addressing the wrong bus (number 1)
> here:
>
> echo ds3231 0x68 > /sys/class/i2c-adapter/i2c-1/new_device
>
> Anyway, if you're really connecting the RTC to bus 2 then 
> "BB-I2C*2*-RTC-DS3231.dtbo"
> should be your device tree.
>
> --
> Kind regards,
> Tarmo
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/m4hZYsA-d8M/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/ed5f7cb9-873a-44d0-8715-c5c624f046d4o%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/CAF7-PaRB9EXQRAp_%3Dsognd5gsAFA_KhwhUfyJQuxduMfEL9Eiw%40mail.gmail.com.
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.19.94-ti-r42 (voodoo@x3-am57xx-beagle-x15-2gb) 
(gcc version 8.3.0 (Debian 8.3.0-6)) #1buster SMP PREEMPT Tue Mar 31 19:38:29 
UTC 2020
[0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] OF: fdt: Machine model: TI AM335x BeagleBone Black
[0.00] Memory policy: Data cache writeback
[0.00] cma: Reserved 48 MiB at 0x9c80
[0.00] On node 0 totalpages: 130560
[0.00]   Normal zone: 1148 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 130560 pages, LIFO batch:31
[0.00] CPU: All CPU(s) started in SVC mode.
[0.00] AM335X ES2.1 (sgx neon)
[0.00] random: get_random_bytes called from start_kernel+0xac/0x4b4 
with crng_init=0
[0.00] percpu: Embedded 17 pages/cpu s38988 r8192 d22452 u69632
[0.00] pcpu-all

[beagleboard] Difference

[jennifer Dsilva]

Hi Sir.

What are the Difference between am335x_boneblack_defconfig vs 
am335x_boneblack_vboot_defconfig  ?

Regards,
Jennifer

-- 
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/aca2ad66-32b2-4baf-ac22-39d087d2441dn%40googlegroups.com.

Re: [beagleboard] Missing Partition table error for image built using the Image Builder

[Robert Nelson]

On Mon, Aug 31, 2020 at 8:23 PM ramprakash baskar
 wrote:
>
>
> Hello,
> I have built a image using the Image builder git repo. Image got built under 
> the repo but when I try to copy the image to a SD card I'm getting a 
> warning"Missing Partition Table" in the balena etcher program. I tried to 
> ignore the warning and proceed but the image is not bootable in beaglebone. 
> Can someone guide me how to fix this issue and proceed further?

By default, the image-builder dumps out a generic RootFS tar file.

To generate that into an image Etcher could use, you need to convert
it into a device specific image:

First extract the file from deploy, it should have a "setup_sdcard.sh"
script in the base directory

Then for a BeagleBone run:

sudo ./setup_sdcard.sh --img-4gb some-file-name --dtb beaglebone

Then you'll have a 4gb image file with the name "some-file-name" that
Balena etcher can write to a microSD card.

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/CAOCHtYhXDz_fPOQw0id%3DK-gnsuTw7NLYGkgTRk%3D0Q9zbXgHW6g%40mail.gmail.com.

[beagleboard] Troubles when adding a LED to Device Tree

[phfbertoleti]

Hi. First of all, thanks in advance for those who try to help me.

I'm studying about Device Trees, and I've chosen to use Beaglebone Green 
Wireless as a board to practice.
I've done the following steps:

1) From u-boot serial, I've seen that Beaglebone green Wireless is using 
uses am335x-bonegreen-wireless-uboot-univ.dtb as DTB file
2) Cloned / downloaded beaglebone Kernel (from 
https://github.com/beagleboard/linux)
3) I want to add LED at GPIO 47 ( = GPIO1_16, and accordingly to board 
schematic, AM33xx GPMC_A0 pin). I've edited am335x-bone-common.dtsi file, 
adding led (led6) in leds node as follows:

leds {
 pinctrl-names = "default";
 pinctrl-0 = <&user_leds_s0>;
   compatible = "gpio-leds";
  led2 {
 label = "beaglebone:green:usr0";
   gpios = <&gpio1 21 GPIO_ACTIVE_HIGH>;
  linux,default-trigger = "heartbeat";
   default-state = "off";
 };
 led3 {
 label = "beaglebone:green:usr1";
   gpios = <&gpio1 22 GPIO_ACTIVE_HIGH>;
  linux,default-trigger = "mmc0";
default-state = "off";
 };
 led4 {
 label = "beaglebone:green:usr2";
   gpios = <&gpio1 23 GPIO_ACTIVE_HIGH>;
  linux,default-trigger = "cpu0";
default-state = "off";
 };
 led5 {
 label = "beaglebone:green:usr3";
   gpios = <&gpio1 24 GPIO_ACTIVE_HIGH>;
  linux,default-trigger = "mmc1";
default-state = "off";
 };

led6 {
label = "beaglebone:green:extLed";
gpios = <&gpio1 16 GPIO_ACTIVE_HIGH>;
linux,default-trigger = "heartbeat";
default-state = "off";
};
};


And I've added gpio2_16 in pinmux of user leds, as follows:

&am33xx_pinmux {
   user_leds_s0: user_leds_s0 {
   pinctrl-single,pins = <
AM33XX_PADCONF(AM335X_PIN_GPMC_A5, PIN_OUTPUT_PULLDOWN, 
MUX_MODE7)  /* gpmc_a5.gpio1_21 */
 AM33XX_PADCONF(AM335X_PIN_GPMC_A6, PIN_OUTPUT_PULLUP, 
MUX_MODE7)/* gpmc_a6.gpio1_22 */
 AM33XX_PADCONF(AM335X_PIN_GPMC_A7, PIN_OUTPUT_PULLDOWN, 
MUX_MODE7)  /* gpmc_a7.gpio1_23 */
 AM33XX_PADCONF(AM335X_PIN_GPMC_A8, PIN_OUTPUT_PULLUP, 
MUX_MODE7)/* gpmc_a8.gpio1_24 */
  AM33XX_PADCONF(AM335X_PIN_GPMC_A0, PIN_OUTPUT_PULLUP, 
MUX_MODE7)/* gpmc_a0.gpio1_16 */
  >;
 };



4) I've successfully compiled all dtbs by doing:

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- dtbs



5) After that, I've updated the recently compiled 
am335x-bonegreen-wireless-uboot-univ.dtb 
file to /boot/dtbs/{uname-r} folder in Beaglebone Green

6) And, finally, I rebooted the board. However, board has entered in a 
"strange state", with all user leds powered on. Using U-Boot serial, I've 
noticed that boot process have stopped at "starting kernel" message


In this case, what have I done wrong? Are my modifications in DTS file 
right? 




Again, 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/aa213315-e647-4488-b0d1-ec97666c5231o%40googlegroups.com.

[beagleboard] Missing Partition table error for image built using the Image Builder

[ramprakash baskar]

Hello,
I have built a image using the Image builder git repo. Image got built 
under the repo but when I try to copy the image to a SD card I'm getting a 
warning"Missing Partition Table" in the balena etcher program. I tried to 
ignore the warning and proceed but the image is not bootable in beaglebone. 
Can someone guide me how to fix this issue and proceed further?

-- 
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/25bc30bf-f630-42ee-8724-cb0240c9df0en%40googlegroups.com.

[beagleboard] AWS Sagemaker Model on BeagleBone AI

[ing . lforeroc]

Hello,

My team is working on an object recognition solution, using the BeagleBone 
AI.

We are currently trying to deploy an AWS Sagemaker object recognition model 
in BeagleBone AI, using some of the reduction tools for embedded systems 
that they offer. When we tested the model on the BeagleBone AI, we had poor 
performance (similar to the performance we get on the BeagleBone Black).

If any of you know how to implement an AWS Sagemaker model on BeagleBone 
AI, ensuring maximum performance, please help us, we are in a hurry.

Thanks a lot.

Best 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/b4528b3c-d5f9-4750-9abb-4691bfa9bcc3o%40googlegroups.com.

Re: [beagleboard] How to automatically set system time of BBB by external DS3231

[Tarmo]

Hi Niresh,

On Monday, 31 August 2020 14:14:05 UTC+3, Niresh wrote:
>
> Hi,
>
> debian@beaglebone:/dev$ i2cdetect -r -y 2
>
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>
> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> 50: -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- --
>
> 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- --
>
> 70: -- -- -- -- -- -- -- --
>

Looks like your RTC is connected to I2C bus number 2 (counting starts from 
0). 

I'm a bit confused. How could the command in your initial post pass and 
create a working RTC device? You were addressing the wrong bus (number 1) 
here:

echo ds3231 0x68 > /sys/class/i2c-adapter/i2c-1/new_device

Anyway, if you're really connecting the RTC to bus 2 then 
"BB-I2C*2*-RTC-DS3231.dtbo" 
should be your device tree.

--
Kind regards,
Tarmo

-- 
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/ed5f7cb9-873a-44d0-8715-c5c624f046d4o%40googlegroups.com.

Re: [beagleboard] How to automatically set system time of BBB by external DS3231

[Niresh]

Hi,

debian@beaglebone:/dev$ i2cdetect -r -y 2

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

00:  -- -- -- -- -- -- -- -- -- -- -- -- --

10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

50: -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- --

60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- --

70: -- -- -- -- -- -- -- --

debian@beaglebone:/dev$ i2cdetect -r -y 1

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

00:  -- -- -- -- -- -- -- -- -- -- -- -- --

10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

70: -- -- -- -- -- -- -- --

debian@beaglebone:/dev$ i2cdetect -r -y 0

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

00:  -- -- -- -- -- -- -- -- -- -- -- -- --

10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --

30: -- -- -- -- 34 -- -- -- -- -- -- -- -- -- -- --

40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

70: UU -- -- -- -- -- -- --

debian@beaglebone:/dev$


Regards,

NK

On Mon, Aug 31, 2020 at 1:46 PM Tarmo  wrote:

> Hi Niresh,
>
> On Monday, 31 August 2020 06:45:48 UTC+3, Niresh wrote:
>>
>> Attached output from "sudo /opt/scripts/tools/version.sh" and the content
>> of your "/boot/uEnv.txt" file along with boot log message.
>>
>
> They look good. I suspect you're mostly there :)
>
> debian@beaglebone:/boot$ dmesg | grep rtc
>>
>> [2.283660] rtc-ds1307: probe of 1-0068 failed with error -16
>>
>
> This indicates that the device tree was loaded correctly, but the kernel
> can't talk to your RTC chip. If you can figure out why, you've enabled
> systemd-timesyncd.
>
> Hmm, can you double-check that the I2C bus number is correct and the RTC
> chip is online?
>
> There is a utility called i2cdetect which should reveal your RTC on bus 1,
> address 68.
> https://linux.die.net/man/8/i2cdetect
>
>
>> Please help me with bash scripts for external RTC and its procedure.
>>
>
> Undo your changes to uEnv.txt and follow this guide instead. It's not
> ideal, but probably covers the relevant requirements.
>
> https://learn.adafruit.com/adding-a-real-time-clock-to-beaglebone-black/set-rtc-time
>
> --
> Kind regards,
> Tarmo
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/m4hZYsA-d8M/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/500b2fb8-177f-4a6e-885a-1d0c612f2e24o%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/CAF7-PaTebyVdN23TdC8g1Se%2BUtkn3DRJQS6n6OiOgMDAEbEk%2Bg%40mail.gmail.com.

Re: [beagleboard] How to automatically set system time of BBB by external DS3231

[Tarmo]

Hi Niresh,

On Monday, 31 August 2020 06:45:48 UTC+3, Niresh wrote:
>
> Attached output from "sudo /opt/scripts/tools/version.sh" and the content 
> of your "/boot/uEnv.txt" file along with boot log message.
>

They look good. I suspect you're mostly there :)

debian@beaglebone:/boot$ dmesg | grep rtc
>
> [2.283660] rtc-ds1307: probe of 1-0068 failed with error -16
>

This indicates that the device tree was loaded correctly, but the kernel 
can't talk to your RTC chip. If you can figure out why, you've enabled 
systemd-timesyncd.

Hmm, can you double-check that the I2C bus number is correct and the RTC 
chip is online?

There is a utility called i2cdetect which should reveal your RTC on bus 1, 
address 68. 
https://linux.die.net/man/8/i2cdetect
 

> Please help me with bash scripts for external RTC and its procedure.
>

Undo your changes to uEnv.txt and follow this guide instead. It's not 
ideal, but probably covers the relevant requirements.
https://learn.adafruit.com/adding-a-real-time-clock-to-beaglebone-black/set-rtc-time

--
Kind regards,
Tarmo

-- 
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/500b2fb8-177f-4a6e-885a-1d0c612f2e24o%40googlegroups.com.