MitySOM-AM57X: Software Developmenthttp://support.criticallink.com/redmine/http://support.criticallink.com/redmine/redmine/favicon.ico?16338348402023-11-27T14:28:33ZCritical Link Support
Redmine Software Development: RE: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/6553?r=6563#message-65632023-11-27T14:28:33ZJonathan Cormierjcormier@criticallink.com
<p>Hint: as long as your changes are only in the device tree file, if you only copy the changed dtb and leave out the zImage, then the kernel version string won't change and you won't have to copy all the kernel modules and copy the extra folder.</p> Software Development: RE: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/6553?r=6562#message-65622023-11-27T14:24:52ZJonathan Cormierjcormier@criticallink.com
<p>Sandeep Sivadas wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6553?r=6561#message-6561">RE: spidev loopback testing not working</a>:</p>
<blockquote>
<p>Hi,<br />I tried the kernel and u-boot building as suggested and included the "extra" folder. Now SPI communication, Ethernet,USB etc are working fine. Only one difficulty faced in the Kernel building and copying to /lib/module portion. There I have to create a kernel folder and copied the contents from my PC to SD card. Otherwise, kernel modules are pasted inside the module folder.</p>
<p>cd ../rootfs/lib/modules/4.19<rest_of_name><br />rsync -r kernel modules* root@${TARGIP}:/lib/modules</p>
<p>Please take a look at this command.</p>
</blockquote>
<p>You are right that's a little more work than needed. I updated the wiki to simplify the copy commands. The following command should be sufficient to create and copy the files a bit easier.</p>
<pre>
TARGET=root@10.0.103.50
cd ../rootfs/
rsync -avr lib ${TARGET}:/
</pre> Software Development: RE: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/6553?r=6561#message-65612023-11-23T13:39:55ZSandeep Sivadas
<p>Hi,<br />I tried the kernel and u-boot building as suggested and included the "extra" folder. Now SPI communication, Ethernet,USB etc are working fine. Only one difficulty faced in the Kernel building and copying to /lib/module portion. There I have to create a kernel folder and copied the contents from my PC to SD card. Otherwise kernel modules are pasted inside the module folder.</p>
<p>cd ../rootfs/lib/modules/4.19<rest_of_name><br />rsync -r kernel modules* root@${TARGIP}:/lib/modules</p>
<p>Please take a look at this command.</p>
<p>Thank you for your support<br />Sandeep S</p> Software Development: RE: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/6553?r=6560#message-65602023-11-22T18:25:00ZJonathan Cormierjcormier@criticallink.com
<p>This doesn't explain why USB isn't coming up though. Your log doesn't show any USB log statements, the most likely reason would be if the USB kernel modules aren't loaded either.</p>
<p>The following modules should have been auto-loaded for USB to function.<br /><pre>
root@mitysom-am57x:~# lsmod | grep -E usb\|dwc
dwc3 73728 0
udc_core 28672 1 dwc3
extcon_usb_gpio 16384 0
phy_omap_usb2 16384 3
dwc3_omap 16384 0
usbserial 36864 1 ftdi_sio
usbcore 217088 4 ftdi_sio,usbserial,xhci_plat_hcd,xhci_hcd
usb_common 16384 3 udc_core,usbcore,dwc3
</pre></p>
<p>I suspect if you run lsmod, you won't have any modules loaded. This would mean you need to copy the modules from the INSTALL_MOD_PATH mentioned in the linux wiki.</p>
<p>The build.sh and push.sh scripts should handle this nicely.</p>
<pre>
./build.sh && ./push.sh root@IPADDRESS
</pre> Software Development: RE: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/6553?r=6559#message-65592023-11-22T18:11:13ZJonathan Cormierjcormier@criticallink.com
<p>Sandeep Sivadas wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6553?r=6558#message-6558">RE: spidev loopback testing not working</a>:</p>
<blockquote>
<p>Hi,</p>
<p>I tried the devmem2 commands.The output got as follows</p>
<p>root@mitysom-am57x:/dev# devmem2 0x4A003460<br />/dev/mem opened.<br />Memory mapped at address 0xb6f15000.<br />Read at address 0x4A003460 (0xb6f15460): 0x0004000E</p>
<p>Then i updated the mux_data.h file for SPI4 pinmux and followed the step as in link <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/U-Boot_Setup_Pinmux">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/U-Boot_Setup_Pinmux</a><br />But instead of changing contents of core_padconf_array_essential_mitysom_devkit , i changed in core_padconf_array_essential_mitysom_nonfpga_devkit located at /boards/cl/mitysom57x/mux_data.h</p>
</blockquote>
<p>Aw okay I didn't know you were using the nonfpga variant, this makes sense. I'll add a note to the wiki.</p>
<blockquote>
<p>and then followed the steps in link <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/U-Boot_Building_for_MitySOM-AM57X">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/U-Boot_Building_for_MitySOM-AM57X</a><br />Copied MLO and u-boot.img to the SD card. Now the SPI4 loop back is working. (Kernel building is already performed as in the wiki page)</p>
<p>the output obtained are</p>
<p>root@mitysom-am57x:/opt# devmem2 0x4A003460<br />/dev/mem opened.<br />Memory mapped at address 0xb6fec000.<br />Read at address 0x4A003460 (0xb6fec460): 0x00050008<br />root@mitysom-am57x:/opt# ./spidev_test -D /dev/spidev4.0 -v<br />spi mode: 0x0<br />bits per word: 8<br />max speed: 500000 Hz (500 KHz)<br />TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......<code>....�.................<br />RX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......</code>....�.................</p>
<p>Bootlog file also attaching here. PRU ethernet,HDMI etc are still disabled.</p>
</blockquote>
<p>There are several kernel modules which are built outside of the kernel source directory and included in the sdcard by yocto. These need to be copied to the new kernel modules directory or video (pvrsrvkm.ko) and the pru stuff will stop working.</p>
<p>It is enough to copy the extra folder from the original kernel modules directory to the new one<br /><pre>
root@mitysom-am57x:~# ls /lib/modules/4.19.94-g913a232ac5/extra/
cmemk.ko debugss_kmodule.ko gdbserverproxy.ko uio_module_drv.ko
cryptodev.ko galcore.ko pvrsrvkm.ko
root@mitysom-am57x:~# cp -R /lib/modules/4.19.94-g913a232ac5/extra /lib/modules/<new build directory>
</pre></p>
<p>Note in the 57x mitysom-linux-4.19 branch, there is a push.sh script which tried to auto handle this while copying the kernel and modules to a running devkit.</p>
<p>I'll update the wiki to make this more clear.</p> Software Development: RE: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/6553?r=6558#message-65582023-11-22T05:43:14ZSandeep Sivadas
<p>Hi,</p>
<p>I tried the devmem2 commands.The output got as follows</p>
<p>root@mitysom-am57x:/dev# devmem2 0x4A003460<br />/dev/mem opened.<br />Memory mapped at address 0xb6f15000.<br />Read at address 0x4A003460 (0xb6f15460): 0x0004000E</p>
<p>Then i updated the mux_data.h file for SPI4 pinmux and followed the step as in link <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/U-Boot_Setup_Pinmux">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/U-Boot_Setup_Pinmux</a><br />But instead of changing contents of core_padconf_array_essential_mitysom_devkit , i changed in core_padconf_array_essential_mitysom_nonfpga_devkit located at /boards/cl/mitysom57x/mux_data.h</p>
<p>and then followed the steps in link <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/U-Boot_Building_for_MitySOM-AM57X">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/U-Boot_Building_for_MitySOM-AM57X</a><br />Copied MLO and u-boot.img to the SD card. Now the SPI4 loop back is working. (Kernel building is already performed as in the wiki page)</p>
<p>the output obtained are</p>
<p>root@mitysom-am57x:/opt# devmem2 0x4A003460<br />/dev/mem opened.<br />Memory mapped at address 0xb6fec000.<br />Read at address 0x4A003460 (0xb6fec460): 0x00050008<br />root@mitysom-am57x:/opt# ./spidev_test -D /dev/spidev4.0 -v<br />spi mode: 0x0<br />bits per word: 8<br />max speed: 500000 Hz (500 KHz)<br />TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......<code>....�.................<br />RX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......</code>....�.................</p>
<p>Bootlog file also attaching here. PRU ethernet,HDMI etc are still disabled.</p> Software Development: RE: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/6553?r=6556#message-65562023-11-21T15:26:41ZJonathan Cormierjcormier@criticallink.com
<p>Sandeep Sivadas wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6553?r=6555#message-6555">RE: spidev loopback testing not working</a>:</p>
<blockquote>
<p>Hi Mike,</p>
<p>Output of the spidev_test obtained is</p>
<p>root@mitysom-am57x:~# ./spidev_test -D /dev/spidev4.0 -v<br />spi mode: 0x0<br />bits per word: 8<br />max speed: 500000 Hz (500 KHz)<br />TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....�.................<br />RX | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | .............................</p>
<p>I scoped the CLK and SPI4_D0, there is no CLK or data signal is coming. I followed the same steps as in the wiki page.</p>
</blockquote>
<p>If there was no output seen on the CLK or D0 then it is very likely that the pinmux was not updated.<br />I added a troubleshooting section to the wiki page, to step you through printing out the pinmux so we can verify it was set correctly.<br /><a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Application_Using_spidev#Verify-pinmux-change-in-u-boot-was-done-correctly">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Application_Using_spidev#Verify-pinmux-change-in-u-boot-was-done-correctly</a></p>
<blockquote>
<p>Also when i updated the Kernel and uboot images, USB, 2 Ethernet and HDMI functionalities also not working</p>
</blockquote>
<p>This is concerning, are you able to build the kernel and u-boot without any changes and get these devices to function?<br />Can you share what commands you are running to build and copy the files to the devkit? As well as a boot log?</p>
<blockquote>
<p>With regards<br />Sandeep S</p>
</blockquote> Software Development: RE: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/6553?r=6555#message-65552023-11-21T12:57:56ZSandeep Sivadas
<p>Hi Mike,</p>
<p>Output of the spidev_test obtained is</p>
<p>root@mitysom-am57x:~# ./spidev_test -D /dev/spidev4.0 -v<br />spi mode: 0x0<br />bits per word: 8<br />max speed: 500000 Hz (500 KHz)<br />TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....�.................<br />RX | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | .............................</p>
<p>I scoped the CLK and SPI4_D0, there is no CLK or data signal is coming. I followed the same steps as in the wiki page. <br />Also when i updated the Kernel and uboot images, USB, 2 Ethernet and HDMI functionalities also not working</p>
<p>With regards<br />Sandeep S</p> Software Development: RE: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/6553?r=6554#message-65542023-11-21T11:22:57ZMichael Williamson
<p>Hi Sandeep,</p>
<p>Are you trying to loop spidev4.0 to spidev4.1? Or are you looping back one of the two devices onto themselves (e.g., SPI4_D0 connected to SPI4_D1 on same SPI channel)?</p>
<p>The example you linked to does not perform a loopback, it just demonstrates transmitting data (the received data is all zeros).</p>
<p>Have you scoped the CLK or output data to confirm you have the pin mux setup correctly?</p>
<p>Can you provide the output of the spidev_test command (in verbose mode) so we can see what the failure mode is?</p>
<p>With regards,<br />Mike</p> Software Development: spidev loopback testing not workinghttp://support.criticallink.com/redmine/boards/59/topics/65532023-11-21T06:16:41ZSandeep Sivadas
<p>Hi,</p>
<p>We tried to configure SPI4 in the devkit by following the guidelines in the below link "(<a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Application_Using_spidev">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Application_Using_spidev</a>)".<br />As per the link we changed mux_data.h file and the "am57xx-mitysom-baseboard.dtsi" file , then flashed the MLO and u-boot.img in to the sd-card and also copied zImage, /rootfs/lib/modules/4.19<rest_of_name> and other .dtb files so as to built the kernel.<br />spidev4.0 and spidev4.1 are listed in /dev. But SPI fails the loopback test when we tried spidev_test.c application<br />Kindly look in to it.</p>
<p>with regards<br />Sandeep S</p> Software Development: RE: Error in Cloning the branches of MitySOMhttp://support.criticallink.com/redmine/boards/59/topics/6529?r=6530#message-65302023-10-26T10:57:45ZArun Krishnan
<p>It was an issue with TI's git server which got solved now.. The above discussion can be ignored.. thank you</p> Software Development: Error in Cloning the branches of MitySOMhttp://support.criticallink.com/redmine/boards/59/topics/65292023-10-26T07:52:20ZArun Krishnan
<p>Following the procedure in the link: <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X</a>, I have used the docker images for cloning the MitySOM branches to the oe-layersetup folder inside the docker. I got the following error messages.</p>
<p>pokyuser@f6d4cbf3d374:/work/oe-layersetup$ ./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-06.03.00.106-cl-external-config.txt<br />/work/oe-layersetup<br />cloning repo bitbake<br />Cloning into '/work/oe-layersetup/sources/bitbake'...<br />warning: redirecting to <a class="external" href="https://git.openembedded.org/bitbake/">https://git.openembedded.org/bitbake/</a><br />remote: Enumerating objects: 63551, done.<br />remote: Counting objects: 100% (72/72), done.<br />remote: Compressing objects: 100% (70/70), done.<br />remote: Total 63551 (delta 47), reused 2 (delta 2), pack-reused 63479<br />Receiving objects: 100% (63551/63551), 13.35 MiB | 2.24 MiB/s, done.<br />Resolving deltas: 100% (47621/47621), done.<br />Branch '1.40' set up to track remote branch '1.40' from 'origin'.<br />Switched to a new branch '1.40'<br />Already up to date.<br />Note: checking out 'b690030efc87850951e8e3ecf4ae3c1dd1dc9b63'.<br />You are in 'detached HEAD' state. You can look around, make experimental<br />changes and commit them, and you can discard any commits you make in this<br />state without impacting any branches by performing another checkout.<br />If you want to create a new branch to retain commits you create, you may<br />do so (now or later) by using -b with the checkout command again. Example:<br />git checkout -b <new-branch-name><br />HEAD is now at b690030e runqueue: fix multiconfig task dependency filtering<br />cloning repo meta-processor-sdk<br />Cloning into '/work/oe-layersetup/sources/meta-processor-sdk'...<br />fatal: unable to access 'https://git.ti.com/processor-sdk/meta-processor-sdk/': The requested URL returned error: 503<br />git failed... remaining attempts: 4 sleeping 15 seconds<br />Cloning into '/work/oe-layersetup/sources/meta-processor-sdk'...<br />fatal: unable to access 'https://git.ti.com/processor-sdk/meta-processor-sdk/': The requested URL returned error: 503<br />git failed... remaining attempts: 3 sleeping 30 seconds<br />Cloning into '/work/oe-layersetup/sources/meta-processor-sdk'...<br />fatal: unable to access 'https://git.ti.com/processor-sdk/meta-processor-sdk/': The requested URL returned error: 503<br />git failed... remaining attempts: 2 sleeping 45 seconds<br />Cloning into '/work/oe-layersetup/sources/meta-processor-sdk'...<br />fatal: unable to access 'https://git.ti.com/processor-sdk/meta-processor-sdk/': The requested URL returned error: 503<br />git failed... remaining attempts: 1 sleeping 60 seconds<br />Cloning into '/work/oe-layersetup/sources/meta-processor-sdk'...<br />fatal: unable to access 'https://git.ti.com/processor-sdk/meta-processor-sdk/': The requested URL returned error: 503<br />git failed... giving up...<br />ERROR: Could not clone repository at <a class="external" href="https://git.ti.com/processor-sdk/meta-processor-sdk">https://git.ti.com/processor-sdk/meta-processor-sdk</a><br />pokyuser@f6d4cbf3d374:/work/oe-layersetup$</p> Software Development: RE: AM5749 Header Files for PRUhttp://support.criticallink.com/redmine/boards/59/topics/6491?r=6493#message-64932023-09-21T13:38:21ZJonathan Cormierjcormier@criticallink.com
<p>Tay Barrett wrote:</p>
<blockquote>
<p>Hi,</p>
<p>I am using the MitySOM-AM57x development board, in conjunction with code developed from TI's PRU training series. I am wondering if the #include header files for the AM572x board (found in the example labs) are applicable for AM5749 or are there other header files that are required?</p>
</blockquote>
<p>I can't say for sure, you may need to ask on the TI e2e for a definitive answer. But if I look at the AM572x and AM574x TRMs, both have the PRUSS registers at the same memory addresses.<br /><a class="external" href="https://www.ti.com/lit/ug/spruhz6l/spruhz6l.pdf">https://www.ti.com/lit/ug/spruhz6l/spruhz6l.pdf</a><br /><a class="external" href="https://www.ti.com/lit/ug/spruih8b/spruih8b.pdf">https://www.ti.com/lit/ug/spruih8b/spruih8b.pdf</a></p>
<blockquote>
<p>I am just trying to toggle an LED using PRU, which I could do using the same code on the AM5728. I have pinmuxed the appropriate pins and copied across the u-boot.img and MLO.</p>
</blockquote>
<p>If the code is working on a 5728 SOM, I'm surprised that it doesn't work the same on a 5749 SOM.</p>
<p>Could you share your pinmux? Also how are you loading the PRUSS?</p> Software Development: RE: AM5749 Header Files for PRUhttp://support.criticallink.com/redmine/boards/59/topics/6491?r=6492#message-64922023-09-21T06:14:02ZTay Barrett
<p>For clarification, the example i am using is Lab 2 from here: <a class="external" href="https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/08_03_00_19/exports/docs/common/PRU-ICSS/PRU-Hands-on-Labs.html">https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/08_03_00_19/exports/docs/common/PRU-ICSS/PRU-Hands-on-Labs.html</a></p> Software Development: AM5749 Header Files for PRUhttp://support.criticallink.com/redmine/boards/59/topics/64912023-09-21T05:25:59ZTay Barrett
<p>Hi,</p>
<p>I am using the MitySOM-AM57x development board, in conjunction with code developed from TI's PRU training series. I am wondering if the #include header files for the AM572x board (found in the example labs) are applicable for AM5749 or are there other header files that are required? <br />I am just trying to toggle an LED using PRU, which I could do using the same code on the AM5728. I have pinmuxed the appropriate pins and copied across the u-boot.img and MLO.</p>
<p>Thanks</p> Software Development: RE: ICE cannot be connected to SOM without FGPAhttp://support.criticallink.com/redmine/boards/59/topics/6432?r=6436#message-64362023-07-28T11:02:04ZJonathan Cormierjcormier@criticallink.com
<p>Glad to hear it.</p> Software Development: RE: ICE cannot be connected to SOM without FGPAhttp://support.criticallink.com/redmine/boards/59/topics/6432?r=6435#message-64352023-07-28T01:56:45ZMasayoshi Furuta
<p>By shorting pins 4 and 8, we were able to connect the ICE to the CPU.</p> Software Development: RE: ICE cannot be connected to SOM without FGPAhttp://support.criticallink.com/redmine/boards/59/topics/6432?r=6434#message-64342023-07-27T16:03:43ZJonathan Cormierjcormier@criticallink.com
<p>On J4, the TDIS signal is supposed to be connected to GND. I tested the connection on a module by shorting pins 4 and 8 using tweezers and was able to connect to the ARM over JTAG.</p>
<p><img src="http://support.criticallink.com/redmine/attachments/download/33899/clipboard-202307271201-phbgc.png" alt="" /></p>
<p>Are you able to mod the SOMs you have by adding a jumper between pins 4 and 8?</p>
<p>I will start the process to fix this on the next release of the SOM.</p>
<p>Link to TI documentation on TDIS: <a class="external" href="https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds_target_connection_guide.html#tdis-considerations">https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds_target_connection_guide.html#tdis-considerations</a></p> Software Development: RE: ICE cannot be connected to SOM without FGPAhttp://support.criticallink.com/redmine/boards/59/topics/6432?r=6433#message-64332023-07-27T14:46:27ZJonathan Cormierjcormier@criticallink.com
<p>I was able to reproduce your results on a 5746-PX-4AA-RI Rev2A. We will look into this.</p> Software Development: ICE cannot be connected to SOM without FGPAhttp://support.criticallink.com/redmine/boards/59/topics/64322023-07-27T07:33:38ZMasayoshi Furuta
<p>I am having trouble making ICE connections with the following SOM<br /> ・5728-PX-4AA-RI<br /> ・5729-PX-4AA-RI<br /> ・5746-PX-4AA-RI<br />In addition, the ICE connection is working for "5749-PM-4AA-RI" by the same operation.</p>
<p>■ICE can NOT connect to CPU <b>PROBLEM</b><br />MotherBoad:<br /> MitySOM-<abbr title="F">AM57</abbr> Family Development Kit<br />ICE:<br /> Blackhawk USB 560v2<br />GEL:<br /> idk_am572x.gel(5728-PX-4AA-RI, 5729-PX-4AA-RI)<br /> idk_am574x.gel(5746-PX-4AA-RI)</p>
<p>※gel-file is copied from the following folder.<br /><pre>
{CCS install Directory}\ccs\ccs_base\emulation\boards
</pre></p>
<p>When you try to connect to CortexA15_0(click CortexA15_0's "Connect Target"), a dialog box appears and the following is displayed</p>
<p><a href="#" onclick="$('#collapse-4dfd0690-show, #collapse-4dfd0690-hide').toggle(); $('#collapse-4dfd0690').fadeToggle(150);; return false;" id="collapse-4dfd0690-show" class="icon icon-collapsed collapsible">Diplay log</a><a href="#" onclick="$('#collapse-4dfd0690-show, #collapse-4dfd0690-hide').toggle(); $('#collapse-4dfd0690').fadeToggle(150);; return false;" id="collapse-4dfd0690-hide" class="icon icon-expended collapsible" style="display:none;">Hide log</a><div id="collapse-4dfd0690" class="collapsed-text" style="display:none;"><pre>
Error connecting to the target:
(Error -183 @ 0x0)
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.
(Emulation package 9.11.0.00128)
</pre></div></p>
<p>The following logs are generated when "Test Connection" is performed</p>
<p><a href="#" onclick="$('#collapse-bf92a392-show, #collapse-bf92a392-hide').toggle(); $('#collapse-bf92a392').fadeToggle(150);; return false;" id="collapse-bf92a392-show" class="icon icon-collapsed collapsible">Diplay log</a><a href="#" onclick="$('#collapse-bf92a392-show, #collapse-bf92a392-hide').toggle(); $('#collapse-bf92a392').fadeToggle(150);; return false;" id="collapse-bf92a392-hide" class="icon icon-expended collapsible" style="display:none;">Hide log</a><div id="collapse-bf92a392" class="collapsed-text" style="display:none;"><pre>
[Start: Blackhawk XDS560v2-USB System Trace Emulator_0]
Execute the command:
%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\YSHIMI~1.ITF\AppData\Local\TEXASI~1\
CCS\ccs1230\0\0\BrdDat\testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 560/2xx-class product.
This utility will load the program 'bh560v2u.out'.
Loaded FPGA Image: C:\ti\ccs1230\ccs\ccs_base\common\uscif\dtc_top.jbc
The library build date was 'Mar 10 2023'.
The library build time was '22:11:02'.
The library package version is '9.11.0.00128'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
An error occurred while hard opening the controller.
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.
The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.
[End: Blackhawk XDS560v2-USB System Trace Emulator_0]
</pre></div></p>
<p>■Linux(SD-Boot) <b>Noproblem</b><br />Linux booted normally and USB worked fine</p>
<ul>
<li>USB-gadget<br /><pre>
modprobe g_ether
</pre><br />Checked both sides of Type-C twice, both times enumerated at SuperSpeed.</li>
<li>USB-host<br />USB memory stick is enumerated as SS device<br /><pre>
root@mitysom-am57x:~# lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
<pre>
</li>
</ul></pre> Software Development: RE: USB touch screen support for AM572x development boardhttp://support.criticallink.com/redmine/boards/59/topics/6356?r=6373#message-63732023-06-02T15:31:02ZJonathan Cormierjcormier@criticallink.com
<p>Note you can update the command line args for the HelloWorld example to work without weston as well.</p>
<p><img src="http://support.criticallink.com/redmine/attachments/download/33591/clipboard-202306021130-ie2bs.png" alt="" /></p> Software Development: RE: USB touch screen support for AM572x development boardhttp://support.criticallink.com/redmine/boards/59/topics/6356?r=6372#message-63722023-06-02T15:29:28ZJonathan Cormierjcormier@criticallink.com
<p>Sandeep Sivadas wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6356?r=6366#message-6366">RE: USB touch screen support for AM572x development board</a>:</p>
<blockquote>
<p>Hi Jonathan,</p>
<p>We tried the evtest and weston commands. But the matrix GUI application is not responding to USB touch. <br />Then we stop the matrix GUI application and opened the wayland terminal, here the USB touch is working.<br />We tried weston-flower command and got the output successfully, USB touch is also working fine.</p>
</blockquote>
<p>Okay, that is good news. At least some things are working with the touch screen.</p>
<blockquote>
<p><strong>is the Matrix GUI application is touch enabled?</strong></p>
</blockquote>
<p>So after some quick googling, I'm seeing a lot of results describing issues between touch support, weston, and qt applications. Some seem to indicate this should have been fixed but I'm not sure.<br /><a class="external" href="https://github.com/eichenberger/qt-widgets-touch-translation">https://github.com/eichenberger/qt-widgets-touch-translation</a><br /><a class="external" href="https://wiki.qt.io/WestonTouchScreenIssues">https://wiki.qt.io/WestonTouchScreenIssues</a></p>
<p>My recommendation would be to launch the qt application without weston running. You probably don't want/need a desktop manager like weston for your product so you'll likely want to do this eventually anyways. Hopefully without weston the touch events will work correctly.<br />Note: When you get past the checkout phase, it will be a good idea to create a custom yocto filesystem without weston installed so you don't have to go in and manually stop it. This will also give you a chance to slim down your filesystem to only the tools you need.</p>
<ul>
<li>Prevent weston and matrix-gui from starting at boot<br /><pre>
root@mitysom-am57x:~# systemctl disable weston matrix-gui-2.0
weston.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable weston
update-rc.d: /etc/init.d/weston exists during rc.d purge (continuing)
Removing any system startup links for weston ...
/etc/rc0.d/K20weston
/etc/rc1.d/K20weston
/etc/rc2.d/S09weston
/etc/rc5.d/S09weston
/etc/rc6.d/K20weston
Synchronizing state of matrix-gui-2.0.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable matrix-gui-2.0
update-rc.d: /etc/init.d/matrix-gui-2.0 exists during rc.d purge (continuing)
Removing any system startup links for matrix-gui-2.0 ...
Removed /etc/systemd/system/multi-user.target.wants/matrix-gui-2.0.service.
root@mitysom-am57x:~# systemctl stop weston matrix-gui-2.0
</pre></li>
<li>Launch qt application without weston<br /><pre>
root@mitysom-am57x:~# ./HelloWorld -platform eglfs
</pre></li>
<li>Similarly the matrix gui can be launched<br /><pre>
root@mitysom-am57x:~# /usr/bin/matrix_browser http://localhost:80/ -platform eglfs
</pre></li>
</ul>
<p>Note that since we aren't relying on weston to handle input events, this page may be useful. <a class="external" href="https://doc.qt.io/qt-5/inputs-linux-device.html#touch">https://doc.qt.io/qt-5/inputs-linux-device.html#touch</a> Though hopefully the defaults will just work.</p> Software Development: RE: Support for Qt creator application for MitySOM AM57x http://support.criticallink.com/redmine/boards/59/topics/6355?r=6371#message-63712023-06-02T14:51:17ZJonathan Cormierjcormier@criticallink.com
<p>Sandeep Sivadas wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6355?r=6367#message-6367">RE: Support for Qt creator application for MitySOM AM57x </a>:</p>
<blockquote>
<p>Hi Jonathan</p>
<p>We followed the guidelines as per the link <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/QT_Starter_Guide_2022">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/QT_Starter_Guide_2022</a> and installed Qt Creator,Qt5 Designer,Qt5 Assistant,Qt5 Linguist.(Qt Version:5.9.5)</p>
<p>But while going through this step " <strong>Select the Compilers tab. Click on Add -> GCC -> C. Navigate to <SDK path>/sysroots/x86_64-arago-linux/usr/bin/arm-criticallink-linux-gnueabi/ and select arm-criticallink-linux-gnueabi-gcc. Change name to "GCC (C 57x)"</strong> ", we couldn't find the mentioned file/folder <strong>arm-criticallink-linux-gnueabi</strong>, instead we find the following set of files/folders in <strong>bin</strong> folder (screenshot is attaching herewith )</p>
</blockquote>
<p>You are right, this was a copy/paste mistake. I've updated the instructions. You found the correct path.</p>
<blockquote>
<p>Another problem we come across is in the step : " <strong>Select the "Qt Versions" tab that is shown. Click the "Add..." button. Navigate to <SDK path>/sysroots/x86_64-arago-linux/usr/bin/ and click on qmake. Change Name to "Qt %{Qt:Version} (57x)"</strong> ", a dialogue box appeared telling that the same was added already and we find a red error icon across the qmake location file name.(screenshot is attaching herewith)</p>
</blockquote>
<p>Can you check again after setting up the compilers? You may need to hit apply or okay and reopen the dialog.<br />Also did you source the toolchain and launch qtcreator from the same terminal?</p>
<blockquote>
<p>Thanks and Regards<br />Sandeep S</p>
</blockquote> Software Development: RE: Support for Qt creator application for MitySOM AM57x http://support.criticallink.com/redmine/boards/59/topics/6355?r=6367#message-63672023-06-02T09:58:15ZSandeep Sivadas
<p>Hi Jonathan</p>
<p>We followed the guidelines as per the link <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/QT_Starter_Guide_2022">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/QT_Starter_Guide_2022</a> and installed Qt Creator,Qt5 Designer,Qt5 Assistant,Qt5 Linguist.(Qt Version:5.9.5)</p>
<p>But while going through this step " <strong>Select the Compilers tab. Click on Add -> GCC -> C. Navigate to <SDK path>/sysroots/x86_64-arago-linux/usr/bin/arm-criticallink-linux-gnueabi/ and select arm-criticallink-linux-gnueabi-gcc. Change name to "GCC (C 57x)"</strong> ", we couldn't find the mentioned file/folder <strong>arm-criticallink-linux-gnueabi</strong>,instead we find the following set of files/folders in <strong>bin</strong> folder (screenshot is attaching herewith )</p>
<p>Another problem we come across is in the step : " <strong>Select the "Qt Versions" tab that is shown. Click the "Add..." button. Navigate to <SDK path>/sysroots/x86_64-arago-linux/usr/bin/ and click on qmake. Change Name to "Qt %{Qt:Version} (57x)"</strong> ",a dialogue box appeared telling that the same was added already and we find a red error icon across the qmake location file name.(screenshot is attaching herewith)</p>
<p>Thanks and Regards<br />Sandeep S</p> Software Development: RE: USB touch screen support for AM572x development boardhttp://support.criticallink.com/redmine/boards/59/topics/6356?r=6366#message-63662023-06-02T05:47:14ZSandeep Sivadas
<p>Hi Jonathan,</p>
<p>We tried the evtest and weston commands. But the matrix GUI application is not responding to USB touch. <br />Then we stop the matrix GUI application and opened the wayland terminal, here the USB touch is working.<br />We tried weston-flower command and got the output successfully, USB touch is also working fine.</p>
<p><strong>is the Matrix GUI application is touch enabled?</strong></p>
<p>We are now trying out the Qt application as per the wiki tutorial. If you have any applications specifically for touch screen application.please share the same.</p>
<p>Thanks and regards<br />Sandeep S</p> Software Development: RE: USB touch screen support for AM572x development boardhttp://support.criticallink.com/redmine/boards/59/topics/6356?r=6365#message-63652023-05-31T14:25:49ZJonathan Cormierjcormier@criticallink.com
<blockquote>
<p>hid-generic 0003:0461:0022.0003: input: USB HID v1.00 Device</p>
</blockquote>
<p>Okay good news, looks like the HID driver is getting loaded.</p>
<p>You should be able to use the "evtest" command to test the input device to make sure touch events are working.</p>
<p>Also, Looks like weston may need some kind of configuring to get it to work with a touchscreen. Some links I found with a quick google search.</p>
<p><a class="external" href="https://community.nxp.com/t5/i-MX-Processors/Want-to-enable-the-touchscreen-support-on-weston/td-p/1469966">https://community.nxp.com/t5/i-MX-Processors/Want-to-enable-the-touchscreen-support-on-weston/td-p/1469966</a><br /><a class="external" href="https://askubuntu.com/questions/1414431/weston-is-not-receiving-touch-input-regarding-touch-input-as-mouse-input">https://askubuntu.com/questions/1414431/weston-is-not-receiving-touch-input-regarding-touch-input-as-mouse-input</a></p>
<p>Useful tools from the links:</p>
<p>evtest<br />weston-touch-calibrator<br />weston-simple-touch</p>
<p>I don't have a USB touchscreen to play with so not sure how to help you. I would recommend reaching out to Newhaven as they may have experience with wayland/weston and know how to configure it. Please update us if you figure out any magic sauce.</p> Software Development: RE: USB touch screen support for AM572x development boardhttp://support.criticallink.com/redmine/boards/59/topics/6356?r=6363#message-63632023-05-31T05:44:27ZSandeep Sivadas
<p>Hi Jonathan,</p>
<p>Thank you for your support.</p>
<p>When i connected the Newhaven Display's USB with the AM572x Development kit, got the following printout messages</p>
<p>[ 3267.951725] usb 1-1.2: new full-speed USB device number 5 using xhci-hcd<br />[ 3268.083379] usb 1-1.2: New USB device found, idVendor=0461, idProduct=0022, bcdDevice= 1.00<br />[ 3268.091857] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />[ 3268.099267] usb 1-1.2: Product: Newhaven Display<br />[ 3268.104064] usb 1-1.2: Manufacturer: NHD<br />[ 3268.161296] input: NHD Newhaven Display as /devices/platform/44000000.ocp/488c0000.omap_dwc3_2/488d0000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.2/1-1.2:1.0/0003:0461:0022.0003/input/input2<br />[ 3268.177894] hid-generic 0003:0461:0022.0003: input: USB HID v1.00 Device [NHD Newhaven Display ] on usb-xhci-hcd.1.auto-1.2/input0</p>
<p>Then tried the lsusb command and got the output as shown below</p>
<p>root@mitysom-am57x:~# lsusb<br />Bus 001 Device 003: ID 0461:0022 Primax Electronics, Ltd<br />Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br />Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub<br />Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</p>
<p>Then tried the lsusb -v command and the output obtained is attached as text file. Kindly look in to it.</p>
<p>With regards<br />Sandeep S</p> Software Development: RE: Support for Qt creator application for MitySOM AM57x http://support.criticallink.com/redmine/boards/59/topics/6355?r=6362#message-63622023-05-30T19:26:34ZJonathan Cormierjcormier@criticallink.com
<p>FYI<br /><pre>
root@mitysom-am57x:~# ls -la /usr/lib/libQt5Network.*
-rw-r--r-- 1 root root 1339 Sep 9 2021 /usr/lib/libQt5Network.prl
lrwxrwxrwx 1 root root 23 Sep 9 2021 /usr/lib/libQt5Network.so -> libQt5Network.so.5.11.3
lrwxrwxrwx 1 root root 23 Sep 9 2021 /usr/lib/libQt5Network.so.5 -> libQt5Network.so.5.11.3
lrwxrwxrwx 1 root root 23 Sep 9 2021 /usr/lib/libQt5Network.so.5.11 -> libQt5Network.so.5.11.3
-rwxr-xr-x 1 root root 1118320 Sep 9 2021 /usr/lib/libQt5Network.so.5.11.3
</pre></p> Software Development: RE: Support for Qt creator application for MitySOM AM57x http://support.criticallink.com/redmine/boards/59/topics/6355?r=6361#message-63612023-05-30T19:25:14ZJonathan Cormierjcormier@criticallink.com
<p>Sandeep Sivadas wrote:</p>
<blockquote>
<p>Hi,</p>
<p>We have to develop a QT application for our AM57x Development board. which version of QT creator is supported with AM57x ?<br />Is there any example programs and getting started tutorials for the same.</p>
<p>with regards</p>
<p>Sandeep S</p>
</blockquote>
<p>In my experience, you should use the latest version of QT creator and expect it to work with whatever version of QT you are developing for.</p>
<p>The version of QT that ships with the <a href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Repositories_and_Pre-built_Images" class="external">20220323 tisdk-rootfs-image</a> image is 5.11.3</p>
<p>I wrote up this wiki page, hope it helps. <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/QT_Starter_Guide_2022">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/QT_Starter_Guide_2022</a></p> Software Development: RE: USB touch screen support for AM572x development boardhttp://support.criticallink.com/redmine/boards/59/topics/6356?r=6360#message-63602023-05-30T17:48:03ZJonathan Cormierjcormier@criticallink.com
<p>Newhaven doesn't provide a lot of details on this USB touch interface other than it's a "USB-HID device". Which I would normally expect to fall under the same standard driver used by the USB mouse. But since the mouse worked and this didn't we need to dig deeper.</p>
<p>Can you capture the USB PID/VID of the touchscreen? This will often be printed out by the kernel when a usb device is plugged in. With this, I can search through the kernel source to see if there are any drivers which support this device.</p>
<p>Or can be gotten from the "lsusb" command<br /><pre>
root@mitysom-am57x:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</pre></p>
<p>And would also be useful to have the output from "lsusb -v"</p>
<p>There are over 100 hid drivers in the kernel so there are good chances we just need to find and enable to correct one.</p> Software Development: RE: Example USB (usb 3.0 port) is not workhttp://support.criticallink.com/redmine/boards/59/topics/6340?r=6358#message-63582023-05-30T14:22:53ZJonathan Cormierjcormier@criticallink.com
<p>Was able to verify that when plugged into a usb2.0 port, the gadget reports high-speed config and then reports super-speed config when plugged into usb3.0 port.<br /><pre>
[ 152.333180] g_cdc gadget: high-speed config #1: CDC Composite (ECM + ACM)
[ 164.797196] g_cdc gadget: super-speed config #1: CDC Composite (ECM + ACM)
</pre></p> Software Development: USB touch screen support for AM572x development boardhttp://support.criticallink.com/redmine/boards/59/topics/63562023-05-30T05:50:49ZSandeep Sivadas
<p>Hi,</p>
<p>We are using a Capacitive HDMI TFT Module (Make: Newhaven) with AM572x development board. On booting the linux with SD card provided with the Development kit, the USB touch is not working.<br />We can connect mouse device with the USB port in Development board and access the TFT display. <br />Is there touch support in the default display setting provided with the bootable Linux SD card.<br />How can we enable USB touch for our TFT Display module?</p>
<p>Details of TFT display we are using is <br />P/N : <strong>NHD-5.0-HDMI-N-RTXL-CTU</strong><br /><a class="external" href="https://newhavendisplay.com/5-0-inch-premium-capacitive-hdmi-tft-module/">https://newhavendisplay.com/5-0-inch-premium-capacitive-hdmi-tft-module/</a></p>
<p>Thanks and regards<br />Sandeep S</p> Software Development: Support for Qt creator application for MitySOM AM57x http://support.criticallink.com/redmine/boards/59/topics/63552023-05-30T05:30:33ZSandeep Sivadas
<p>Hi,</p>
<p>We have to develop a QT application for our AM57x Development board. which version of QT creator is supported with AM57x ?<br />Is there any example programs and getting started tutorials for the same.</p>
<p>with regards</p>
<p>Sandeep S</p> Software Development: RE: Query - Example Baseboard I2C Power Monitorhttp://support.criticallink.com/redmine/boards/59/topics/6351?r=6352#message-63522023-05-25T10:30:54ZMichael Williamson
<p>The original linux kernel driver for the LTC2945 has a 0.001 Ohm resistor value hardcoded in the logic that converts measured voltage across the sense resistor to current.</p>
<p>Our current / released board design has been using 0.01 Ohms as the sense resistor. So the original driver was computing the current with a 10x error (it was reporting a current value that was 10x higher than what is actually passing through the current resistor).</p>
<p>We have pushed <a href="https://support.criticallink.com/gitweb/?p=processor-sdk-linux.git;a=commitdiff;h=c9071bf1b32c76e59042b0c2a130ff1be781df57;hp=9ceb5b5956b11a236268e5fbb57d76ae757e87d7" class="external">a patch</a> into the mainline (and our latest kernel sources on our git server) that allows the value of the resistor to be loaded out of the device tree, so that you can program in the 0.01 Ohm value instead of the 0.001 value that is assumed by the driver. This will result in the correct current / power readback (if you have the patch applied).</p>
<p>With regards,<br />Mike</p> Software Development: Query - Example Baseboard I2C Power Monitorhttp://support.criticallink.com/redmine/boards/59/topics/63512023-05-25T05:24:02ZSandeep Sivadas
<p>Hi,</p>
<p>We tested the i2C power monitor as per the below link and got the result as shown below. <br /><a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Example_Baseboard_I2C_Power_Monitor">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Example_Baseboard_I2C_Power_Monitor</a></p>
<p>root@mitysom-am57x:/sys/class/hwmon/hwmon1# tail *input<br />> curr1_input <<br />7300<br />> in1_input <<br />5000 <br />> in2_input <<br />988 <br />> power1_input <<br />36500000</p>
<p>As per the calculation provided in the wiki page the current drawn is 7300/1000 = 7.3A</p>
<p>Please clarify the Note: provided in the wiki page<br /><strong>Note: An early version of the LTC2945 driver assumed a resistor value different from the actual resistor value used on the development kit. This difference resulted in values for the current and power which were 10 times larger than the actual values. A change to the driver was made and committed to Linux to correct this. The formulas shown below assume the newer driver is being used.</strong></p>
<p>With regards</p>
<p>Sandeep S</p> Software Development: RE: Example USB (usb 3.0 port) is not workhttp://support.criticallink.com/redmine/boards/59/topics/6340?r=6347#message-63472023-05-12T08:00:57ZMasayoshi Furuta
<ul>
<li>R59(USB_ID) behavior</li>
</ul>
<blockquote>
<p>Can you measure the voltage on R59? (this is on the underside of the board and should be unpopulated). Both sides should be ~1.8V when no drive is plugged in.<br />The side by C95 should be ~0V when a flash drive is connected. This is the USB_ID output from U12 (HD3SS3220). This goes to the processor board which should enable DRVVBUS to enable the 5V VBUS.</p>
</blockquote>
<p>Both sides were 1.77V regardless of whether or not a USB device was connected<br />At this point, I think the behavior is different from what we expect.</p>
<ul>
<li>USB 3.0 Peripheral (RNDIF gadget)</li>
</ul>
<blockquote>
<p>Have you tested if you can connect the devkit to your PC in peripheral mode? You may need to run "modprobe g_ether".</p>
</blockquote>
<p>I was able to confirm that I could connect in peripheral mode, but it seems to be unstable.<br />Connection: PC (USB 3.0 A port) - cable - (Type-C) devkit<br />When the cable on Type-C side is unplugged and plugged in, the PC (Linux) frequently enumerates it as Hi-Speed device or Full-Speed device.<br />After the PC has recognized the device at Super-Speed, it will be recognized again at Super-Speed even if the PC side connector is unplugged or plugged in.</p>
<p>Your log shows that gadget is recognized as hi-speed. (Host port is hi-speed?)</p>
<pre>
[ 147.135587] g_ether gadget: high-speed config #1: CDC Ethernet (ECM)
</pre>
<ul>
<li>Board Label information</li>
</ul>
<p>The label included the following information</p>
<pre>
Board #1
20026899
80-001317RH-3
20-10-10 B
</pre><br /><pre>
Board #2
20026893
80-001317RH-3
20-10-10 B
</pre>
<blockquote>
<p>Note it can also be a good idea to try a usb-C connector in both directions in case one direction is broken.</p>
</blockquote>
Yes.<br />We tried.
<ul>
<li>Flip switching test was conducted.</li>
<li>Several cables were used</li>
<li>Only cables listed in the USB specification were used (male to male)</li>
<li>The cable used is probably USB logo certified cable.</li>
<li>The device used works fine when connected to a PC.</li>
</ul> Software Development: RE: Example USB (usb 3.0 port) is not workhttp://support.criticallink.com/redmine/boards/59/topics/6340?r=6345#message-63452023-05-11T15:11:02ZJonathan Cormierjcormier@criticallink.com
<p>Note it can also be a good idea to try a usb-C connector in both directions in case one direction is broken.</p> Software Development: RE: Example USB (usb 3.0 port) is not workhttp://support.criticallink.com/redmine/boards/59/topics/6340?r=6344#message-63442023-05-11T15:05:05ZJonathan Cormierjcormier@criticallink.com
<p>)Masayoshi Furuta wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6340?r=6343#message-6343">RE: Example USB (usb 3.0 port) is not work</a>:</p>
<blockquote><blockquote>
<p>tisdk-rootfs-image-mitysom-am57x-20210909.rootfs.img.zip</p>
</blockquote>
<p>The new image could NOT solve the problem either.</p>
</blockquote>
<p>Okay, at least we are working from a known state.</p>
<blockquote>
<p>I was able to download the image you restored and tried the USB 3.0 host operation.<br />However, when I connected the device, it did not enumerate in lsusb</p>
<p>It seems that VBUS is not output when the device is connected</p>
</blockquote>
<p>Can you measure the voltage on R59? (this is on the underside of the board and should be unpopulated). Both sides should be ~1.8V when no drive is plugged in. The side by C95 should be ~0V when a flash drive is connected. This is the USB_ID output from U12 (HD3SS3220). This goes to the processor board which should enable DRVVBUS to enable the 5V VBUS.</p>
<p>Also, can you measure pin 4 on U14 (TPS2561)? This should go high (DRVVBUS) when the voltage on R59 (USB_ID) goes low. Unfortunately, these pins are super tiny so it may be hard to probe them.<br /><img src="http://support.criticallink.com/redmine/attachments/download/33456/clipboard-202305111102-i8bm4.png" alt="" /></p>
<blockquote>
<p>Is it working fine in your environment?</p>
</blockquote>
<p>Yes, I flashed this image and was able to connect to my PC in Peripheral mode and also connected a <a href="https://www.amazon.com/SanDisk-128GB-Ultra-Drive-Type-C/dp/B01EZ0X55C/" class="external">USB-c flash drive</a><br /><a class="attachment" href="http://support.criticallink.com/redmine/attachments/33454">host_flashdrive.log</a><br /><a class="attachment" href="http://support.criticallink.com/redmine/attachments/33455">peripheral_rndis.log</a></p>
<p>Have you tested if you can connect the devkit to your PC in peripheral mode? You may need to run "modprobe g_ether".<br /><a class="wiki-page" href="http://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Example_RNDIS">Example RNDIS</a></p>
<blockquote>
<blockquote><blockquote>
<p>Is it safe to assume that the boards being sold have resolved the following issues?<br /><a class="external" href="https://e2e.ti.com/support/interface-group/interface/f/interface-forum/937216/hd3ss3220-request-sch-review-am57x-ss-is-not-working">https://e2e.ti.com/support/interface-group/interface/f/interface-forum/937216/hd3ss3220-request-sch-review-am57x-ss-is-not-working</a></p>
</blockquote></blockquote></blockquote>
<p>Note that for this quoted issue, connected devices would still connect, just at USB2 speeds. As far as I'm aware all boards shipped had this fix.</p>
<blockquote><blockquote>
<p>What is the 80- number on your devkit?</p>
</blockquote>
<p>Both of the two sets I have, have the same following numbers.</p>
<p>DK# 80-001430</p>
</blockquote>
<p>I'm looking for the entire 80- number on the barcode located near the FMC connector. Should be something like 80-001317RI-2. As well as the serial number just above it.</p> Software Development: RE: Example USB (usb 3.0 port) is not workhttp://support.criticallink.com/redmine/boards/59/topics/6340?r=6343#message-63432023-05-11T01:21:30ZMasayoshi Furuta
<blockquote>
<p>tisdk-rootfs-image-mitysom-am57x-20210909.rootfs.img.zip</p>
</blockquote>
<p>The new image could NOT solve the problem either.</p>
<p>I was able to download the image you restored and tried the USB 3.0 host operation.<br />However, when I connected the device, it did not enumerate in lsusb</p>
<p>It seems that VBUS is not output when the device is connected</p>
<p>Is it working fine in your environment?</p>
<blockquote><blockquote>
<p>Is it safe to assume that the boards being sold have resolved the following issues?<br /><a class="external" href="https://e2e.ti.com/support/interface-group/interface/f/interface-forum/937216/hd3ss3220-request-sch-review-am57x-ss-is-not-working">https://e2e.ti.com/support/interface-group/interface/f/interface-forum/937216/hd3ss3220-request-sch-review-am57x-ss-is-not-working</a></p>
</blockquote>
<p>What is the 80- number on your devkit?</p>
</blockquote>
<p>Both of the two sets I have have the same following numbers.</p>
<p>DK# 80-001430</p> Software Development: RE: Example USB (usb 3.0 port) is not workhttp://support.criticallink.com/redmine/boards/59/topics/6340?r=6342#message-63422023-05-10T14:40:45ZJonathan Cormierjcormier@criticallink.com
<p>Jonathan Cormier wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6340?r=6341#message-6341">RE: Example USB (usb 3.0 port) is not work</a>:</p>
<blockquote>
<p>Masayoshi Furuta wrote:</p>
<blockquote>
<p><a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Example_usb">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Example_usb</a></p>
<p>I tested with this procedure and got the following results.<br />We tested with two DevKits with the same results.</p>
<ul>
<li>USB-2.0 Ports on MitySOM AM54 board recognized USB memroy successfully.</li>
<li>However, the USB-3.0 Port host operation does not recognize the device (HUB, USB memroy).</li>
</ul>
<p>The results of lsusb and lsusb -t are as follows.</p>
<p>[...]</p>
<p>[...]</p>
<p>The USB 3.0 port does not appear to be supplying VBUS even though the device is connected.<br />Is there something I need to configure that is not mentioned in the wiki when operating the USB 3.0 port?</p>
<p>In the above test, I used the SD card included in the Devkit to run Linux.<br />If you have the latest PreBuild, please update link on the Wiki<br />The link listed in the Wiki was not accessible.</p>
<p>tisdk-rootfs-image<br /><a class="external" href="https://support.criticallink.com/files/mitysom57x/tisdk-rootfs-image-mitysom-am57x-20210909.rootfs.img.zip">https://support.criticallink.com/files/mitysom57x/tisdk-rootfs-image-mitysom-am57x-20210909.rootfs.img.zip</a></p>
</blockquote>
<p>Sorry you caught us at a bad time, we had a power outage yesterday so the support site was switched over to a backup location that didn't have all the files. This should be resolved by the end of business today.</p>
</blockquote>
<p>Main server has been restored</p> Software Development: RE: Example USB (usb 3.0 port) is not workhttp://support.criticallink.com/redmine/boards/59/topics/6340?r=6341#message-63412023-05-10T14:11:54ZJonathan Cormierjcormier@criticallink.com
<p>Masayoshi Furuta wrote:</p>
<blockquote>
<p><a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Example_usb">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Example_usb</a></p>
<p>I tested with this procedure and got the following results.<br />We tested with two DevKits with the same results.</p>
<ul>
<li>USB-2.0 Ports on MitySOM AM54 board recognized USB memroy successfully.</li>
<li>However, the USB-3.0 Port host operation does not recognize the device (HUB, USB memroy).</li>
</ul>
<p>The results of lsusb and lsusb -t are as follows.</p>
<p>[...]</p>
<p>[...]</p>
<p>The USB 3.0 port does not appear to be supplying VBUS even though the device is connected.<br />Is there something I need to configure that is not mentioned in the wiki when operating the USB 3.0 port?</p>
<p>In the above test, I used the SD card included in the Devkit to run Linux.<br />If you have the latest PreBuild, please update link on the Wiki<br />The link listed in the Wiki was not accessible.</p>
<p>tisdk-rootfs-image<br /><a class="external" href="https://support.criticallink.com/files/mitysom57x/tisdk-rootfs-image-mitysom-am57x-20210909.rootfs.img.zip">https://support.criticallink.com/files/mitysom57x/tisdk-rootfs-image-mitysom-am57x-20210909.rootfs.img.zip</a></p>
</blockquote>
<p>Sorry you caught us at a bad time, we had a power outage yesterday so the support site was switched over to a backup location that didn't have all the files. This should be resolved by the end of business today.</p>
<blockquote>
<p>Is it safe to assume that the boards being sold have resolved the following issues?<br /><a class="external" href="https://e2e.ti.com/support/interface-group/interface/f/interface-forum/937216/hd3ss3220-request-sch-review-am57x-ss-is-not-working">https://e2e.ti.com/support/interface-group/interface/f/interface-forum/937216/hd3ss3220-request-sch-review-am57x-ss-is-not-working</a></p>
</blockquote>
<p>What is the 80- number on your devkit?</p> Software Development: Example USB (usb 3.0 port) is not workhttp://support.criticallink.com/redmine/boards/59/topics/63402023-05-10T12:57:13ZMasayoshi Furuta
<p><a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Example_usb">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Example_usb</a></p>
<p>I tested with this procedure and got the following results.<br />We tested with two DevKits with the same results.</p>
<ul>
<li>USB-2.0 Ports on MitySOM AM54 board recognized USB memroy successfully.</li>
<li>However, the USB-3.0 Port host operation does not recognize the device (HUB, USB memroy).</li>
</ul>
<p>The results of lsusb and lsusb -t are as follows.</p>
<pre>
root@mitysom-am57x:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</pre>
<pre>
root@mitysom-am57x:~# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
</pre>
<p>The USB 3.0 port does not appear to be supplying VBUS even though the device is connected.<br />Is there something I need to configure that is not mentioned in the wiki when operating the USB 3.0 port?</p>
<p>In the above test, I used the SD card included in the Devkit to run Linux.<br />If you have the latest PreBuild, please update link on the Wiki<br />The link listed in the Wiki was not accessible.</p>
<p>tisdk-rootfs-image<br /><a class="external" href="https://support.criticallink.com/files/mitysom57x/tisdk-rootfs-image-mitysom-am57x-20210909.rootfs.img.zip">https://support.criticallink.com/files/mitysom57x/tisdk-rootfs-image-mitysom-am57x-20210909.rootfs.img.zip</a></p>
<p>Is it safe to assume that the boards being sold have resolved the following issues?<br /><a class="external" href="https://e2e.ti.com/support/interface-group/interface/f/interface-forum/937216/hd3ss3220-request-sch-review-am57x-ss-is-not-working">https://e2e.ti.com/support/interface-group/interface/f/interface-forum/937216/hd3ss3220-request-sch-review-am57x-ss-is-not-working</a></p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6339#message-63392023-05-09T13:37:30ZJonathan Cormierjcormier@criticallink.com
<p>Sandeep Sivadas wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6322?r=6337#message-6337">RE: Yocto build for mitySOM AM57x</a>:</p>
<blockquote>
<p>Hi,</p>
<p>1. In the meantime, you should be able to use the released filesystem and replace just the kernel on it. And be able to make headway with customizing your kernel.</p>
<p>Q. Can you please clarify the point above. I didnt get how to do this.</p>
</blockquote>
<p>You can update/customize the kernel without rebuilding the whole filesystem. You just need to update the files located on the boot partition of the sdcard.<br />See <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel#Building-the-kernel">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel#Building-the-kernel</a></p>
<blockquote>
<p>2. Added some fixes for a few recipes which SRC urls changed slightly. Let me know if you run into any more issues.</p>
<p>Q. Do i need to update the changes in my build directory? where can i find the updated fixes.</p>
</blockquote>
<p>If you rerun the "oe-layertool-setup.sh" step on the wiki it will grab any new changes.</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6337#message-63372023-05-09T04:29:01ZSandeep Sivadas
<p>Hi,</p>
<p>1. In the meantime, you should be able to use the released filesystem and replace just the kernel on it. And be able to make headway with customizing your kernel.</p>
<p>Q. Can you please clarify the point above.I didnt get how to do this.</p>
<p>2. Added some fixes for a few recipes which SRC urls changed slightly. Let me know if you run into any more issues.</p>
<p>Q. Do i need to update the changes in my build directory? where can i find the updated fixes.</p>
<p>Thanks & regards</p>
<p>Sandeep s</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6336#message-63362023-05-08T19:19:36ZJonathan Cormierjcormier@criticallink.com
<p>Added some fixes for a few recipes which SRC urls changed slightly. Let me know if you run into any more issues.</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6335#message-63352023-05-05T13:55:45ZJonathan Cormierjcormier@criticallink.com
<p>Looks like it built successfully this time. I'll let you know how I get along with the systemd issue, I may not have time until next week.</p>
<p>In the meantime, you should be able to use the released filesystem and replace just the kernel on it. And be able to make headway with customizing your kernel.<br /><a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Repositories_and_Pre-built_Images">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Repositories_and_Pre-built_Images</a></p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6334#message-63342023-05-05T01:47:14ZSandeep Sivadas
<p>Hi,</p>
<p>I have tried to rebuild qtbase as told above. The log files are attaching here.</p>
<p>Thanks & regards</p>
<p>Sandeep s</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6333#message-63332023-05-04T22:18:20ZJonathan Cormierjcormier@criticallink.com
<p>Hi Sandeep,</p>
<p>I've run into some issues building the systemd package during the build. I am looking into it.</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6332#message-63322023-05-04T13:17:54ZJonathan Cormierjcormier@criticallink.com
<p>1. Great</p>
<p>2. I'm not sure what would have caused this file to get truncated. Seems like some kind of file corruption, not sure. Can you try to rebuild just qtbase? <code>MACHINE=mitysom-am57x bitbake qtbase -c cleanall && MACHINE=mitysom-am57x bitbake qtbase</code></p>
<pre>
| /home/mitysom/tools/mitysom-57x/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/8.3.0/../../../../arm-linux-gnueabihf/bin/ld: .obj/tst_qeventdispatcher.o: file not recognized: file truncated
</pre> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6331#message-63312023-05-04T08:45:18ZSandeep Sivadas
<p>Hi,</p>
<p>1. I tried the custom-crops modifications and got the menuconfig window.</p>
<p>2. I have tried to build MACHINE=mitysom-am57x bitbake tisdk-rootfs-image, but got some errors as shown below</p>
<p>ERROR: qtbase-5.11.3+gitAUTOINC+08de243eaa-r0.arago16.tisdk5.7 do_compile: oe_runmake failed<br />ERROR: qtbase-5.11.3+gitAUTOINC+08de243eaa-r0.arago16.tisdk5.7 do_compile: Function failed: do_compile (log file is located at /work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work/armv7at2hf-neon-linux-gnueabi/qtbase/5.11.3+gitAUTOINC+08de243eaa-r0.arago16.tisdk5.7/temp/log.do_compile.23819)<br />ERROR: Logfile of failure stored in: /work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work/armv7at2hf-neon-linux-gnueabi/qtbase/5.11.3+gitAUTOINC+08de243eaa-r0.arago16.tisdk5.7/temp/log.do_compile.23819<br />Log data follows:</p>
<p>Log data file is attaching here with. Kindly check the file.</p>
<p>Thanks and regards<br />Sandeep S</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6330#message-63302023-05-03T14:12:32ZJonathan Cormierjcormier@criticallink.com
<p>Sandeep Sivadas wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6322?r=6329#message-6329">RE: Yocto build for mitySOM AM57x</a>:</p>
<blockquote>
<p>Hi,</p>
<p>Thank you for your support.<br />I tried the updated steps for yocto build and it worked fine.</p>
<p>1. The command i used for bitbake build is "MACHINE=mitysom-am57x bitbake arago-base-tisdk-image". The image written to the SD card and booting is completed.<br />But LCD Display connected to the HDMI port is blank (showing white page). Is there any other setting we need to do for HDMI communication?</p>
</blockquote>
<p>The arago-base-tisdk-image is a minimal filesystem that doesn't include the packages for the video driver or an Xserver.<br />You can check arago-base-tisdk-image-mitysom-am57x.manifest to see all the packages that get installed.</p>
<p>The tisdk-rootfs-image is a full featured image which does have the graphics drivers and wayland installed so that you will get a desktop prompt.</p>
<blockquote>
<p>2. When i tried the command for changing the configuration of the kernel, i got the following errors. It showing Unable to find the ncurses package.<br />Please help on this..</p>
_<br />GEN ./Makefile
*
<ul>
<li>Unable to find the ncurses package.</li>
<li>Install ncurses (ncurses-devel or libncurses-dev</li>
<li>depending on your distribution).
<strong><br />/work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work-shared/mitysom-am57x/kernel-source/scripts/kconfig/Makefile:228: recipe for target 'scripts/kconfig/.mconf-cfg' failed<br />make<sup><a href="#fn3">3</a></sup>: <b></strong> [scripts/kconfig/.mconf-cfg] Error 1<br />/work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work-shared/mitysom-am57x/kernel-source/Makefile:534: recipe for target 'menuconfig' failed<br />make<sup><a href="#fn2">2</a></sup>: <strong></b> [menuconfig] Error 2<br />Makefile:146: recipe for target 'sub-make' failed<br />make<sup><a href="#fn1">1</a></sup>: <b></strong> [sub-make] Error 2<br />Makefile:24: recipe for target '__sub-make' failed<br />make: *</b> [__sub-make] Error 2<br />Command failed.<br />Press any key to continue..._</li>
</ul>
<p>--Sandeep S</p>
</blockquote>
<p>The crops/poky docker image doesn't have the libncurses-dev package installed that menuconfig requires.</p>
<p>Depending on what you're trying to do I can make a few suggestions.</p>
<ul>
<li>You can create your own Dockerfile, using the crops image as a base, and add the missing packages you want
<ul>
<li><code>mkdir custom-crops && cd custom-crops</code></li>
<li><code>vim Dockerfile</code><br /><pre>
FROM crops/poky:ubuntu-18.04
USER root
RUN apt-get install libncurses5-dev -y
USER usersetup
</pre></li>
<li><code>docker build . --tag custom_crops</code></li>
<li>Then replace "crops/poky:ubuntu-18.04" in the docker command with "custom_crops" <br /><pre>
docker run --rm -it -v $PWD:/work -v /home/tools:/home/tools --tmpfs /opt/poky --env "TOOLCHAIN_PATH_ARMV7=/home/tools/mitysom-57x/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf" custom_crops --workdir=/work
pokyuser@a6dbf190ee68:/work/build$ MACHINE=mitysom-am57x bitbake virtual/kernel -c menuconfig
...
Loading cache: 100% |##############################################################################| Time: 0:00:01
Loaded 4677 entries from dependency cache.
</pre></li>
</ul></li>
</ul>
<p>Sorry about this confusion, I'll see if we can clean up the docs</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6329#message-63292023-05-03T12:25:01ZSandeep Sivadas
<p>Hi,</p>
<p>Thank you for your support.<br />I tried the updated steps for yocto build and it worked fine.</p>
<p>1. The command i used for bitbake build is "MACHINE=mitysom-am57x bitbake arago-base-tisdk-image". The image written to the SD card and booting is completed.<br />But LCD Display connected to the HDMI port is blank (showing white page). Is there any other setting we need to do for HDMI communication?</p>
<p>2. When i tried the command for changing the configuration of the kernel, i got the following errors. It showing Unable to find the ncurses package.<br />Please help on this..</p>
_<br /> GEN ./Makefile
*
<ul>
<li>Unable to find the ncurses package.</li>
<li>Install ncurses (ncurses-devel or libncurses-dev</li>
<li>depending on your distribution).
<strong><br />/work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work-shared/mitysom-am57x/kernel-source/scripts/kconfig/Makefile:228: recipe for target 'scripts/kconfig/.mconf-cfg' failed<br />make<sup><a href="#fn3">3</a></sup>: <b></strong> [scripts/kconfig/.mconf-cfg] Error 1<br />/work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work-shared/mitysom-am57x/kernel-source/Makefile:534: recipe for target 'menuconfig' failed<br />make<sup><a href="#fn2">2</a></sup>: <strong></b> [menuconfig] Error 2<br />Makefile:146: recipe for target 'sub-make' failed<br />make<sup><a href="#fn1">1</a></sup>: <b></strong> [sub-make] Error 2<br />Makefile:24: recipe for target '__sub-make' failed<br />make: *</b> [__sub-make] Error 2<br />Command failed.<br />Press any key to continue..._</li>
</ul>
<p>--Sandeep S</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6328#message-63282023-05-02T15:18:56ZJonathan Cormierjcormier@criticallink.com
<p>Wiki has been updated. Thanks for reporting this.</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6327#message-63272023-05-02T15:07:24ZJonathan Cormierjcormier@criticallink.com
<p>Sandeep Sivadas wrote in <a class="message" href="http://support.criticallink.com/redmine/boards/59/topics/6322?r=6326#message-6326">RE: Yocto build for mitySOM AM57x</a>:</p>
<blockquote>
<p>Hi,</p>
<p>Thank you for your support.<br />I have followed the steps in the link you provided. <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X</a></p>
<p>But got some error as shown below.<br /><em><br />_pokyuser@31657297eb91:/work/oe-layersetup/build$ MACHINE=mitysom-am57x bitbake arago-base-tisdk-image<br />Traceback (most recent call last):<br />File "/work/oe-layersetup/sources/bitbake/bin/bitbake", line 31, in <module><br />import bb<br />File "/work/oe-layersetup/sources/bitbake/lib/bb/</em>_init__.py", line 81, in <module><br />import bb.msg<br />File "/work/oe-layersetup/sources/bitbake/lib/bb/msg.py", line 32, in <module><br />import bb.event<br />File "/work/oe-layersetup/sources/bitbake/lib/bb/event.py", line 35, in <module><br />import bb.compat<br />File "/work/oe-layersetup/sources/bitbake/lib/bb/compat.py", line 3, in <module><br />from collections import MutableMapping, KeysView, ValuesView, ItemsView, OrderedDict<br />ImportError: cannot import name 'MutableMapping' from 'collections' (/opt/poky/4.1/sysroots/x86_64-pokysdk-linux/usr/lib/python3.10/collections/__init__.py)__</p>
<p>Kindly look in to it.</p>
<p>Sandeep S</p>
</blockquote>
<p>Hi Sandeep, the crops/poky group decided they needed a newer python, etc in their 18.04 ubuntu image which breaks the older thud build. We can work around this by mounting an empty tmpfs directory over /opt/poky so that the original 18.04 tools will be used.</p>
<p>I will update the wiki to address this.</p>
<p><code>docker run --rm -it -v $PWD:/work -v /home/tools:/home/tools --tmpfs /opt/poky --env "TOOLCHAIN_PATH_ARMV7=/home/tools/mitysom-57x/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf" crops/poky:ubuntu-18.04 --workdir=/work</code></p>
<p>Note there is a docker-poky.sh helper script in sources/meta-mitysom/build/ that can be used to call the "docker run ..." command so you don't have to remember it every time.</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6326#message-63262023-05-02T05:40:45ZSandeep Sivadas
<p>Hi,</p>
<p>Thank you for your support.<br />I have followed the steps in the link you provided. <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X</a></p>
<p>But got some error as shown below.<br /><em><br />_pokyuser@31657297eb91:/work/oe-layersetup/build$ MACHINE=mitysom-am57x bitbake arago-base-tisdk-image<br />Traceback (most recent call last):<br /> File "/work/oe-layersetup/sources/bitbake/bin/bitbake", line 31, in <module><br /> import bb<br /> File "/work/oe-layersetup/sources/bitbake/lib/bb/</em>_init__.py", line 81, in <module><br /> import bb.msg<br /> File "/work/oe-layersetup/sources/bitbake/lib/bb/msg.py", line 32, in <module><br /> import bb.event<br /> File "/work/oe-layersetup/sources/bitbake/lib/bb/event.py", line 35, in <module><br /> import bb.compat<br /> File "/work/oe-layersetup/sources/bitbake/lib/bb/compat.py", line 3, in <module><br /> from collections import MutableMapping, KeysView, ValuesView, ItemsView, OrderedDict<br />ImportError: cannot import name 'MutableMapping' from 'collections' (/opt/poky/4.1/sysroots/x86_64-pokysdk-linux/usr/lib/python3.10/collections/__init__.py)__</p>
<p>Kindly look in to it.</p>
<p>Sandeep S</p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6325#message-63252023-05-01T14:32:03ZJonathan Cormierjcormier@criticallink.com
<p>sandeep Sivadas wrote:</p>
<blockquote>
<p>Hi,</p>
<p>We purchased MitySOM AM572x development kit and trying to build our own yocto linux.<br />Then we have a problem while cloning the branches of mitysom AM57x. <br />While cloning the below git files, it shows as "fatal: unable to access 'https://gitlab.syr.criticallink.com/critical-link/yocto/meta-mitysom.git/': Could not resolve host: gitlab.syr.criticallink.com"</p>
<p>meta-mitysom,<a class="external" href="https://gitlab.syr.criticallink.com/critical-link/yocto/meta-mitysom.git,thud,HEAD,layers=">https://gitlab.syr.criticallink.com/critical-link/yocto/meta-mitysom.git,thud,HEAD,layers=</a></p>
<p>The config file i got from Critical link is attaching here. Kindly look in to it.</p>
</blockquote>
<p>The correct config file is processor-sdk-06.03.00.106-cl-external-config.txt</p>
<p>See <a class="external" href="https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X">https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X</a></p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6324#message-63242023-05-01T13:01:07ZMichael Williamson
<p>Summary repo link:</p>
<p><a class="external" href="https://support.criticallink.com/gitweb/?p=meta-mitysom.git;a=summary">https://support.criticallink.com/gitweb/?p=meta-mitysom.git;a=summary</a></p> Software Development: RE: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/6322?r=6323#message-63232023-05-01T13:00:35ZMichael Williamson
<p>Hi Sandeep,</p>
<p>That repository is mirrored here:</p>
<p><a class="external" href="https://support.criticallink.com/git/meta-mitysom.git">https://support.criticallink.com/git/meta-mitysom.git</a></p>
<p>I think you should be able to update the URL for this repository.</p>
<p>We will look into updating the config file and remove our internal links. Sorry for the inconvenience.</p>
<p>-Mike</p> Software Development: Yocto build for mitySOM AM57xhttp://support.criticallink.com/redmine/boards/59/topics/63222023-05-01T08:38:57ZSandeep Sivadas
<p>Hi,</p>
<p>We purchased MitySOM AM572x development kit and trying to build our own yocto linux.<br />Then we have a problem while cloning the branches of mitysom AM57x. <br />While cloning the below git files, it shows as "fatal: unable to access 'https://gitlab.syr.criticallink.com/critical-link/yocto/meta-mitysom.git/': Could not resolve host: gitlab.syr.criticallink.com"</p>
<p>meta-mitysom,<a class="external" href="https://gitlab.syr.criticallink.com/critical-link/yocto/meta-mitysom.git,thud,HEAD,layers=">https://gitlab.syr.criticallink.com/critical-link/yocto/meta-mitysom.git,thud,HEAD,layers=</a></p>
<p>The config file i got from Critical link is attaching here. Kindly look in to it.</p>
<p>Thanks and regards</p>
<p>Sandeep S</p>