added input ports

Author: ineskhou

FprimeZephyrReference/Components/Burnwire/Burnwire.fpp

@@ -29,6 +29,12 @@ module Components {
         # @ Example port: receiving calls from the rate group
         # sync input port run: Svc.Sched
 
+        @ Port getting start signal
+        sync input port burnStart: Fw.Signal
+
+        @ Port getting stop signal
+        sync input port burnStop: Fw.Signal
+
         @ Input Port to get the rate group
         sync input port schedIn: Svc.Sched
 

FprimeZephyrReference/Components/Burnwire/Burnwire.hpp

@@ -7,6 +7,7 @@
 #ifndef Components_Burnwire_HPP
 #define Components_Burnwire_HPP
 
+#include <atomic>
 #include "FprimeZephyrReference/Components/Burnwire/BurnwireComponentAc.hpp"
 
 namespace Components {
@@ -48,11 +49,10 @@ class Burnwire final : public BurnwireComponentBase {
     //! Handler implementation for command STOP_BURNWIRE
     void STOP_BURNWIRE_cmdHandler(FwOpcodeType opCode, U32 cmdSeq) override;
 
-    Fw::On m_state = Fw::On::OFF;  // keeps track if burnwire is on or off
-    std::atomic<U32>
-        m_safetyCounter;  // makes this an atomic variable (so its set only in one comnmdn), so you won't have smth so
-                          // you read and write half the value bc a corrupted read could be dangerouts
-    U32 m_safetyMaxCount = 5;  // make this a aparamater
+    Fw::On m_state = Fw::On::OFF;      // keeps track if burnwire is on or off
+    std::atomic<U32> m_safetyCounter;  // makes this an atomic variable (so its set only in one command),
+                                       // you read and write half the value bc a corrupted read could be dangerouts
+    U32 m_safetyMaxCount = 5;          // make this a aparamater
 };
 
 }  // namespace Components

FprimeZephyrReference/Components/Burnwire/docs/sdd.md

@@ -16,19 +16,12 @@ Add requirements in the chart below
 |BW-005|The burnwire component shall be controlled by a safety timeout attached to a 1Hz rate group that can be changed within the code |Integration Test|
 |BW-006|The burnwire safety time shall emit an event when it starts and stops |Integration Test|
 
-
-Use the Zephyr GPIO driver --> so that the GPIO driver can be changed instead of being hardcoded
-checking is it calling that set port, break the two layers out
-Write, read get interrupt from GPIO
-single port of type driver.gPIO write that is a port on your FPP
-
-
 ## Port Descriptions
 Name | Type | Description |
 |----|---|---|
-|----|`Fw::Signal`|Receive stop signal to stop the burnwire|
-|----|`Fw::Signal`|Receive start signal to start burnwire|
-|----|`Drv::GpioWrite`|Control GPIO state to driver|
+|burnStop|`Fw::Signal`|Receive stop signal to stop the burnwire|
+|burnStart|`Fw::Signal`|Receive start signal to start burnwire|
+|gpioSet|`Drv::GpioWrite`|Control GPIO state to driver|
 |schedIn|[`Svc::Sched`]| run | Input | Synchronous | Receive periodic calls from rate group
 
 
@@ -62,4 +55,4 @@ Add unit test descriptions in the chart below
 
 ## Parameter
 | Name | Description |
-| ---- | ----------- |
+| m_safetyMaxCount | The maximum amount that the burnwire will burn before stopping itself for safety |

FprimeZephyrReference/ReferenceDeployment/Top/ReferenceDeploymentTopology.cpp

@@ -14,7 +14,7 @@
 #include <zephyr/drivers/gpio.h>
 
 static const struct gpio_dt_spec ledGpio = GPIO_DT_SPEC_GET(DT_ALIAS(led0), gpios);
-// static const struct gpio_dt_spec ledGpio = GPIO_DT_SPEC_GET(DT_ALIAS(burnwire0), gpios);
+// static const struct gpio_dt_spec burnwire0Gpio = GPIO_DT_SPEC_GET(DT_ALIAS(burnwire0), gpios);
 
 static const struct gpio_dt_spec burnwire0Gpio = {
     .port = DEVICE_DT_GET(DT_NODELABEL(gpio0)),