Yes, but i am only using uart1 for uboot debugging which is in domain of A9 and SSH trough usb, which also has inA9 domain. In the other side, I am just testing hello world with uart2 from M4 and I checked twice that this was not activated in A9 on device tree.
After all this considerations jlink still halting both cores. Now I read also, that I am using a old version of kernel linux 3.14.58 from udoo team, and also uboot 2015.xx, I read in embedded artist tutorial that the problem is related to RDC initialization for A9 on uboot which is not possible in my actual uboot version. However, for me this statement does not make sense since I was careful selecting, enabling and isolating peripherals.
I do not want to update linux, because is a huge labor. Udoo neo team is not bringing a new version with uboot and linux updated. So I will need to port from NXP official repository, and build my own image from scratch. I am leaving this updating process like my last alternative if every else fault.
However, I was checking the similitude between sabre board and udoo neo board and does not look to different in hardware point of view. Probably I am wrong...
Now I can work debugging without reset the board, but for me, still being a lost of time copy the built project to boot partition and then executing from linux and then debug... It is annoying. I am trying figure out how to flash directly the built project .bin with jlink by connecting to A9 side. It is a huge process also and there is not more information...
BTW, I already read all documentation that you recommend me, I dont know if I am forgetting something and probably I can debug without halt A9 with my actual version of images...
