Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
NuttX RTOS
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
f4grx
NuttX RTOS
Commits
8b64f8ae
Commit
8b64f8ae
authored
7 years ago
by
Gregory Nutt
Browse files
Options
Downloads
Patches
Plain Diff
Update README.txt
parent
692ebdf9
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
configs/stm32l476-mdk/README.txt
+31
-5
31 additions, 5 deletions
configs/stm32l476-mdk/README.txt
with
31 additions
and
5 deletions
configs/stm32l476-mdk/README.txt
+
31
−
5
View file @
8b64f8ae
...
...
@@ -25,10 +25,20 @@ STM32L476ME:
CRC calculation unit
RTC
Acronyms
========
MDK is, of course, the Motorola Development Kit.
MuC is the acronym that is used to refer to the STM32L476ME on the MDK
board.
MHB is the acronym given to Toshiba Interface Bridge, part number T6WV7XBG.
See https://toshiba.semicon-storage.com/us/product/assp/interface-bridge.html
NuttX runs the MuC.
Flashing
========
The MDK has a builtin FTDI to support flashing from openocd. There are a
The MDK has a built
-
in FTDI to support flashing from openocd. There are a
few extensions to openocd that haven't been integrated upstream yet. To
flash (or debug) the MDK, you will need the code from:
...
...
@@ -76,9 +86,25 @@ The serial console is configured on USART3 using MUC_UART3_TX (PC10) and
MUC_UART_RX (PC11). This connects to the FT4232 part which supports 4
CDC/ACM serial ports. The MuC console is on port C which will probably be
/dev/ttyUSB2 on your Linux host. Port A (ttyUSB0) is the MuC SWD debug
interface. Ports B and D are the MHB* debug and console ports, respectively.
interface. Ports B and D are the MHB debug and console ports, respectively.
The serial terminal that you use must be configured to use the /dev/ttyUSB2
device at 11500 baud, no parity, 8 bits of data, 1 stop bit (115200 8N1 in
minicom-speak) and with no flow control. Minicom works well.
You will probably need to be super-user in order access the /dev/ttyUSB2
device:
$ sudo minicom mdk
When mdk is the name of my saved configuration using the above serial
configuration.
The Motorola documentation also mentions picocom. NSH also works well with
picocom:
You may need to be super-user in order access the /dev/ttyUSB2 device.
$ sudo apt install picocom
$ sudo picocom -b 115200 /dev/ttyUSB2
*MHB is the acronym given to Toshiba Interface Bridge, part number T6WV7XBG.
See https://toshiba.semicon-storage.com/us/product/assp/interface-bridge.html
Everything else defaults correction. Ctrl-A then Ctrl-X will terminate
either the minicom or the picocom session.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment