BeagleBone AI-64 issueshttps://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues2023-08-23T12:40:29-04:00https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/53DisplayPort config pins should be weakly pulled down, not grounded2023-08-23T12:40:29-04:00Matthijs van DuinDisplayPort config pins should be weakly pulled down, not groundedThe CONFIG1 and CONFIG2 pins of the DisplayPort connector are currently grounded via 0Ω resistors R308 and R309. However, the DisplayPort specification (I checked v1.1a and v1.2) says these pins "must be weakly pulled down with 1MΩ resis...The CONFIG1 and CONFIG2 pins of the DisplayPort connector are currently grounded via 0Ω resistors R308 and R309. However, the DisplayPort specification (I checked v1.1a and v1.2) says these pins "must be weakly pulled down with 1MΩ resistors". Grounding CONFIG2 in particular may be hazardous since it may be driven high by a downstream device as part of a detection sequence.
Since there are already resistors in the design, this should be fixable with a simple BOM change.https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/52Docs/HW: Add RoHS certificate of compliance2023-02-08T09:59:24-05:00Kevin LeongDocs/HW: Add RoHS certificate of complianceAn environmental certificate of compliance (RoHS and if possible, REACH) of the board assembly (PCB+components) would help a lot to comply to European regulations.An environmental certificate of compliance (RoHS and if possible, REACH) of the board assembly (PCB+components) would help a lot to comply to European regulations.https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/51crash with azurewave wifi2022-11-18T21:30:00-05:00Nishanth Menoncrash with azurewave wifi
When we use https://www.amazon.com/gp/product/B07FMJDK1N
And the default image configuration:
/boot/firmware/extlinux/extlinux.conf contains "quiet" in the append bootargs line, then kernel crashes
example:
```
append root=/dev/mmcbl...
When we use https://www.amazon.com/gp/product/B07FMJDK1N
And the default image configuration:
/boot/firmware/extlinux/extlinux.conf contains "quiet" in the append bootargs line, then kernel crashes
example:
```
append root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0 quiet
```
Workaround: If we drop the quiet keywod to make extlinux.conf, system works fine.
```
append root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0
```
Crash Signature:
```
[ 0.717189] k3-ringacc 2b800000.ringacc: Failed to get MSI domain
[ 0.717228] k3-ringacc 3c000000.ringacc: Failed to get MSI domain
[ 0.717366] debugfs: Directory '31010000.pat' with parent 'regmap' already present!
[ 0.717606] debugfs: Directory '31011000.pat' with parent 'regmap' already present!
[ 0.717738] debugfs: Directory '31012000.pat' with parent 'regmap' already present!
[ 0.717868] debugfs: Directory '31013000.pat' with parent 'regmap' already present!
[ 0.718021] debugfs: Directory '31014000.pat' with parent 'regmap' already present!
[ 0.900250] k3-ringacc 2b800000.ringacc: Failed to get MSI domain
[ 0.900350] k3-ringacc 3c000000.ringacc: Failed to get MSI domain
[ 1.280265] am65-cpsw-nuss c000000.ethernet: /bus@100000/ethernet@c000000/ethernet-ports/port@1 error retrieving port phy: -19
[ 1.639493] j721e-pcie 2910000.pcie: LINK DOWN!
[ 1.639533] SError Interrupt on CPU1, code 0xbf000000 -- SError
[ 1.639534] CPU: 1 PID: 76 Comm: kworker/1:3 Not tainted 5.10.145-ti-arm64-r73 #1bullseye
[ 1.639536] Hardware name: BeagleBoard.org BeagleBone AI-64 (DT)
[ 1.639537] Workqueue: events deferred_probe_work_func
[ 1.639539] pstate: 20000085 (nzCv daIf -PAN -UAO -TCO BTYPE=--)
[ 1.639540] pc : pci_generic_config_read+0x3c/0xe0
[ 1.639541] lr : pci_generic_config_read+0x24/0xe0
[ 1.639542] sp : ffff8000122e3750
[ 1.639543] x29: ffff8000122e3750 x28: ffff00081507c800
[ 1.639545] x27: 0000000000000001 x26: 0000000000000000
[ 1.639547] x25: ffff00081507b0e8 x24: 0000000000000000
[ 1.639549] x23: 0000000000000000 x22: 0000000000000000
[ 1.639551] x21: ffff8000122e3864 x20: 0000000000000004
[ 1.639553] x19: ffff8000122e37c4 x18: 00000000fffffffb
[ 1.639555] x17: 000000005c365dd1 x16: 000000008fa6af27
[ 1.639557] x15: 0000000000000020 x14: ffffffffffffffff
[ 1.639559] x13: ffff0008147ada1c x12: ffff0008147ad29a
[ 1.639561] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
[ 1.639563] x9 : 6b622c7265717361 x8 : 0000000000000757
[ 1.639565] x7 : ffff8000122e37a0 x6 : 0000000000000000
[ 1.639567] x5 : ffff00081507c800 x4 : 000000000000000b
[ 1.639570] x3 : 0000000000000001 x2 : ffff800017400008
[ 1.639572] x1 : 0000000000000000 x0 : ffff800012208000
[ 1.639574] Kernel panic - not syncing: Asynchronous SError Interrupt
[ 1.773832] SMP: stopping secondary CPUs
[ 1.773833] Kernel Offset: disabled
[ 1.773834] CPU features: 0x08240022,20006008
[ 1.773835] Memory Limit: none
```https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/50kernel-based IMX219 camera support2023-04-17T15:18:41-04:00Jason Kridnerkernel-based IMX219 camera supportWe need non-GStreamer, V4L2-based Pi-camera support. Using GStreamer is not a good solution for Beagle.We need non-GStreamer, V4L2-based Pi-camera support. Using GStreamer is not a good solution for Beagle.Andrei AldeaAndrei Aldeahttps://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/49window manager does not startup if DP is connected after system boot is complete2022-11-01T13:52:33-04:00Nishanth Menonwindow manager does not startup if DP is connected after system boot is completeIf the DP cable is plugged into the system after the system has completed bootup, window manager does'nt come up.
Based on discussion with Robert, looks like lightdm.service is not restarted
Workaround:
```
sudo systemctl restart light...If the DP cable is plugged into the system after the system has completed bootup, window manager does'nt come up.
Based on discussion with Robert, looks like lightdm.service is not restarted
Workaround:
```
sudo systemctl restart lightdm.service
```Robert NelsonRobert Nelsonhttps://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/48Possible Device Manager (TISCI server) crash Locks up system2022-11-02T22:37:33-04:00Nishanth MenonPossible Device Manager (TISCI server) crash Locks up system* Board SN: 202208 000230 (no display or peripherals connected)
* Log: [a.txt](/uploads/39e73b96aa5bcc91782cda061e39282a/a.txt)
* Fail frequency seen 1 in 1000 cold boots at this point.
```
Starting Hold until boot process fini...* Board SN: 202208 000230 (no display or peripherals connected)
* Log: [a.txt](/uploads/39e73b96aa5bcc91782cda061e39282a/a.txt)
* Fail frequency seen 1 in 1000 cold boots at this point.
```
Starting Hold until boot process finishes up...
[ 22.498073] Mass Storage Function, version: 2009/09/11
[ 22.503275] LUN: removable file: (no medium)
[ 22.511863] ti-sci 44083000.dmsc: Mbox timedout in resp(caller: ti_sci_cmd_get_device_exclusive+0x18/0x2c)
[ 22.521549] ti-sci 44083000.dmsc: Mbox send fail -110
[ 22.526650] pvrsrvkm 4e20000000.gpu: adding gpu_0 device link failed!
ERROR: Unhandled External Abort received on 0x80000001 from S-EL1
ERROR: exception reason=0 syndrome=0xbf000000
Unhandled Exception from EL1
x0 = 0xffff800014a80000
x1 = 0x0000000000000000
x2 = 0x0000000000000000
x3 = 0xffff800009352018
x4 = 0x0000000000000000
x5 = 0x0000000000000000
x6 = 0xffff8000130f35e7
```
Note:
```
[ 22.511863] ti-sci 44083000.dmsc: Mbox timedout in resp(caller: ti_sci_cmd_get_device_exclusive+0x18/0x2c)
[ 22.521549] ti-sci 44083000.dmsc: Mbox send fail -110
```
Seems to indicate DM has gone non-operational for some reason.. in the get_device call
```
[ 22.526650] pvrsrvkm 4e20000000.gpu: adding gpu_0 device link failed!
```
Seems to indicate this is around the GPU - power domain failed to attach for some reason.
Another signature as indicated by @BaozhuZuo in the comments includes:
```
[ 13.027250] ti-sci 44083000.dmsc: Mbox timedout in resp(caller: k3_ringacc_ring_reset_sci+0x68/0xb4)
[ 13.036498] ti-sci 44083000.dmsc: RM_RA:Mbox config send fail -110
[ 13.036504] k3-ringacc 3c000000.ringacc: TISCI reset ring fail (-110) ring_idx 367
[ 13.055483] ti-udma 31150000.dma-controller: flow68 config failed: -22
[ 13.055538] SError Interrupt on CPU0, code 0xbf000002 -- SError
[ 13.055539] CPU: 0 PID: 426 Comm: systemd-udevd Tainted: G C O 5.10.120-ti-arm64-r66 #1bullseye
```
This could indicate the behavior is linked to the DMA operations around pdma too.https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/47Random System lockup during kernel bootup.2022-11-01T09:21:01-04:00Nishanth MenonRandom System lockup during kernel bootup.This is probably impacting ALL boards. Rigorous testing done on:
* SN: 202208 000208 - Connected to 1080p DP display + USB + Ethernet
* SN: 202208 000230 - no peripherals connected
Test case involves cold booting this board with edge AI...This is probably impacting ALL boards. Rigorous testing done on:
* SN: 202208 000208 - Connected to 1080p DP display + USB + Ethernet
* SN: 202208 000230 - no peripherals connected
Test case involves cold booting this board with edge AI image + DDR configuration set to : LPDDR4 3200 Kingston DDR configuration with SK IO latencies + wrDBI enabled.
Fail rate so far:
* board-208: 62 out of 1000 cold boots. [board-208.tar.xz](/uploads/46931fdec70ccf0545ad551817d468f0/board-208.tar.xz)
* board-230: 32 out of 1000 cold boots. [board-230.tar.xz](/uploads/1992f09b9b31d645fa4000daae86c2a9/board-230.tar.xz)
~9-10% failure rate (if we average the above two).
Failure signature:
Default image:
```
[ 9.479074] platform 5d00000.r5f: configured R5F for remoteproc mode
[ 9.521241] platform 5e00000.r5f: configured R5F for remoteproc mode
[ 9.535493] remoteproc remoteproc18: request_firmware failed: -2
[ 9.543669] platform 5f00000.r5f: configured R5F for remoteproc mode
[ 9.555368] remoteproc remoteproc19: request_firmware failed: -2
```
With debug logs enabled:
```
[ 12.356772] remoteproc remoteproc17: 5d00000.r5f is available
[ 12.377568] platform 5e00000.r5f: configured R5F for remoteproc mode
[ 12.443393] platform 5e00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a6000000
[ 12.489328] remoteproc remoteproc17: powering up 5d00000.r5f
[ 12.495020] remoteproc remoteproc17: Booting fw image vision_apps_eaik/vx_app_rtos_linux_mcu2_1.out, size 297932
[ 12.514298] remoteproc remoteproc18: 5e00000.r5f is available
[ 12.520457] remoteproc remoteproc18: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
[ 12.529658] remoteproc remoteproc18: powering up 5e00000.r5f
[ 12.535356] remoteproc remoteproc18: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
[ 12.544526] remoteproc remoteproc18: request_firmware failed: -2
[ 12.550716] remoteproc remoteproc16: powering up 5c00000.r5f
[ 12.556415] remoteproc remoteproc16: Booting fw image vision_apps_eaik/vx_app_rtos_linux_mcu2_0.out, size 572788
[ 12.557703] platform 5f00000.r5f: configured R5F for remoteproc mode'
```
In this scenario - the Linux heartbeat LED stops blinking (either on or off), display (if connected will freezeup) etc.https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/46R5 SPL: Timeout during frequency handshake2022-10-27T11:35:07-04:00Nishanth MenonR5 SPL: Timeout during frequency handshake6 / 1500 boards in production floor consistently show "Timeout during frequency handshake"
Kingston DDR on all production boards.
SN 202208 001462 falls in this category (shipped to Jason).
This ticket tracks this specific issue.
```
U-...6 / 1500 boards in production floor consistently show "Timeout during frequency handshake"
Kingston DDR on all production boards.
SN 202208 001462 falls in this category (shipped to Jason).
This ticket tracks this specific issue.
```
U-Boot SPL 2021.01-00015-gf158702edf4b (Oct 25 2022 - 18:38:17 -0500)
Model: BeagleBoard.org BeagleBone AI-64 R5 NM-LP4-3200-SK-wrDBI
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -1
Board: J721EX-PM1-SOM rev E2
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.1--v08.04.01 (Jolly Jellyfi')
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -1
Timeout during frequency handshake
### ERROR ### Please RESET the board ###
U-Boot SPL 2021.01-00015-gf158702edf4b (Oct 25 2022 - 18:38:17 -0500)
Model: BeagleBoard.org BeagleBone AI-64 R5 NM-LP4-3200-SK-wrDBI
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -1
Board: J721EX-PM1-SOM rev E2
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.1--v08.04.01 (Jolly Jellyfi')
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -1
Timeout during frequency handshake
### ERROR ### Please RESET the board ###
```
e2e.ti.com https://e2e.ti.com/search?q=%22timeout%20during%20frequency%20handshake%22&category=forum -> there seems to be others who seem to have managed by slowing the DDR down - we seem to have tried the same as well, without success.https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/45HW: Missing 3D CAD model2022-10-27T11:29:01-04:00Kevin LeongHW: Missing 3D CAD modelHaving the 3D CAD model of the BBAI-64 **(heatsink included)** would be very helpful for mechanical integration.Having the 3D CAD model of the BBAI-64 **(heatsink included)** would be very helpful for mechanical integration.https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/44Docs: references to docs needs to be moved2022-10-24T09:26:41-04:00Jason KridnerDocs: references to docs needs to be movedDocs should all be referenced at https://docs.beagleboard.org.Docs should all be referenced at https://docs.beagleboard.org.https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/43SW: need better user feedback on flasher2022-06-17T00:28:02-04:00Jason KridnerSW: need better user feedback on flasherdisplay needs to come on and indicate progress.
maybe USR4 could flash faster and faster?display needs to come on and indicate progress.
maybe USR4 could flash faster and faster?Jason KridnerJason Kridnerhttps://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/42Docs: clarify when barrel jack is needed along with Type-C connection2022-08-28T15:04:33-04:00Jason KridnerDocs: clarify when barrel jack is needed along with Type-C connectionSee https://twitter.com/_dcd/status/1537098368442175488
![image](/uploads/fbda6dc055d1bd574a13b153a097e799/image.png)See https://twitter.com/_dcd/status/1537098368442175488
![image](/uploads/fbda6dc055d1bd574a13b153a097e799/image.png)Deepak KhatriDeepak Khatrihttps://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/41Docs: Type-C shouldn't be referred to as supporting host mode2022-06-15T10:34:21-04:00Jason KridnerDocs: Type-C shouldn't be referred to as supporting host mode```
•zmatt>
jkridner: it may be better to not call the type-C port "dual role" given that it doesn't actually support host role (as previously discussed) .. and it doesn't really need it anyway since there are two usb 3 type-A ports
10:...```
•zmatt>
jkridner: it may be better to not call the type-C port "dual role" given that it doesn't actually support host role (as previously discussed) .. and it doesn't really need it anyway since there are two usb 3 type-A ports
10:28 AM
in de board features list I mean
10:28 AM
*in the
10:29 AM <jkridner> Jason Kridner
sure, but it can work with some hubs as a host. Suggesting just calling it a client port?
10:29 AM <•zmatt>
those hubs are in violation of the usb s[ec
10:29 AM
*spec
10:30 AM <jkridner> Jason Kridner
removed Host from https://beagleboard.org/boards/
10:30 AM <•zmatt>
but yeah, device port or peripheral port
10:31 AM
— jkridner wishes lorforlinux logged into IRC so I can pawn off the update to the SRM.
10:31 AM <•zmatt>
host role requires either being a power source or a type-c controller that supports data role swap
10:31 AM <jkridner> Jason Kridner
documentation pull requests to git.beagleboard.org/beagleboard/beaglebone-ai-64 are *welcome*!
10:32 AM
right. we'd need a hub that starts in the wrong data role.
10:33 AM <•zmatt>
yep, the hub would need to act in peripheral role even though host role was negotiated for it
```https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/40The power of external connector(such as CSI DSI M.2) should be turned off by ...2022-06-13T17:34:16-04:00Jason KridnerThe power of external connector(such as CSI DSI M.2) should be turned off by PMIC*Created by: JunqingXin*
@jadonk Jason, should we turn off the power of external connector(such as CSI, DSI, M.2, P8 P9, mikroBUS Header) by PMIC when the board power down by software? the power of CSI/DSI/M.2 connector connected to "VS...*Created by: JunqingXin*
@jadonk Jason, should we turn off the power of external connector(such as CSI, DSI, M.2, P8 P9, mikroBUS Header) by PMIC when the board power down by software? the power of CSI/DSI/M.2 connector connected to "VSYS_3V3" in first prototype which is the same as TI's demo, but I think it should be tied to "VSYS_IO_3V3", so the power can be turned off by GPIO "EN_3V3IO_LDSW" of PMIC.
By the way, have you tested the POWER ON/OFF BUTTON SW2? it needs driver to control.
![image](https://user-images.githubusercontent.com/90748281/137881701-37484660-fcd9-4a34-a253-2588e433e58e.png)
![image](https://user-images.githubusercontent.com/90748281/137881840-1fb52301-a92d-4339-b300-6b14ba5fd356.png)https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/39PCIe can not support 5Gbps when using TDA4 internal clock. Should change DTS ...2022-06-13T17:34:16-04:00Jason KridnerPCIe can not support 5Gbps when using TDA4 internal clock. Should change DTS to let 5.0G module works at 2.4G.*Created by: FionaYu20180326*
![image](https://user-images.githubusercontent.com/43629663/138671566-970c529e-fe53-4e42-9594-8c09fd92e1f3.png)*Created by: FionaYu20180326*
![image](https://user-images.githubusercontent.com/43629663/138671566-970c529e-fe53-4e42-9594-8c09fd92e1f3.png)https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/38eMMC mmc-utils bits need for flasher:2022-06-13T18:22:56-04:00Jason KridnereMMC mmc-utils bits need for flasher:*Created by: RobertCNelson*
Linux Dump:
```
sudo mmc extcsd read /dev/mmcblk0
```
U-Boot
```
"emmc_boot0_bbai=mmc partconf 0 1 1 1; " \
"mmc dev 0 1; " \
"mmc erase 0 0x2400; " \
"fatload mmc 1 ${loadaddr} tiboot3.bi...*Created by: RobertCNelson*
Linux Dump:
```
sudo mmc extcsd read /dev/mmcblk0
```
U-Boot
```
"emmc_boot0_bbai=mmc partconf 0 1 1 1; " \
"mmc dev 0 1; " \
"mmc erase 0 0x2400; " \
"fatload mmc 1 ${loadaddr} tiboot3.bin; " \
"mmc write ${loadaddr} 0x0 0x300; " \
"fatload mmc 1 ${loadaddr} tispl.bin; " \
"mmc write ${loadaddr} 0x300 0x600; " \
"fatload mmc 1 ${loadaddr} u-boot.img; " \
"mmc write ${loadaddr} 0x900 0x1000; " \
"fatload mmc 1 ${loadaddr} sysfw.itb; " \
"mmc write ${loadaddr} 0x1900 0x300; " \
"mmc bootbus 0 2 0 0; " \
"\0" \
```
Files:
Unlock:
Linux:
```
echo 0 > /sys/class/block/mmcblk0boot0/force_ro
sudo sh -c "echo '0' >> /sys/class/block/mmcblk0boot0/force_ro"
```
boot bus:
Linux:
```
sudo mmc bootpart enable 1 2 /dev/mmcblk0
```
```
Boot configuration bytes [PARTITION_CONFIG: 0x48]
Boot Partition 1 enabled
No access to boot partition
Boot config protection [BOOT_CONFIG_PROT: 0x00]
Boot bus Conditions [BOOT_BUS_CONDITIONS: 0x02]
```
U-Boot
```
mmc bootbus 0 2 0 0
```
```
Boot configuration bytes [PARTITION_CONFIG: 0x48]
Boot Partition 1 enabled
No access to boot partition
Boot config protection [BOOT_CONFIG_PROT: 0x00]
Boot bus Conditions [BOOT_BUS_CONDITIONS: 0x02]
```
H/W Reset:
Linux
```
sudo mmc hwreset enable /dev/mmcblk0
```
U-boot
```
mmc rst-function 0 1
```
mmc-utils:
```
H/W reset function [RST_N_FUNCTION]: 0x00
```
```
H/W reset function [RST_N_FUNCTION]: 0x01
```
Hacks:
```
dd if=/dev/mmcblk0boot0 of=/home/debian/u-boot.img count=32 bs=128k
dd if=/dev/zero of=/dev/mmcblk0boot0 count=32 bs=128k
dd if=/boot/firmware/tiboot3.bin of=/dev/mmcblk0boot0 count=3 bs=128k
"fatload mmc 1 ${loadaddr} tispl.bin; " \
"mmc write ${loadaddr} 0x300 0x600; "
dd if=/boot/firmware/tispl.bin of=/dev/mmcblk0boot0 seek=3 count=3 bs=128k
"fatload mmc 1 ${loadaddr} u-boot.img; " \
"mmc write ${loadaddr} 0x900 0x1000; " \
dd if=/boot/firmware/u-boot.img of=/dev/mmcblk0boot0 seek=9 count=10 bs=128k
"fatload mmc 1 ${loadaddr} sysfw.itb; " \
"mmc write ${loadaddr} 0x1900 0x300; " \
dd if=/boot/firmware/sysfw.itb of=/dev/mmcblk0boot0 seek=19 count=3 bs=128k
dd if=/dev/mmcblk0boot0 of=/home/debian/linux.img count=32 bs=128k
```https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/37SW: power on/off by button press2022-06-13T18:26:51-04:00Jason KridnerSW: power on/off by button press*Created by: jadonk*
Software is not implemented*Created by: jadonk*
Software is not implementedhttps://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/36X3 22.5792MHz Crystal is DNP on TI EVB. We need to find if ai-64 can also DNP...2022-06-13T18:22:56-04:00Jason KridnerX3 22.5792MHz Crystal is DNP on TI EVB. We need to find if ai-64 can also DNP this part.*Created by: FionaYu20180326*
![捕获](https://user-images.githubusercontent.com/43629663/138071040-6f658ac6-542f-4169-bd84-cc03d01f683a.PNG)*Created by: FionaYu20180326*
![捕获](https://user-images.githubusercontent.com/43629663/138071040-6f658ac6-542f-4169-bd84-cc03d01f683a.PNG)https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/35SW: Get EDGE AI SDK and Robotics SDK demos running2022-06-13T17:34:15-04:00Jason KridnerSW: Get EDGE AI SDK and Robotics SDK demos running*Created by: jadonk*
Robotics: https://software-dl.ti.com/jacinto7/esd/robotics-sdk/00_05_00_05/docs/index.html
Edge: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-sk-tda4vm/08_00_01_10/exports/docs/index.html*Created by: jadonk*
Robotics: https://software-dl.ti.com/jacinto7/esd/robotics-sdk/00_05_00_05/docs/index.html
Edge: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-sk-tda4vm/08_00_01_10/exports/docs/index.htmlhttps://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/34SW: regression with USB HS hub not showing up2022-06-13T18:22:56-04:00Jason KridnerSW: regression with USB HS hub not showing up*Created by: jadonk*
Logitech USB camera plugged into top USB
Sandisk USB thumb drive plugged into bottom USB
```
debian@BeagleBone:/opt/source/dtb-5.10-ti-arm64$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5...*Created by: jadonk*
Logitech USB camera plugged into top USB
Sandisk USB thumb drive plugged into bottom USB
```
debian@BeagleBone:/opt/source/dtb-5.10-ti-arm64$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
```
```
debian@BeagleBone:/opt/source/dtb-5.10-ti-arm64$ sudo beagle-version
[sudo] password for debian:
eeprom:[BBONEAI-64-B0-B0007801B00001640322BBBBBB0041]
model:[BeagleBoard.org_BeagleBone_AI-64]
dogtag:[BeagleBoard.org Debian Bullseye Xfce Image 2022-01-14]
UBOOT: Booted Device-Tree:[k3-j721e-beagleboneai64.dts]
kernel:[5.10.100-ti-arm64-r37]
nodejs:[v12.22.5]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
WARNING:pkg:[bb-cape-overlays]:[NOT_INSTALLED]
pkg:[bb-customizations]:[1.20220119.0-0~bullseye+20220119]
pkg:[bb-usb-gadgets]:[1.20220113.1-0~bullseye+20220113]
WARNING:pkg:[bb-wl18xx-firmware]:[NOT_INSTALLED]
pkg:[kmod]:[28-1]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
pkg:[firmware-ti-connectivity]:[20210315-3]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal input bluetooth netdev gpio docker admin tisdk weston-launch cloud9ide]
cmdline:[console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0]
dmesg | grep remote
[ 6.965085] remoteproc remoteproc0: b034000.pru is available
[ 6.985050] remoteproc remoteproc1: b004000.rtu is available
[ 6.994317] remoteproc remoteproc2: b00a000.txpru is available
[ 7.000592] remoteproc remoteproc3: b038000.pru is available
[ 7.006756] remoteproc remoteproc4: b006000.rtu is available
[ 7.012932] remoteproc remoteproc5: b00c000.txpru is available
[ 7.019197] remoteproc remoteproc6: b134000.pru is available
[ 7.025353] remoteproc remoteproc7: b104000.rtu is available
[ 7.031525] remoteproc remoteproc8: b10a000.txpru is available
[ 7.037755] remoteproc remoteproc9: b138000.pru is available
[ 7.043879] remoteproc remoteproc10: b106000.rtu is available
[ 7.050160] remoteproc remoteproc11: b10c000.txpru is available
[ 9.753842] k3-dsp-rproc 4d80800000.dsp: configured DSP for remoteproc mode
[ 9.842370] remoteproc remoteproc12: 4d80800000.dsp is available
[ 9.977316] k3-dsp-rproc 4d81800000.dsp: configured DSP for remoteproc mode
[ 10.012197] remoteproc remoteproc12: powering up 4d80800000.dsp
[ 10.018664] remoteproc remoteproc12: Booting fw image vision_apps_eaik/vx_app_rtos_linux_c6x_1.out, size 1436436
[ 10.067264] remoteproc12#vdev0buffer: assigned reserved memory node vision-apps-c66-dma-memory@a9000000
[ 10.080481] remoteproc remoteproc13: 4d81800000.dsp is available
[ 10.088384] remoteproc12#vdev0buffer: registered virtio0 (type 7)
[ 10.103142] remoteproc remoteproc12: remote processor 4d80800000.dsp is now up
[ 10.178701] remoteproc remoteproc13: powering up 4d81800000.dsp
[ 10.190808] remoteproc remoteproc13: Booting fw image vision_apps_eaik/vx_app_rtos_linux_c6x_2.out, size 1436436
[ 10.221515] remoteproc13#vdev0buffer: assigned reserved memory node vision-apps-c66-dma-memory@a8000000
[ 10.236260] remoteproc13#vdev0buffer: registered virtio1 (type 7)
[ 10.246168] remoteproc remoteproc13: remote processor 4d81800000.dsp is now up
[ 10.365412] k3-dsp-rproc 64800000.dsp: configured DSP for remoteproc mode
[ 10.375671] remoteproc remoteproc14: 64800000.dsp is available
[ 10.483082] remoteproc remoteproc14: powering up 64800000.dsp
[ 10.488860] remoteproc remoteproc14: Booting fw image vision_apps_eaik/vx_app_rtos_linux_c7x_1.out, size 12980288
[ 10.522159] remoteproc remoteproc14: unsupported resource 65538
[ 10.556446] remoteproc14#vdev0buffer: assigned reserved memory node vision-apps-c71-dma-memory@aa000000
[ 10.576535] remoteproc14#vdev0buffer: registered virtio2 (type 7)
[ 10.582829] remoteproc remoteproc14: remote processor 64800000.dsp is now up
[ 10.583552] remoteproc remoteproc15: 41000000.r5f is available
[ 10.716854] remoteproc remoteproc15: attaching to 41000000.r5f
[ 10.756672] remoteproc15#vdev0buffer: assigned reserved memory node vision-apps-r5f-dma-memory@a0000000
[ 10.773568] remoteproc15#vdev0buffer: registered virtio3 (type 7)
[ 10.783290] remoteproc remoteproc15: remote processor 41000000.r5f is now attached
[ 10.794869] platform 5c00000.r5f: configured R5F for remoteproc mode
[ 10.820507] remoteproc remoteproc16: 5c00000.r5f is available
[ 10.837323] remoteproc remoteproc16: powering up 5c00000.r5f
[ 10.843265] remoteproc remoteproc16: Booting fw image vision_apps_eaik/vx_app_rtos_linux_mcu2_0.out, size 568692
[ 10.861061] platform 5d00000.r5f: configured R5F for remoteproc mode
[ 10.863853] remoteproc16#vdev0buffer: assigned reserved memory node vision-apps-r5f-dma-memory@a2000000
[ 10.879371] remoteproc16#vdev0buffer: registered virtio4 (type 7)
[ 10.885632] remoteproc remoteproc16: remote processor 5c00000.r5f is now up
[ 10.996196] remoteproc remoteproc17: 5d00000.r5f is available
[ 11.005760] remoteproc remoteproc17: powering up 5d00000.r5f
[ 11.012234] remoteproc remoteproc17: Booting fw image vision_apps_eaik/vx_app_rtos_linux_mcu2_1.out, size 301996
[ 11.029085] remoteproc17#vdev0buffer: assigned reserved memory node vision-apps-r5f-dma-memory@a4000000
[ 11.045584] remoteproc17#vdev0buffer: registered virtio5 (type 7)
[ 11.051806] remoteproc remoteproc17: remote processor 5d00000.r5f is now up
[ 11.059314] platform 5e00000.r5f: configured R5F for remoteproc mode
[ 11.076375] remoteproc remoteproc18: 5e00000.r5f is available
[ 11.082340] remoteproc remoteproc18: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
[ 11.091578] remoteproc remoteproc18: powering up 5e00000.r5f
[ 11.098011] remoteproc remoteproc18: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
[ 11.107731] remoteproc remoteproc18: request_firmware failed: -2
[ 11.114433] platform 5f00000.r5f: configured R5F for remoteproc mode
[ 11.132255] remoteproc remoteproc19: 5f00000.r5f is available
[ 11.138937] remoteproc remoteproc19: Direct firmware load for j7-main-r5f1_1-fw failed with error -2
[ 11.149430] remoteproc remoteproc19: powering up 5f00000.r5f
[ 11.155941] remoteproc remoteproc19: Direct firmware load for j7-main-r5f1_1-fw failed with error -2
[ 11.165825] remoteproc remoteproc19: request_firmware failed: -2
dmesg | grep pru
[ 6.965085] remoteproc remoteproc0: b034000.pru is available
[ 6.994317] remoteproc remoteproc2: b00a000.txpru is available
[ 7.000592] remoteproc remoteproc3: b038000.pru is available
[ 7.012932] remoteproc remoteproc5: b00c000.txpru is available
[ 7.019197] remoteproc remoteproc6: b134000.pru is available
[ 7.031525] remoteproc remoteproc8: b10a000.txpru is available
[ 7.037755] remoteproc remoteproc9: b138000.pru is available
[ 7.050160] remoteproc remoteproc11: b10c000.txpru is available
dmesg | grep pinctrl-single
[ 1.396735] pinctrl-single 4301c000.pinctrl: 94 pins, size 376
[ 1.402986] pinctrl-single 11c000.pinctrl: 173 pins, size 692
dmesg | grep gpio-of-helper
lsusb
Bus 002 Device 003: ID 0781:5581 SanDisk Corp. Ultra
Bus 002 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
```
dmesg log: https://paste.debian.net/1232183/