raiden00pl opened a new pull request, #20903:
URL: https://github.com/apache/nuttx/pull/20903

   
   ## Summary
   
     Fixes in the nRF52/nRF53/nRF54L IEEE 802.15.4 radio driver:                
                                                                                
                                                                                
                                    
     - TX scheduling: five code paths decided independently when a waiting 
frame may start, and lost frames or disabled the radio during an ACK; one 
txnext() now owns that decision                                                 
                                               
     - RX filter followed neither 7.5.6.2 nor the PAN coordinator rules: 
beacons were dropped once macPANId was set, broadcast PAN ID frames and 
source-only frames were dropped                                                 
                                                   
     - RSSI of a received frame was always 0 and LQI was the raw register value 
                                                                                
                                                                                
                                    
     - the radio interrupts ran at NVIC priority 0 above the critical sections, 
their handlers call the OS                                                      
                                                                                
                                    
     - nRF5340: the application core left the HFXO load capacitors untrimmed 
unless it used the HFXO itself, so the network core radio was off frequency     
     
   ## Impact
   
   fixes for nordic IEEE 802.15.4 
   
   ## Testing
   
   nrf52840-dk, nrf5340-dk (net core), nrf54lm20-dk, nrf52832-dk with MRF24J40, 
every coordinator/device pair: association, 50 direct, 30 indirect frames, 
poll, expiry, re-association, energy scan, resources back at baseline.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to