Fixed errors

diff --git a/docs/pinmux.mdwn b/docs/pinmux.mdwn
index 46388545a4aa9f93d5fdcf2f3912b9a98cc24abe..295c652cc4781aa5d296af7839f0aa510a270e8d 100644 (file)
--- a/docs/pinmux.mdwn
+++ b/docs/pinmux.mdwn
@@ -473,7 +473,7 @@ The diagram below shows the layout of the configuration byte.
 If the block is created with more GPIOs than can fit in a single data word,
 the next set of GPIOs can be accessed by incrementing the address.
 For example, if 16 GPIOs are instantiated and 64-bit data bus is used, GPIOs
-0-7 are accessed via address 0, whereas GPIOs 8-15 are accessed by address 0.
+0-7 are accessed via address 0, whereas GPIOs 8-15 are accessed by address 1.
 
 ### Example Memory Map
 

diff --git a/docs/pinmux/gpio-mem-layout.jpg b/docs/pinmux/gpio-mem-layout.jpg
index d8c2b12f2d24da284eaa15b5022bc8c46080b9e8..e7c30a3a5f8f025604fb96973ee16d152876ddf7 100644 (file)
Binary files a/docs/pinmux/gpio-mem-layout.jpg and b/docs/pinmux/gpio-mem-layout.jpg differ