Raspberry Pi

-


https://www.raspberrypi.org/documentation/hardware/computemodule/RPI-CM-DATASHEET-V1_0.pdf

 Booting Steps

  • When the Raspberry Pi is first turned on, the ARM core is off, and the GPU core is on. At this point the SDRAM is disabled.
  • The GPU starts executing the first stage bootloader, which is stored in ROM on the SoC. The first stage bootloader reads the SD card, and loads the second stage bootloader (bootcode.bin) into the L2 cache, and runs it.
  • bootcode.bin enables SDRAM, and reads the third stage bootloader (loader.bin) from the SD card into RAM, and runs it. [ More recent versions do not use a third stage bootloader. ]
  • [ If applicable ]loader.bin reads the GPU firmware (start.elf).
  • start.elf reads config.txt, cmdline.txt and kernel.img

loader.bin doesn't do much. It can handle .elf files, and so is needed to load start.elf at the top of memory (ARM uses SDRAM from address zero). There is a plan to add elf loading support to bootcode.bin, which would make loader.bin unnecessary, but it's a low priority (I guess it might save you 100ms on boot). [ This change has since taken place. ]

https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=6685#p85064



Accessing Raspberrypi without connecting it with monitor and keyboard


Terminal: enter the command ssh pi@raspberrypi


If this FAILS, try finding out what IP address is assigned to the Raspberry Pi from Router Admin Panel. Look up the device named something like raspberrypi and copy the IP address. Paste it into the command you tried from above where it now states raspberrypi.

create an 'ssh' file without any extension in 'boot' folder of sd card to enable ssh access.

connect to a wireless router create another file called "wpa_supplicant.conf" which contains the following info

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US

network={
 ssid="Your network SSID"
 psk="Your WPA/WPA2 security key"
 key_mgmt=WPA-PSK
}
Edit the country code, SSID and the WPA/WPA2 key with the info you need to connect to your network.


Qemu 

https://azeria-labs.com/emulate-raspberry-pi-with-qemu/

Comments

Post a Comment

Popular posts from this blog

Thread & Locks

-
Image
Threads Threads are subunits of processes, which can be scheduled independently by the operating system scheduler. Multiple threads can be executed at the same time on a single CPU core. The operating system assigns small slices of computing time to each thread, so that it seems to the user as if multiple tasks are executed at the same time. If multiple CPU cores are available, then multiple threads can be executed truly in parallel. We can either use the POSIX thread API, or the Objective-C wrapper around this API, NSThread. NSThread is a simple Objective-C wrapper around pthreads. Grand Central Dispatch With GCD you don’t interact with threads directly anymore. Instead you add blocks of code to queues, and GCD manages a thread pool behind the scenes. GCD decides on which particular thread your code blocks are going to be executed on, and it manages these threads according to the available system resources. This alleviates the problem of too many threads being cre...
Read more

Opengl-es Buffer

-
Image
Framebuffer A  Framebuffer  is a collection of buffers that can be used as the destination for rendering. OpenGL has two kinds of framebuffers: the  Default Framebuffer , which is provided by the  OpenGL Context ; and user-created framebuffers called  Framebuffer Objects  (FBOs). The buffers for default framebuffers are part of the context and usually represent a window or display device. The buffers for FBOs reference images from either  Textures  or  Renderbuffers ; they are never directly visible. Default Framebuffer The Default Framebuffer is the Framebuffer that OpenGL is created with. It is created along with the OpenGL Context. Like Framebuffer Objects , the default framebuffer is a series of images. Unlike FBOs, one of these images usually represents what you actually see on some part of your screen. Framebuffer Object FBO contains a collection of rendering destinations; color, depth and stencil buffer. These logical buff...
Read more

Kernel Startup

-
Image
BootLoader GRUB Version 2 (GRUB) Stage 1 :  boot.img  is stored in the master boot record (MBR) or optionally in any of the  volume boot records  (VBRs), and addresses the next stage by an  LBA48  address (thus, the 1024-cylinder limitation of GRUB legacy is avoided); at installation time it is configured to load the first sector of  core.img . Stage 1.5 :   core.img  is by default written to the sectors between the MBR and the first partition, when these sectors are free and available. For legacy reasons, the first partition of a hard drive does not begin at sector 1 (counting begins with 0) but at sector 63, leaving 62 sectors of empty space not part of any partition or file system, and therefore not prone to any problems related with it. Once executed,  core.img  will load its configuration file and any other modules needed, particularly  file system  drivers; at installation time, it is generated from...
Read more