sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
99c69e9c07
nuttx/configs/pizero/README.txt

105 lines
3.4 KiB
Plaintext
Raw Normal View History

Squashed commit of the following: BCM2708: Add enough infrastructrue (more stubs) to get a clean compilation of the Pi Zero configuration (with many undefined things at link time). BCM2708: Add basic interrupt handling logic BCM2708: Add interrupt register definitions. BCM2708: Add irq.h header file BCM2708/Pi zero: bcm_boot.c and bcm_memorymap.h now compile. Added pizero linker script. BCM2708/Pi Zero: Add Make.defs needed to build. arch/arm/include/bcm2708, arch/arm/src/bcm2708, configs/pizero: Add some basic build and configuration logic. configs/pizero: Add some basic structure of the Rasperry Pi Zero port. Created directory configs/pizero. Nothing there now but a README.txt file. Add initial boot.c and memorymap.c files Author: Alan Carvalho de Assis <acassis@gmail.com> Add AUX/UART/SPI registers definition Author: Alan Carvalho de Assis <acassis@gmail.com> Pizero GPIO registers * Initial commit to add GPIO definitions * Add remaining GPIO registers definition Alan Carvalho de Assis <acassis@gmail.com> BCM2708 memory map: Add VBASE defintions; fix VCSDRAM address per Alan; move all virtual address to the bottom of the file to avoid confusion -- top is all physical address; bottom is all veritural address. Add initial memory map to BCM2708/BCM2835 Alan Carvalho de Assis <acassis@gmail.com>
2017-10-09 21:06:47 +02:00
README
======
Update a README file
2017-10-09 21:40:54 +02:00
This README file discusses the port of NuttX to the Raspberry Pi Zero.
The Raspberry Pi Zero is based on the Broadcom BCM2835 CPU. This is the
same Broadcom chip used in the Raspberry Pi Model A, B, B+, the Compute
Module.
STATUS
======
2017-10-09: This is a work in progress. The port is not complete and
will not build to completion. Missing logic includes:
- GPIO support,
- System timer initialization, and
- Serial driver.
net/tcp: Same change to tcp_send_buffered.c probably also applies to tcp_send_unbuffered.c.
2017-10-20 00:14:18 +02:00
2017-10-19: Much of that logic is in place but there are a few things
still missing.
- Mini-UART Baud divisor calculation,
arch/mips/include/mips32/cp0.h: Fix some copy-paste errors that cause malformed comments and syntax errors when certain CP0 CONFIG1 bits are referenced. Note in Issue 123 by Anonymous.
2018-10-12 22:52:05 +02:00
- Start-up logic. My understand from what I have read on the Internet
net/tcp: Same change to tcp_send_buffered.c probably also applies to tcp_send_unbuffered.c.
2017-10-20 00:14:18 +02:00
is the PiZero OS starts up in hypervisor mode with the MMU and I- and
arch/mips/include/mips32/cp0.h: Fix some copy-paste errors that cause malformed comments and syntax errors when certain CP0 CONFIG1 bits are referenced. Note in Issue 123 by Anonymous.
2018-10-12 22:52:05 +02:00
D-Caches enabled. This probably means that the standard, classic ARM
net/tcp: Same change to tcp_send_buffered.c probably also applies to tcp_send_unbuffered.c.
2017-10-20 00:14:18 +02:00
startup logic at at arch/arm/src/arm/up_head.S will need to be replaced
with some custom logic.
No testing has yet been performed.
Squashed commit of the following: BCM2708: Add enough infrastructrue (more stubs) to get a clean compilation of the Pi Zero configuration (with many undefined things at link time). BCM2708: Add basic interrupt handling logic BCM2708: Add interrupt register definitions. BCM2708: Add irq.h header file BCM2708/Pi zero: bcm_boot.c and bcm_memorymap.h now compile. Added pizero linker script. BCM2708/Pi Zero: Add Make.defs needed to build. arch/arm/include/bcm2708, arch/arm/src/bcm2708, configs/pizero: Add some basic build and configuration logic. configs/pizero: Add some basic structure of the Rasperry Pi Zero port. Created directory configs/pizero. Nothing there now but a README.txt file. Add initial boot.c and memorymap.c files Author: Alan Carvalho de Assis <acassis@gmail.com> Add AUX/UART/SPI registers definition Author: Alan Carvalho de Assis <acassis@gmail.com> Pizero GPIO registers * Initial commit to add GPIO definitions * Add remaining GPIO registers definition Alan Carvalho de Assis <acassis@gmail.com> BCM2708 memory map: Add VBASE defintions; fix VCSDRAM address per Alan; move all virtual address to the bottom of the file to avoid confusion -- top is all physical address; bottom is all veritural address. Add initial memory map to BCM2708/BCM2835 Alan Carvalho de Assis <acassis@gmail.com>
2017-10-09 21:06:47 +02:00
Basic Setup
===========
+------------+
| |
| +--+
| USB | | <----------------------------> USB Power Source
| +--+ +------------+
| | | +--+
| +--+ | | | <---> Keyboard
| USB | | <-------->| USB +--+
| +--+ | HUB |
| | | +--+
| | | | | <---> Mouse
| | | +--+
| | +------------+
| Mini +--+
| HDMI | | <----------------------------> Monitor/TV
| +--+
| |
+------------+
You might be able to use the hub to power the Pi Zero, but I was not
able to do that; my hub would not switch on power until it was enumerated
by the host (the Raspberry Pi Zero), but then I could not power the Pi
with the hub because it was not providing power. Chicken'n'Egg.
Update a README file
2017-10-09 21:40:54 +02:00
NuttX Boot Sequence
===================
To be provided.
Configurations
==============
Information Common to All Configurations
----------------------------------------
Each Raspberry Pi Zero configuration is maintained in a sub-directory
and can be selected as follow:
tools/configure.sh [OPTIONS] pizero/<subdir>
Where [OPTIONS] include -l to configure for a Linux host platform and
-c means to configure for a Windows Cygwin host platform. -h will give
you the list of all options.
Before building, make sure the PATH environment variable includes the
correct path to the directory than holds your toolchain binaries.
And then build NuttX by simply typing the following. At the conclusion of
the make, the nuttx binary will reside in an ELF file called, simply, nuttx.
make
The <subdir> that is provided above as an argument to the tools/configure.sh
must be is one of the following.
NOTES:
1. These configurations use the mconf-based configuration tool. To
change any of these configurations using that tool, you should:
a. Build and install the kconfig-mconf tool. See nuttx/README.txt
see additional README.txt files in the NuttX tools repository.
b. Execute 'make menuconfig' in nuttx/ in order to start the
reconfiguration process.
Configuration Sub-directories
-----------------------------
nsh:
This simple configuration directory provide the NuttShell (NSH).
Reference in New Issue Copy Permalink