Hm, I see, the kernel falls back to the tty1 console if no console is specified. Adding console=null seems to really help to work around that.
I just tested using 2.7b3 release and a V1.1A module.
setenv setup 'setenv setupargs ${memargs} consoleblank=0 console=null'
saveenv
This worked fine here, the board booted in around 10 seconds.
I don’t think that this is hardware related… Which BSP version are you using exactly on the two modules?
Can you try again with this settings and provide the full journal log journalctl -b 0 > journal.log.