Fabrication Location and IC Assembly Location A5EC013BM16AI4S - Case (202358)
Hello Team, We hope this email finds you well. Could you kindly provide us with the Fabrication Location and IC Assembly Location for the following part number: A5EC013BM16AI4S? In case this is not your responsibility, please forward it to the proper personnel. Please feel free to contact me if you have any questions or concerns. We appreciate your help. Thanks in advance! Case (202358)679Views0likes2CommentsProvide details for the - FFV1_ITEMMASTER_20240221
Hello, Below is the information needed as per request. ITEM NUMBER: FFV1H-ICS-1080-00 MPN_DESCRIPTION: IC, FPGA, AGILEX 7-M, AGMG039R47A2E2V, MEDIUM SPEED, EXTENDED TEMP, BGA4700 MANUFACTURER PART NUMBER (MPN): AGMG039R47A2E2V ABOVE DESCRIPTION MATCHES WITH MPN ? (YES / NO) ?: GIVEN MPN IS CORRECT & ORDERABLE / INCORRECT / INVALID ?: IS THIS MPN AVAILABLE IN TAPE & REEL PACKAGING OPTION ? (YES / NO) ?: IF YES, PROVIDE US CORRECT & ORDERABLE TAPE & REEL PART NUMBER ?: PROVIDE US CORRECT & ORDERABLE PART NUMBER FOR PURCHASE ORDER #PO's ?: LIFE CYCLE STATUS (ACTIVE / OBSOLETE / NRND) ?: PART MARKING ?: MOUNTING TYPE: SURFACE MOUNT TECHNOLOGY (SMT) ? (YES / NO) ?: MOISTURE SENSITIVITY LEVEL (MSL) ?: PACKAGING TYPE (TAPE & REEL, ROLL, TRAY, TUBE, AMMO, BULK etc.) ?: ROHS COMPLAINT ? (YES / NO) ?:1.1KViews0likes3CommentsKITRON_LifeCycle Status_RoHS_REACH_PFAS_
Hello Valued Supplier, This is Donald from Techadvance Solutions. We are contracted by Kitron Group to collect information regarding intentionally added per and polyfluoroalkyl substances (PFAS), Eu RoHS, and Eu REACH declarations for the attached part list. The coloured cells are the one for which we require declaration. RoHS and REACH Compliance · Lifecycle Status : (Active/Obsolete/EOL/NRND) · Last Time Buy (LTB) date ( If the input part is EOL ) · RoHS 3 (2015/863/EU) Certificate of Compliance (URL/File Name) · Alternate RoHS Compliant part if the input part is Obsolete/EOL/NRND/Non-RoHS · REACH Certificate of Compliance (URL/File Name) · SCIP reference number for SVHC present parts PFAS Investigation Material Group/ Functions - (Raw Cable, Electronics, Sealing, …) PFAS candidate for exclusion PFAS Presence (Yes/No) Alternatives/ Opportunities to phase out PFAS candidate. A letter of authorization from Kitron Group has been shared in this email. Please submit your response within one week from the date of this request. For any further clarification or concerns, please do feel free to email me. Thank you for your cooperation and support. Respectfully, Donald Sourcing Engineer TechAdvance Solutions1.1KViews0likes1CommentTiming for Quartus Multiply .BDF module
I am using a large number of Quartus IP LPMMULT "Basic Functions" both in parallel and then in series to calculate a 32 bit number from a large number of 16 bit (unsigned) array of numbers. Its a large branched tree. I assume each multiplication takes place with a low to high clock pulse. How do I know when the calculation is done to issue a clock pulse to the next adder using a pair of result[31..0] values from the previous multiplier. ---->Mult---->Mult---->Mult | ---->Mult--->Mult---- | ---->Mul---> Any help here from an expert would be appreciated -- I'm new to Quartus. PS this may be the wrong location for this question, if so where is best.1.3KViews0likes3CommentsTCLK Drive requirements
We have an Icelake-D Xeon Microprocessor, installed on a router PCB. I believe the part number is D-1700. We are driving the TCLK input ( AH-51 ) using a TI CPU JTAG Translator 74AXC8T245 , with output voltage set to 1.01 volts. This pin on the microprocessor pulls the data line voltage (VOH) to 0.633 volts. I am looking for the drive requirements for the TCLK input for this microprocessor. -g mooreg@juniper.net1.1KViews0likes1CommentTrouble with DRNLIN not updating IOBS data number
I am using DINLAP to invert a LaPlace transformed equation, and then DRNLIN for least-squares fitting data EY to 5 unknown parameters THETA. RNLIN subroutine does not update the data number IOBS and just recycles the IOBS=1 data point. Not sure way or how to input the IOBS to DRNLIN, which must have the counter within the source code. Here is the part that does not work. DINLAP works fine. Can you help? IDERIV = 0 !Derivatives are obtained by finite differences IOPT = 0 !Evaluate the function CALL DRNLIN(FUNC,NPARM,IDERIV,THETA,R,LDR,IRANK,DFE,SSE) ********************************************************************** SUBROUTINE FUNC (NPARM,THETA,IOPT,IOBS,FRQ,WT,DIF,DE,IEND) INTEGER NUMPT,NOBS,IOBS,NPARM,N COMMON NUMPT,NOBS,FINV INTEGER KMAX,IOPT,NPT,IEND,LDR REAL(8) EXP,FRQ,WT,DE(1),RELERR,THETA(NPARM),DIF,FINV EXTERNAL F !FUNCTION WITH LAPLACE TRANSFORM EQUATION COMPLEX(8) F,S INTRINSIC EXP NOBS = 80 IF (IOBS .LE. NOBS) THEN !IOBS SHOULD BE INCREASED TO NOBS BUT IT DOES NOT N = 1 !Number of DINLAP inverted data points at each time T(IOBS) ALPHA = 0.0E0 !Estimated no. of singularities of F. Unknown = 0. RELERR = 2.22D-7 !Default double precision relative accuracy KMAX = 500 !Max number of function evaluations for each T(I) CALL DINLAP(F,N,T,ALPHA,RELERR,KMAX,FINV) !Double Precision WT = 1.0E0 !Frequency of observation: Output FRQ = 1.0E0 !Weight for observation Output IEND = 0 !IOBS .LE. NOBS DIF = EY(IOBS) - FINV !Difference used for DRNLIN ELSE IEND = 1 !IOBS > NOBS, FINISH AFTER NOBS POINTS FOR NEXT DRNLIN ITERATION??? END IF RETURN END766Views0likes0CommentsPCIe configuration/capability list
Hi, So we've been testing a custom hardware card connected to a server with Ice Lake CPUs, and found it's been disconnecting over the PCIe connection. This is compared to an identical configuration but with Cascade Lake CPUs, where it managed to work. This was done using CentOS 8 Stream. I was wondering if there've been any changes to the PCIe capabilities, or anything else relevant that could help explain this. I'll also include an error message that might help, on sending a command to the hardware that causes it to fail: Hardware error from APEI Generic Hardware Error Source: 5 event severity: recoverable Error 0, type: fatal section_type: PCIe error port_type: 4, root port version: 3.0 command: 0x0547, status: 0x4010 device_id: 0000:b0:04.0 slot: 4 secondary_bus: 0xb1 vendor_id: 0x8086, device_id: 0x347c class_code: 000406 bridge: secondary_status: 0x2000, control: 0x0003 aer_uncor_status: 0x00004000, aer_uncor_mask: 0x01310000 aer_uncor_severity: 0x044ef030 TLP Header: 00000001 fc22fe01 dbc04000 00000000 Thanks, Matthew3.4KViews0likes5Comments