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.

BAD0 in DRAM memory

Other Parts Discussed in Thread: AM3517

Hi,

I would like to know the meaning of "BAD0" error.

My customer uses AM3517 with WEC7. Customer's system sometimes fails to boot the WEC7 OS.

Customer tried to read DRAM memory when boot failed.  But "BAD0" message was displayed in some memory address.

What is "BAD0" message?  Is it the same meaning of memory read failed? I wonder BAD0 spot may cause the OS boot failure.

Please let me know the meaning of "BAD0".

Best regards,

Michi 

  • Dear Michi-san,

    As you guessed right the BAD0 occurs when its unable to read the memory. Are you using CCS to read the memory? Since Wince has enabled virtual memory, if you use a debugger which is not aware of virtual memory, this can happen as well. Basically the error doesn't mean that memory access has completely failed, that's just one of the possibility.

  • Dear Renjith-san,

    Thank you for your reply.

    According to customer's information,

    #80226AC0 - 80226AFFh ----- All BAD0

    #80226C80 - 80226CBF ------ All OK

    #80226CC0 - 80226DFF ----- All BAD0

    #80226E00 - 80226E2F ----- All OK

    #80226E30 - 80226F7F ------ All BAD0

    #80226F80 - 80226FFF ----- All OK

    Address #80000000h -  is DRAM area on customer's system.

    Are you aware from the above symptom? Is this symptom from virtual memory system of OS?

    And does "BAD0" show that it is just occurred memory read error?

    Pleasee advise me.

    Best regards,

    Michi

     

  • Dear Michi-san,

    Did the customer checked this using CCS or Platform builder? If you are checking from virtual memory the address 80000000h need not be pointing to DRAM. It entirely depends on the page table mapping performed by the OS. 

    If WINCE is not running then these addresses are valid. BAD0 means that the read has failed. 

    Can you describe the exact issue that customer is facing? Are they able to boot up WINCE successfully? More details about the issue will be helpful.