· /TestSupport.c

(-2, +2)

| History

| Source

| Diff

]]> Mon, 09 Mar 2026 14:03:37 -0700 Dara Navaei https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3605-2 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3605-2 Dara Navaei Closed LEAHI-DD-FIRMWARE-LDT-3605-2 ]]> Mon, 09 Mar 2026 13:53:27 -0700 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3605-2 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3605-2 Sean Nash and Vendor - TEL - Jashwant Gantyada finished reviewing LEAHI-DD-FIRMWARE-LDT-3605-2 LEAHI-DD-FIRMWARE-LDT-3605_(DD) BLD sensor intermittently does not read for B2.0 HW ]]> Mon, 09 Mar 2026 13:24:47 -0700 Dara Navaei https://devapps.diality.us/changelog/leahi-fwcommon?cs=9ca22b5254ff1d2261a7cceabfff1d74b56b45eb https://devapps.diality.us/changelog/leahi-fwcommon?cs=9ca22b5254ff1d2261a7cceabfff1d74b56b45eb Dara Navaei committed 9ca22b5 on branch LDT-1195-dd-is-balancing-chamber-switching, LDT-1415-pressures-monitoring-td-baro and 22 more in leahi-fwcommon LDT-3605 updated the test support module

· /TestSupport.c

(-1, +1)

| History

| Source

| Diff

]]> Sat, 07 Mar 2026 15:22:36 -0800 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3605-2 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3605-2 Dara Navaei added Vendor - TEL - Jashwant Gantyada to LEAHI-DD-FIRMWARE-LDT-3605-2 LEAHI-DD-FIRMWARE-LDT-3605_(DD) BLD sensor intermittently does not read for B2.0 HW ]]> Sat, 07 Mar 2026 15:09:02 -0800 Dara Navaei https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3605-2 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3605-2 Dara Navaei started review LEAHI-DD-FIRMWARE-LDT-3605-2 ]]> Sat, 07 Mar 2026 15:03:44 -0800 Dara Navaei https://devapps.diality.us/changelog/leahi-fwcommon?cs=25c3fb3f0df41d7d125dc92062112eef57243a08 https://devapps.diality.us/changelog/leahi-fwcommon?cs=25c3fb3f0df41d7d125dc92062112eef57243a08 Dara Navaei committed 25c3fb3 on branch LDT-1195-dd-is-balancing-chamber-switching, LDT-1415-pressures-monitoring-td-baro and 22 more in leahi-fwcommon LDT-3605 updated the test support to initialize the blood leak driver if a new hardware config is selected

· /TestSupport.c

(-0, +5)

| History

| Source

| Diff

]]> Tue, 24 Feb 2026 11:55:37 -0800 Vendor - TEL - Jashwant Gantyada https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3344-1 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3344-1 Vendor - TEL - Jashwant Gantyada Closed LEAHI-DD-FIRMWARE-LDT-3344-1 ]]> Tue, 24 Feb 2026 10:38:39 -0800 Dara Navaei https://devapps.diality.us/changelog/leahi-fwcommon?cs=15a51afe22cbd841aea9edc4ed66db7e021ddc69 https://devapps.diality.us/changelog/leahi-fwcommon?cs=15a51afe22cbd841aea9edc4ed66db7e021ddc69 Dara Navaei committed 15a51af on branch LDT-1195-dd-is-balancing-chamber-switching, LDT-1415-pressures-monitoring-td-baro and 24 more in leahi-fwcommon Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

· /FPGA.c	(-2, +2)	| History	| Source	| Diff
· /TestSupport.c	(-2, +2)	| History	| Source	| Diff
· /TestSupport.h	(-2, +2)	| History	| Source	| Diff

]]> Tue, 24 Feb 2026 10:35:01 -0800 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3344-1 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3344-1 Raghu Kallala , Vinayakam Mani and Sean Nash finished reviewing LEAHI-DD-FIRMWARE-LDT-3344-1 LEAHI-DD-FIRMWARE-LDT-3344_Firmware support for Beta 2 FPGA updates. ]]> Mon, 23 Feb 2026 13:18:40 -0800 Vendor - TEL - Jashwant Gantyada https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3344-1 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3344-1 Vendor - TEL - Jashwant Gantyada started review LEAHI-DD-FIRMWARE-LDT-3344-1 ]]> Fri, 20 Feb 2026 14:19:23 -0800 Vendor - TEL - Sameer Poyil https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3344-1/#c27522 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3344-1/#c27522 Vendor - TEL - Sameer Poyil replied to Raghu Kallala in LEAHI-DD-FIRMWARE-LDT-3344-1

This is total mess up . that is what I want it a clean implementation. created a ticket LDT-3563 and closing all review comments.

Removing all the review comments and created a ticket to handle it in separate ticket -LDT-3563

removed.

changed.

removed.

the 2nd if statement for beta 1.0 is an ask from systems team to raise fault alarm if user by mistake enable Beta 2.0 config when Beta1.0 is active

Noe says we can distinguish between beta 1.9 and 2.0 w/ ID (4 and 6).
We still need test configs for beta 1.0 stuff and non-fpga differences.
We can use DD fpga ID # here in this macro instead of test config.
Since this is all temporary, I'm not that concerned about how we do this so long as it works.

I think Sameer is saying that the monitor should just call one get level function in FPGA and that one function (in FpgaDD.c) would handle all of this beta 1/1.9/2.0 stuff.
I agree, but didn't comment on it because it's all temporary anyway.

Why do we need a get function to call another get function? The caller of this function should just call getFPGAGPIOStatus() and then we wouldn't need this.

Move this up to public definitions section.

readFloaterLevelStatus is higher level functions that give the data from the FPGA.
Reason why we had these get functions here is, based on the FPGA response we translate it to the user understandable enum values (low, medium, high)

This is a reset call, as the default requirement is to be on Beta 1.9 HW
The logic is checking if the user is resetting the Beta 2.0 config, if yes, we will have to fall back to the Beta 1.9 FPGA registers

Level.c is a higher level abstracted functions and should not implement the HW dependent details in this file. this details should be pushed to FPGADD. and single function should handle all the cases instead of multiple functions.

Its not required, HW should be auto detected and initialized without any user configuration.

why its checking beta 2 and then setting beta 1.9 HW ?

We don't need this complex logic . use getFPGAVersions() function