AnsweredAssumed Answered


Question asked by js-atl on May 22, 2017
Latest reply on May 25, 2017 by gverma

I am working on a modified prototype platform that ports the AD9371 EVM + KC706 Mykonos reference design to a AD9371 EVM + KC705 board and swaps out the ARM CPU on the KC706 for a x86 Linux hardware platform with DMA over PCIe.  Everything else about this system - JESD204B links, sample rates, AD9371 connectivity remains the same.


We have recompiled the Mykonos API on the x86 system, with suitable "common.c" changes. This uses all the standard EVM setup (link rates, clocks etc) from the KC706 reference design. On the new platform we can setup the JESD204B links, program the AD9528 clock generator on the AD9371 EVM, reset and initialize the AD9371 device, download the ARM M3 image and verify it has a valid checksum on the HW - all good.


BUT... when we boot the ARM M3 boots, it returns an API error MYKONOS_ERR_ARMSTATE_EXCEPTION -  "ARM system problem has been detected". 


All sequences in the recommended API boot sequence up to this point pass successfully, and monitor logic in the FPGA shows all clocks present and on frequency, and the JESD204B sync active and correct. A memory dump of the M3 program memory further verifies that ARM download image is all present and correct.


Is there any known cause or mechanism to diagnose the cause of the MYKONOS_ERR_ARMSTATE_EXCEPTION exception?