This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Pre-flashing AM3517 by emac

Other Parts Discussed in Thread: AM3517

I am looking at a design where the am3517 is to be used, and the use of the emac interface for

preflashing the nand over ethernet at production.

Currently i am playing with the Zoom AM3517 EVM board. I am trying to receive the UDP packet containing the "asic id" with wireshark, the

boot pins are set accordingly. But i am having no response.

Does someone have experience using ethernet for preflashing with this board/cpu?

Does it also exists host software to do this? I have only managed to find the Flash v1.2 that only supports serial and usb flashing, not ethernet.

 

-Markus

  • If you simply boot the board, you wont find the packet containing the ASIC ID. You'll have to connect the board to CCS (through JTAG) and do a CPU reset through CCS or manually go to address 14000 and then run the ROM code. Now you'll see the packet with the ASIC ID.


    Regards,
    Chintan

  • Thanks for your reply Chintan.

    I could not find any reference for this method in the technical reference document or other documents

    I have read. Is it described somewhere I haven`t looked? Does this method also apply for all the

    peripheral booting options?

     

    How about the host software, do you know if there exists solutions?

     

     

    -Markus

  • One more thing. This cpu reset that is bypassed when booting the board. Is it a pin configuration on the

    cpu itself, or is it in the hardware of the EVM board? So when using the cpu in a final design, will it be possible to

    use the memory and peripheral booting options as described in chapter 24.4.1 in the technical reference manual?

     

     

    -Markus

  • This is an issue with the Experimenter kit as on a reset, the PHY is not ready when the ROM code sends the ASIC ID packet. When you connect it to CCS, the PHY gets enough time to get active and now when the ROM code is ran, you see the ASIC ID packet which passes PHY this time. So in your final design, just make sure that your PHY gets active before the ROM code sends the ASIC ID packet. The other peripheral booting options work perfectly fine. I dont know of any existing solution for the host software.

    Regards,
    Chintan