NHD-2.8-240320AF-CSXP-FCTP- Display dose not turn on

MEENAKSHI

• September 16, 2024 08:05

When BLE packet sent. My display is turned on. But in this case I sent a packet to MCU display is not turned on but the operations are done. This the code.

switch(sierra_response){

case SBLE_CONNECT:

/* Change the state to connect */

prvlock.porta_status_flag = SBLE_CONNECT;

 

if(prvlock.sleep_mode_flag == 1)

{

pwr_LowPowerWakeup();

prvlock.sleep_mode_flag = 0;

 

/* Display Lock Screen */

xTaskNotifyFromISR( prvlock.touchtask, ulNotifiedDisplayLockScreen , eSetValueWithOverwrite, NULL );

vTaskDelay(5000);

}

break;

}

Help me

0

• 

  Engineering Support

  Community moderator

  • September 17, 2024 21:10

  Verify pwr_LowPowerWakeup() Functionality

  • Ensure that pwr_LowPowerWakeup() correctly powers up the display.
  • Confirm that the display receives adequate power after the MCU wakes up. You might need to add diagnostic logging around this function to verify its behavior.

  2. Ensure Proper Task Notification

  • Ensure that xTaskNotifyFromISR() is correctly notifying the touch task to update the display.
  • Check the implementation of the touchtask to confirm it correctly handles the notification and attempts to turn on the display.

  3. Adjust Delays

  • Experiment with the vTaskDelay(5000); value. The display might require a longer delay to stabilize after waking up. Try increasing the delay to see if it affects the display's ability to turn on.

  4. Verify the Display Power Sequence

  • Ensure the display power-on sequence is correct after pwr_LowPowerWakeup(). Some displays have specific timing requirements that need to be followed precisely during power-up.

  5. Check for Interrupt Conflicts

  • Ensure that no other interrupts or tasks are interfering with the display's power-on sequence.
  • Disable other peripherals temporarily to isolate the problem and see if it helps in turning on the display.

  6. Directly Test Display Commands

  • As a debugging step, try sending display initialization commands directly after pwr_LowPowerWakeup() without relying on other parts of the system (e.g., touch task). This can help identify if the issue lies in the display wake-up process.

  7. Verify BLE Packet Handling

  • Confirm that the BLE packet handling does not interfere with the display's initialization. Sometimes, shared resources like memory or I/O pins can cause conflicts if not managed correctly.

  0

Please sign in to leave a comment.