[riot-notifications] [RIOT-OS/RIOT] cpu/esp32: periph uart cleanups (#11276)

Gunar Schorcht notifications at github.com
Tue Mar 26 16:00:44 CET 2019


@MrKevinWeiss Thank you for testing and figuring out the problem.

> I did notice an issue when leaving the GPIO9 and GPIO10 connected after a reset then trying to init gives some weird output then crashes.

Hm ... interessting. I haven't seen this problem before with the boards I used for testing. But, I have a board where I can reproduce it. The crash output
```
2019-03-26 12:45:06,756 - INFO # EXCE
```
is the beginning of an exception message.

GPIO9 and GPIO10 are critical on some boards because they are connected as additional data lines to the SPI flash memory for the QOUT and QIO flash modes. Normally, these GPIOs should be available when QOUT/QIO flash modes are not used. Obviously this does not seem to be the case with some boards. I have to think about whether it makes sense to forbit the use of these GPIOs to avoid such problems.

Could you test again with other GPIOs by overwriting the default board configuration:
```
CFLAGS='-DUART1_RXD=GPIO16 -DUART1_TXD=GPIO17' make BOARD=esp32-wroom-32 -C tests/periph_uart
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11276#issuecomment-476688805
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190326/1f3aef04/attachment-0001.html>


More information about the notifications mailing list