Hi Surya, Could you please give us more details? It is hard to help when we don't know exactly what is your scenario and the way you are doing it.
What debugger tool are you using? Are you using the mainline ethernet driver? (Please read your message again, I know you are using RX65 chip, but many people don't know it and you didn't say it). Which are the steps to reproduce this issue? Does this issue happen on other arch as well (i.e. STM32) ? BR, Alan On 4/29/20, Surya prakash Verma <surya.prak...@tataelxsi.co.in.invalid> wrote: > Hello Everyone, > > We are facing issue of hang when powering up board and target > simultaneously. > > We have debugged and observed that it is hanging at nxsem_wait(sem) during > auto ip configuration by dhcp where waiting for > offer repsonse corresponding to dhcp_request at lock nxsem_wait(sem). This > lock is not getting released. So it is hanging. > > As per my understanding router may not be in UP state when discovery message > send from board. So router will not send any IP offer message. > So the above lock will keep waiting as this lock will wait as long as > necessary to get the lock. > > Please let us know, if someone face similar issue. > > Regards > SURYA PRAKASH VERMA > MOB: +91 9916589237 > TATA ELXSI > Tower B, 9th Floor, Prestige Shantiniketan > ITPB Road, Whitefield, Bangalore 560048 India > > > ________________________________ > Disclaimer: This email and any files transmitted with it are confidential > and intended solely for the use of the individual or entity to whom they are > addressed. If you are not the intended recipient of this message , or if > this message has been addressed to you in error, please immediately alert > the sender by reply email and then delete this message and any attachments. > If you are not the intended recipient, you are hereby notified that any use, > dissemination, copying, or storage of this message or its attachments is > strictly prohibited. Email transmission cannot be guaranteed to be secure or > error-free, as information could be intercepted, corrupted, lost, destroyed, > arrive late or incomplete, or contain viruses. The sender, therefore, does > not accept liability for any errors, omissions or contaminations in the > contents of this message which might have occurred as a result of email > transmission. If verification is required, please request for a hard-copy > version. > ________________________________ >
