Re: Interest in developer preview?
Posted: Sat Aug 27, 2016 1:35 pm
[ advanced note ]
AES_IDLE_REG
*) i have not used this in preview code, for certain reasons.
but want now use - not sure - so i ask:
in technical reference manual read,
we wait for AES_IDLE_REG until reads 1
*) just in time missed a VAR for it or a define.
in esp32_technical_reference_manual_en
AES_IDLE_REG is described on side 116 with address 0x3FF01004
for a try i added directly in eagle.fpga32.rom.addr.v7.ld
and define in global app code
in app code i wait for the AES_IDLE_REG reads 1
not sure - is this just in time the right way for AES_IDLE_REG ? ( int ? )
compile & link done - can't test flash - have no modul with esp32 release.
edit: ( S. 117 )
but think this is not the right way, because
register 10.2: AES_IDLE_REG (0x004)
is 32bit
your further help and critical ("never change the ld file" )
is welcome
best wishes
rudi
AES_IDLE_REG
*) i have not used this in preview code, for certain reasons.
but want now use - not sure - so i ask:
in technical reference manual read,
we wait for AES_IDLE_REG until reads 1
*) just in time missed a VAR for it or a define.
in esp32_technical_reference_manual_en
AES_IDLE_REG is described on side 116 with address 0x3FF01004
for a try i added directly in eagle.fpga32.rom.addr.v7.ld
Code: Select all
..
PROVIDE (AES_IDLE_REG = 0x3FF01004 );
..
Code: Select all
..
extern int AES_IDLE_REG;
..
Code: Select all
..
while ( AES_IDLE_REG != 1) ;
..
not sure - is this just in time the right way for AES_IDLE_REG ? ( int ? )
compile & link done - can't test flash - have no modul with esp32 release.
edit: ( S. 117 )
but think this is not the right way, because
register 10.2: AES_IDLE_REG (0x004)
is 32bit
your further help and critical ("never change the ld file" )
is welcome
best wishes
rudi