BeagleBone AI-64 issueshttps://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues2022-11-18T21:30:00-05:00https://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/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/1Docs: Board EEPROM content definition2022-06-13T17:34:09-04:00Jason KridnerDocs: Board EEPROM content definition*Created by: RobertCNelson*
Prototype has:
```
0000: aa 55 33 ee 01 37 00 10 2e 00 4a 37 32 31 45 58 .U3..7....J721EX
0010: 2d 50 4d 32 2d 53 4f 4d 00 00 45 38 30 30 37 38 -PM2-SOM..E80078
0020: 30 31 45 38 00 00 30 31 30 31 32 3...*Created by: RobertCNelson*
Prototype has:
```
0000: aa 55 33 ee 01 37 00 10 2e 00 4a 37 32 31 45 58 .U3..7....J721EX
0010: 2d 50 4d 32 2d 53 4f 4d 00 00 45 38 30 30 37 38 -PM2-SOM..E80078
0020: 30 31 45 38 00 00 30 31 30 31 32 33 32 31 00 00 01E8..01012321..
0030: 00 00 00 00 30 31 37 39 11 02 00 60 7d fe ff ff ....0179...`}...
````
at a minimal, need replacement for:
J721EX-PM2-SOM section
Requirements:
```
char name[AM6_EEPROM_HDR_NAME_LEN];
char version[AM6_EEPROM_HDR_VERSION_LEN];
char proc_number[AM6_EEPROM_HDR_PROC_NR_LEN];
char variant[AM6_EEPROM_HDR_VARIANT_LEN];
char pcb_revision[AM6_EEPROM_HDR_PCB_REV_LEN];
char schematic_bom_revision[AM6_EEPROM_HDR_SCH_BOM_REV_LEN];
char software_revision[AM6_EEPROM_HDR_SW_REV_LEN];
char vendor_id[AM6_EEPROM_HDR_VID_LEN];
char build_week[AM6_EEPROM_HDR_BLD_WK_LEN];
char build_year[AM6_EEPROM_HDR_BLD_YR_LEN];
char board_4p_number[AM6_EEPROM_HDR_4P_NR_LEN];
char serial[AM6_EEPROM_HDR_SERIAL_LEN];
```
https://github.com/beagleboard/u-boot/blob/v2021.01-ti-08.00.00.004/board/ti/j721e/evm.c#L29-L38
https://github.com/beagleboard/u-boot/blob/v2021.01-ti-08.00.00.004/board/ti/common/board_detect.h#L84-L97https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/3Docs: Documentation: Development Repos for: Linux and U-Boot2022-06-13T17:34:09-04:00Jason KridnerDocs: Documentation: Development Repos for: Linux and U-Boot*Created by: RobertCNelson*
u-boot, following TI's repo: https://git.ti.com/gitweb?p=ti-u-boot/ti-u-boot.git;a=summary
OURS: https://github.com/BeagleBoard/u-boot/tree/v2021.01-ti-08.00.00.004
kernel, following TI's repo: https://git....*Created by: RobertCNelson*
u-boot, following TI's repo: https://git.ti.com/gitweb?p=ti-u-boot/ti-u-boot.git;a=summary
OURS: https://github.com/BeagleBoard/u-boot/tree/v2021.01-ti-08.00.00.004
kernel, following TI's repo: https://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-5.10.y
OURS: https://github.com/beagleboard/linux/tree/5.10-arm64
Device Tree & Overlays: https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v5.10.x-ti-arm64https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/17Docs: How to use DSI2022-06-13T17:34:12-04:00Jason KridnerDocs: How to use DSI*Created by: mingzhangqun*
DSI does not work.*Created by: mingzhangqun*
DSI does not work.https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/7Docs: Include accessories2022-06-13T17:34:10-04:00Jason KridnerDocs: Include accessories*Created by: jadonk*
* Include active mini-DP to HDMI adapter
* Include 2x serial FTDI adapters
* Include 2x CSI to 15 pin ribbon cables for Pi camera
* Include DSI ribbon cable for Seeed DSI panel
* Include USB type-C to type-C cable
...*Created by: jadonk*
* Include active mini-DP to HDMI adapter
* Include 2x serial FTDI adapters
* Include 2x CSI to 15 pin ribbon cables for Pi camera
* Include DSI ribbon cable for Seeed DSI panel
* Include USB type-C to type-C cable
Alternatively, package a kit with all of the above.https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/issues/31Docs: Jtag is functional (openocd)2022-06-13T17:34:14-04:00Jason KridnerDocs: Jtag is functional (openocd)*Created by: nmenon*
Lauterbach: using lauterbach cpu->systemsettings -> detect -> should be able to probe and get the jtag ID.
https://www.tag-connect.com/product/tc2050-idc-nl-10-pin-no-legs-cable-with-ribbon-connector
+
https://www....*Created by: nmenon*
Lauterbach: using lauterbach cpu->systemsettings -> detect -> should be able to probe and get the jtag ID.
https://www.tag-connect.com/product/tc2050-idc-nl-10-pin-no-legs-cable-with-ribbon-connector
+
https://www.tag-connect.com/product/tc2050-clip-3pack-retaining-clip
+
https://www.tag-connect.com/product/tc2050-arm2010-arm-20-pin-to-tc2050-adapter
- do not forget to solderbridge trst.
![image](https://user-images.githubusercontent.com/22279/137637311-6bde5a28-a121-472a-a048-294ec8ae0382.png)
+ debugger of choice. (openocd)
https://www.diygadget.com/jtag-cables-and-microcontroller-programmers/tiao-usb-multi-protocol-adapter-jtag-spi-i2c-serial
-
```
# BBAI64
# I use TUMPA: http://www.tiaowiki.com/w/TIAO_USB_Multi_Protocol_Adapter_User's_Manual
# https://www.diygadget.com/jtag-cables-and-microcontroller-programmers/tiao-usb-multi-protocol-adapter-jtag-spi-i2c-serial
source [find interface/ftdi/tumpa.cfg]
transport select jtag
# default JTAG configuration has only SRST and no TRST
reset_config srst_only srst_push_pull
# delay after SRST goes inactive
adapter srst delay 20
if { ![info exists SOC] } {
set SOC j721e
}
source [find target/ti_k3.cfg]
ftdi tdo_sample_edge falling
# Speeds for FT2232H are in multiples of 2, and 32MHz is tops
# max speed we seem to achieve with BB-AI64 is ~20MHz.. so we pick 16MHz
adapter speed 16000
```
OR
lauterbach, etc..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/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/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/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/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/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/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/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/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/30SW: Need QEP demo2022-06-13T18:27:21-04:00Jason KridnerSW: Need QEP demo*Created by: jadonk*
See https://github.com/beagleboard/robotics-cape/issues/19
Personally, I'm having some problems with my encoder hardware still to verify. I've got the code integrated:
* [Kernel patch](https://github.com/beagleboar...*Created by: jadonk*
See https://github.com/beagleboard/robotics-cape/issues/19
Personally, I'm having some problems with my encoder hardware still to verify. I've got the code integrated:
* [Kernel patch](https://github.com/beagleboard/linux/commit/53a02ea4ff2967687f5dabe9d4bb4aa1e4f5e4ca)
* [Device tree overlay](https://github.com/jadonk/BeagleBoard-DeviceTrees/blob/robotics-cape/src/arm64/overlays/robotics-cape.dts#L147-L183)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/33SW: Watchdog is not implemented.2022-06-13T18:26:32-04:00Jason KridnerSW: Watchdog is not implemented.*Created by: FionaYu20180326**Created by: FionaYu20180326*