Aug 27, 2020
10:13 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 27, 2020
10:13 PM
Can you please clarify if following will be the TLF35584 device behaviour when MCU is goes through below scenarion
1. MCU comes out of Reset
2. MCU initializes SBC registers & enables watchdog & error monitoring (Proper Initialization of SBC)
3. MCU send SBC SPI: Go to NORMAL command --> At this point SBC is in Normal mode
4. MCU crashes/resets due to error in MCU's application SW
- After Step#4, will TLF35584 device be in Normal Mode or go to Init (will SBC observe MCU going through a reset and move to Init) ?
- After Step#4, will TLF35584 device move to FailSafe State as error monitoring signal goes low due to MCU reset ?
1. MCU comes out of Reset
2. MCU initializes SBC registers & enables watchdog & error monitoring (Proper Initialization of SBC)
3. MCU send SBC SPI: Go to NORMAL command --> At this point SBC is in Normal mode
4. MCU crashes/resets due to error in MCU's application SW
- After Step#4, will TLF35584 device be in Normal Mode or go to Init (will SBC observe MCU going through a reset and move to Init) ?
- After Step#4, will TLF35584 device move to FailSafe State as error monitoring signal goes low due to MCU reset ?
Solved! Go to Solution.
1 Solution
Sep 01, 2020
12:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sep 01, 2020
12:52 AM
In scenario -2 Step#4 is an additional step ("Go to normal state") needed. You can check always the DEVSTAT register of TLF to known in which state the TLF is.
Any hint for scenario - 1 Step#4: The window watchdog and ERR pin monitor function should be enabled by HW (MPS pin low) and maybe disabled if needed (e.g. during reprogramming). Information about the state of this functions you can find in register RSYSPCFG1 and RWDCFG0.
Any hint for scenario - 1 Step#4: The window watchdog and ERR pin monitor function should be enabled by HW (MPS pin low) and maybe disabled if needed (e.g. during reprogramming). Information about the state of this functions you can find in register RSYSPCFG1 and RWDCFG0.
4 Replies
Aug 28, 2020
03:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 28, 2020
03:29 AM
The pin ROT of TLF35584 is an output and the TLF35584 will not react if this pin is driven low from MCU. In this case the TLF35584 will be stay in Normal Mode.
If an error monitoring triggered or an watchdog overflow occurs then TLF35584 goes to INIT state. This is dependent of configuration of the TLF.
If an error monitoring triggered or an watchdog overflow occurs then TLF35584 goes to INIT state. This is dependent of configuration of the TLF.
Aug 31, 2020
10:12 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 31, 2020
10:12 AM
Thank you for clarifying, In this case can you please clarify below questions
Scenario - 1
1. Normal Powerup
2. TLF device is in Init mode
3. On MCU Bootloader SW detects a valid application SW and then jumps to application SW
4. In application SW, SBC driver Initializes SBC (enable watchdog, error & voltage monitoring etc.).
5. SBC driver gives SPI command "Go to Normal", TLF device is in Normal mode now.
6. Application SW is in normal operation.
7. Application SW receives re-programming request
8. Application SW disables SBC watchdog, error monitoring etc. and gives reset to go boot mode.
9. Bootloader SW detects re-programming request and stays in boot mode- TLF device is in Normal mode
10. Bootloader SW re-configures SBC (based on bootloader requirements)
Scenario - 2
1. Normal Powerup
2. TLF device is in Init mode
3. On MCU Bootloader SW detects a Invalid/No application SW and then stays in boot mode - TLF device is in Init mode
4. Bootloader SW re-configures SBC (based on bootloader requirements)
In Scenario - 1 Step#10, should SBC complex driver in the bootloader take care of any additional steps when compared to Scenario - 2 , Step#4.
In both the cases, TLF state machine will be in different states, so wanted to confirm if there any differences to configure the TLF device.
Scenario - 1
1. Normal Powerup
2. TLF device is in Init mode
3. On MCU Bootloader SW detects a valid application SW and then jumps to application SW
4. In application SW, SBC driver Initializes SBC (enable watchdog, error & voltage monitoring etc.).
5. SBC driver gives SPI command "Go to Normal", TLF device is in Normal mode now.
6. Application SW is in normal operation.
7. Application SW receives re-programming request
8. Application SW disables SBC watchdog, error monitoring etc. and gives reset to go boot mode.
9. Bootloader SW detects re-programming request and stays in boot mode- TLF device is in Normal mode
10. Bootloader SW re-configures SBC (based on bootloader requirements)
Scenario - 2
1. Normal Powerup
2. TLF device is in Init mode
3. On MCU Bootloader SW detects a Invalid/No application SW and then stays in boot mode - TLF device is in Init mode
4. Bootloader SW re-configures SBC (based on bootloader requirements)
In Scenario - 1 Step#10, should SBC complex driver in the bootloader take care of any additional steps when compared to Scenario - 2 , Step#4.
In both the cases, TLF state machine will be in different states, so wanted to confirm if there any differences to configure the TLF device.
Sep 01, 2020
12:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sep 01, 2020
12:52 AM
In scenario -2 Step#4 is an additional step ("Go to normal state") needed. You can check always the DEVSTAT register of TLF to known in which state the TLF is.
Any hint for scenario - 1 Step#4: The window watchdog and ERR pin monitor function should be enabled by HW (MPS pin low) and maybe disabled if needed (e.g. during reprogramming). Information about the state of this functions you can find in register RSYSPCFG1 and RWDCFG0.
Any hint for scenario - 1 Step#4: The window watchdog and ERR pin monitor function should be enabled by HW (MPS pin low) and maybe disabled if needed (e.g. during reprogramming). Information about the state of this functions you can find in register RSYSPCFG1 and RWDCFG0.
Sep 01, 2020
01:32 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sep 01, 2020
01:32 PM
MoD wrote:
In scenario -2 Step#4 is an additional step ("Go to normal state") needed. You can check always the DEVSTAT register of TLF to known in which state the TLF is.
Any hint for scenario - 1 Step#4: The window watchdog and ERR pin monitor function should be enabled by HW (MPS pin low) and maybe disabled if needed (e.g. during reprogramming). Information about the state of this functions you can find in register RSYSPCFG1 and RWDCFG0.
Thank you, this makes sense. Yes, Ofcourse the MPS pin will be low in the HW (production intent).