The id will be checked just before the first comand touching the flash is
executed (setparms, mass_erase, ...), that's the auto_probe. Yes, it would be
nice if you could check whether commenting out the read_id helps.
But: Please don't use the old version. The updated patch had been merged
alr
This is an automated email from Gerrit.
Tarek BOCHKATI (tarek.bouchk...@gmail.com) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/6015
-- gerrit
commit 447071fe4cf84fc785910f0854f5b797dc510ec5
Author: Tarek BOCHKATI
Date: Tue Jan 12 20:10:23 2021 +010
This is an automated email from Gerrit.
Tarek BOCHKATI (tarek.bouchk...@gmail.com) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/6016
-- gerrit
commit aa33b014259f643190aed5c933196a99604a208b
Author: Tarek BOCHKATI
Date: Tue Jan 12 20:11:11 2021 +010
I have replaced the flash chip in other board also, but no luck. it fails to
start the debug session.
When will be RDJDID send from Openocd? does it send once after memory mapped is
configured from cfg or before that?
Can i comment the validation of flash id in openocd source and allow to prog
I'm afraid there is no chance to investigate this any further. Maybe the WIP
bit sticks at '1' after reset, maybe the flash doesn't reply to RDJDID in QPI
mode (early revision, defective?), so you might try to use only SPI mode in
your cfg. Or replace the flash chip? Since it works on one board
This is an automated email from Gerrit.
Tarek BOCHKATI (tarek.bouchk...@gmail.com) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/6014
-- gerrit
commit 89ea614fbf6ed882c76cd3c9932d10c3fcd38531
Author: Tarek BOCHKATI
Date: Tue Jan 12 11:57:18 2021 +010
