WE CURRENTLY ARE WORKING DOWN FOR OUR EMERGENT CASE WHICH IS ASKED BY END CUSTOMER FOR EXPECTED DATE OF MASS PRODUCTION ON 28 FEB 2019. THE PROBLEM IS ADOPTED SBC UJA1075ATW WITH READING BACK UNKNOWN DEVICE ID.
ACCORDING TO A LIST OF DEVICE IDS IN APPLICATION NOTE AH1002 THE ID SHOULD BE
UJA0175A 0X5208
UJA1076A 0X5008
UAJ1078A 0X5308
UAJ1079A 0X5200
IN THE CASE WE USE THE HOST MCU S32K116 ALONG WITH SBC UJA1075ATW
BUT WHAT WE READ BACK IS
0x5002
IN THE OTHER BOARD DESIGNED WITH SAME SBC UJA1075ATW BUT DIFFERENT HOST MCU KINETIS EA
WHAT WE READ BACK
0x5004
WHATEVER WE TRY THE OTHER BOARD IN SAME MCU AND SBC
THEY ALWAYS READ WRONG DEVICE IDS
IN KINETIS EA 128 + SBC UJA1075ATW 0x5004
IN S32K116 + SBC UJA1075ATW 0x5002
IT'S STRANGE SINCE THE DEVICE ID ISN'T LISTED IN AH1002 AT ALL.
AND WE CANNOT WRITE TO CONTROL THE SBC UJA1075ATW.
WHAT REASON WILL CAUSE A DIFFERENT DEVICE ID READ BACK BY DIFFERENT MCU IN SAME SBC?
CAN YOU HELP TO FIND OUT WHAT THE PROBLEM IS?
AND HERE IS DOESN'T A CHIP PART NUMBER MATCHED WITH WHAT WE USE
UJA1075ATW
BUT
DATASHEET IS NO DOUBT RIGHT BUT IN APPLICATION NOTE AH1002 WE FIND NO UAJ1075ATW LISTED HERE. AND WE HAVE DEFINITELY CONFIRMED FOLLOWING IO
1. WD OFF - ACTIVE HIGH TO DISABLE
2. CHIP SELECT - ACTIVE LOW TO ENABLE
PLEASE SEE FOLLOWING SCREENSHOTS OF SCHEMATIC
2-1. AS YOU SEE THE HARDWARE DESIGN IS DIFFERENT FROM YOUR PROVIDED DESIGN REFERENCE ESPECIALLY:
IF THE HOST MCU IS NOT READY AND CONFIGURE THE IO ACTIVE HIGH THEN WDOFF WILL BE ACTIVE IN OUR DESIGN. WE THINK IT A BIG MISTAKE DUE TO OUR CASE REQUIRED TO UPDATE CODES BY CAN FLASH BOOTLOADER.
2-2. ANOTHER BIG PROBLEM WITH OUR DESIGN AS YOU SEE IS THE 2 SETS OF PINNING WAKEUP.
I DON'T HAVE IDEAS ABOUT THE ERROR DEVICE ID. IS IT POSSIBLE CAUSED BY HARDWARE DESIGN MISSES?
AND HERE ARE 2 KIND OF SAMPLE CODES PROVIDED BY YOU:
UJA107XA CODE.ZIP
LOOKS A SAMPLE CODES FOR S12X SERIES CHIPSET AND CANNOT BE APPLIED DIRECTLY IN LATEST S32K11X AND KINETIS EA.
UJA107XA CODE RAR
WITH MORE SIMPLE SAMPLE CODES WHICH ARE NOT SPECIFIC FOR A CHIPSET AND MATCH THE APPLICATION HINT
WHAT IS THE DEFINITE ONE?
CAN YOU PROVIDE SAMPLE CODES FOR
S32K116
KINETIS EA
WE HAVE VERY URGENT CASE READY FOR MASS PRODUCTION IN SCHEDULED DATE 28 FEB 2019.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
WE'VE FOUND OUT ANOTHER ISSUE WITH INT PIN. THE INT PIN KEEPS IN SEEDING INTERRUPT TO MCU WHEN POWER ON. DOES IT THE FACTOR CAUSE WE READ BACK WRONG DEVICE IDS? FROM YOUR DATASHEET HERE ARE LOTS OF REASONS THE INT PIN WILL SEND INTERRUPT TO HOST MCU AS BELOW:
SEEMS IF V1 / V2 UNDERVOLTAGE OR DESIGN MISSES WILL CAUSE INTERRUPT OUT TO HOST MCU?
Solved! Go to Solution.
Hi
Your issue has solved because of the wrong SPI timing.