Yes. Thanks Neeraj.
Regards,
Pratik Manvar
Thank You, Neeraj.
Regards,
Pratik Manvar
Hello @Niraj,
Yes, we want to upgrade to the kernel-v5.10.
For that, I have posted the query in the other OSD32MP1-BRK latest patches – Octavo Systems thread. Seems like it is still not published and pending for approval.
Can you please confirm that the Octavo patches for kernel-5.10 available at GitHub – octavosystems/meta-octavo-osd32mp1: Yocto layer for OSD32MP1 Family of devices from Octavo Systems can be used to migrate to updated kernel-v5.10 provided by STM?
Thanks & Regards,
Pratik Manvar
Hi @Eshtaartha Basu,
As per your suggestion we were checking this link (https://github.com/octavosystems/BRK_Developer_Package_patches)Â for updates.
But, we did not see any updates on this repo. However, we found a new repo with meta layer at GitHub – octavosystems/meta-octavo-osd32mp1: Yocto layer for OSD32MP1 Family of devices from Octavo Systems.
Can we use the patches of kernel to migrate to the kernel v5.10.10?
Thanks & Regards,
Pratik Manvar
Hello
I could not upload the script files (com1.sh and com2.sh).
==> com1.sh
1 2 3 4 5 6 7 | #!/bin/bash while true do echo -n -e ‘\x00\x01\x02\x03\x04\x05\x06\x07\x10\x07\x23\x60\x61\x86\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xC4\x3A\x35\x7C\x56\x78’ > /dev/ttySTM1 echo -n "1" done |
==> com2.sh
1 2 3 4 5 6 7 | #!/bin/bash while true do echo -n -e ‘\x00\x01\x02\x03\x04\x05\x06\x07\x10\x07\x23\x60\x61\x86\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xC4\x3A\x35\x7C\x56\x78’ > /dev/ttySTM2 echo -n "2" done |
Thanks & Regards,
Pratik Manvar
Hello @Aedan and @Niraj,
Thank you for your support.
Yes, we have a custom board with Octavo BRK SIP module (STM32MP157C) with kernel v5.4.31.
As per your suggestion, I tried on OSD32MP1-BRK board with couple of kernel releases (v5.4.31 and v5.10.10) and able to reproduce the same issue on kernel v5.4.31!
It works fine with kernel v5.10.10 release.
I have added more data in echo command with a print of each transmission (PFA the updated scripts com-1.txt & com-2.txt).
1 2 3 4 5 6 | #!/bin/bash while true do echo -n -e ‘\x00\x01\x02\x03\x04\x05\x06\x07\x10\x07\x23\x60\x61\x86\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xC4\x3A\x35\x7C\x56\x78’ > /dev/ttySTM1 echo -n "1" done |
Please see the attached test logs (kernel-v5.4.31-serial-test-logs.txt & kernel-v5.10.10-serial-test-logs.txt).
Thanks & Regards,
Pratik Manvar
Hi Neeraj,
Sorry for the late response on this thread.
We were able solve this issue. As you said in point #3, one GPIO pin (eMMC clock pin) has been utilized by something else for custom things. Once, we changed that pin as per new designed schematics, the eMMC get initialized without any issue in bootloader.
Thanks for your help.
Regards,
Pratik Manvar
Octavo Systems LLC all rights reserved
OCTAVO is registered in the U.S. Patent and Trademark Office. OSD, C-SiP, and the Octavo Logo are trademarks of Octavo Systems LLC.
"*" indicates required fields
"*" indicates required fields
"*" indicates required fields
"*" indicates required fields