Bad #define for S32K148 ENET wake feature

cancel
Showing results for 
Search instead for 
Did you mean: 

Bad #define for S32K148 ENET wake feature

311 Views
freddy_ben-zeev
Contributor IV

This is for SDK 2.9.2. In enet_driver.c there are a number of "#ifdef FEATURE_ENET_WAKEUP_IRQS". In S32K148_features.h it is #define'ed as FEATURE_ENET_WAKE_IRQS...
It could be intended as a different "#define" (there is a reference to FEATURE_ENET_WAKE_IRQS too in enet_driver.c) but in this case the other #define is missing (and other ENET IRQ features use a single such #define).

0 Kudos
3 Replies

204 Views
jiri_kral
NXP Employee
NXP Employee

Hi, 

it looks that these are different values - FEATURE_ENET_WAKEUP_IRQS is used as flag - (defined or not defined). FEATURE_ENET_WAKE_IRQS is value - 77u. 

Jiri

0 Kudos

204 Views
freddy_ben-zeev
Contributor IV

I thought so too at the beginning - but then I compared with other #define's such as FEATURE_ENET_RX_IRQS (and others) and there it uses only one #define for both flag and value... Even if what you suggest was true - the feature flag should be defined as (as 1 or as 0) - other similar feature flags in that file are defined so. 

0 Kudos

204 Views
jiri_kral
NXP Employee
NXP Employee

Hi,

I see - thanks for report. JIRA ticket was created for this issue and it will be solved probably in next SDK release. 

Jiri 

0 Kudos