Exploring Raspberry Pi

Click on the chapter titles below to view the digital resources, source code and external resources that are described in the book chapters.

Part I – Raspberry Pi Basics

Chapter 1: Raspberry Pi Hardware (pg. 3)

Chapter 2: Raspberry Pi Software (pg. 23)

Chapter 3: Exploring Embedded Linux Systems (pg. 55)

Chapter 4: Interfacing Electronics (pg. 113)

Chapter 5: Programming on the Raspberry Pi (pg. 159)

Part II – Interfacing, Controlling, and Communicating

Chapter 6: Interfacing to the Raspberry Pi Input/Outputs (pg. 219)

Chapter 7: Cross-Compilation and the Eclipse IDE (pg. 275)

Chapter 8: Interfacing to the Raspberry Pi Buses (pg. 309)

Chapter 9: Enhancing the Input/Output Interfaces on the RPi (pg. 363)

Chapter 10: Interacting with the Physical Environment (pg. 405)

Chapter 11: Real-Time Interfacing Using the Arduino (pg. 453)

Part III – Advanced Interfacing and Interaction

Chapter 12: The Internet of Things (pg. 483)

Chapter 13: Wireless Communication and Control (pg. 535)

Chapter 14: Raspberry Pi with a Rich User Interface (pg. 577)

Chapter 15: Images, Video, and Audio (pg. 615)

Chapter 16: Kernel Programming (pg. 647)

Index (pg. 677)

3 Comments

Angelo July 2, 2016 at 7:13 pm

Erratum: Page 184 contains the phrase

“platform-independent assembler code”.

Assembler code is not platform independent. Maybe what you mean is that it is still a text file, not a binary?

The beablebone book contains the same error on page 171.

admin July 3, 2016 at 12:45 pm

Thanks Angelo, that should be platform-dependent assembler code. To illustrate this point further I have added the two .s file examples below, the first is compiled with a native compiler under x86 and the second is compiled using a cross-compiler to ARMHF. The .s files can be compared.
The .c source file:

molloyd@molloyd-VirtualBox:~/temp$ more test.c
#include
int main(){
   printf("Hello World\n");
   return 0;
}

molloyd@molloyd-VirtualBox:~/temp$ more test.c

#include

int main(){

printf("Hello World\n");

return 0;

}

The Intel x86 Code:

molloyd@molloyd-VirtualBox:~/temp$ gcc -S test.c
molloyd@molloyd-VirtualBox:~/temp$ more test.s
	.file	"test.c"
	.section	.rodata
.LC0:
	.string	"Hello World"
	.text
	.globl	main
	.type	main, @function
main:
.LFB0:
	.cfi_startproc
	pushq	%rbp
	.cfi_def_cfa_offset 16
	.cfi_offset 6, -16
	movq	%rsp, %rbp
	.cfi_def_cfa_register 6
	movl	$.LC0, %edi
	call	puts
	movl	$0, %eax
	popq	%rbp
	.cfi_def_cfa 7, 8
	ret
	.cfi_endproc
.LFE0:
	.size	main, .-main
	.ident	"GCC: (Ubuntu 5.3.1-14ubuntu2.1) 5.3.1 20160413"
	.section	.note.GNU-stack,"",@progbits

molloyd@molloyd-VirtualBox:~/temp$ gcc -S test.c

molloyd@molloyd-VirtualBox:~/temp$ more test.s

.file "test.c"

.section .rodata

.LC0:

.string "Hello World"

.text

.globl main

.type main, @function

main:

.LFB0:

.cfi_startproc

pushq %rbp

.cfi_def_cfa_offset 16

.cfi_offset 6, -16

movq %rsp, %rbp

.cfi_def_cfa_register 6

movl $.LC0, %edi

call puts

movl $0, %eax

popq %rbp

.cfi_def_cfa 7, 8

ret

.cfi_endproc

.LFE0:

.size main, .-main

.ident "GCC: (Ubuntu 5.3.1-14ubuntu2.1) 5.3.1 20160413"

.section .note.GNU-stack,"",@progbits

And the equivalent ARMHF code:

molloyd@molloyd-VirtualBox:~/temp$ arm-linux-gnueabihf-gcc -S test.c -o test1.s
molloyd@molloyd-VirtualBox:~/temp$ more test1.s
	.arch armv7-a
	.eabi_attribute 28, 1
	.fpu vfpv3-d16
	.eabi_attribute 20, 1
	.eabi_attribute 21, 1
	.eabi_attribute 23, 3
	.eabi_attribute 24, 1
	.eabi_attribute 25, 1
	.eabi_attribute 26, 2
	.eabi_attribute 30, 6
	.eabi_attribute 34, 1
	.eabi_attribute 18, 4
	.file	"test.c"
	.section	.rodata
	.align	2
.LC0:
	.ascii	"Hello World\000"
	.text
	.align	2
	.global	main
	.syntax unified
	.thumb
	.thumb_func
	.type	main, %function
main:
	@ args = 0, pretend = 0, frame = 0
	@ frame_needed = 1, uses_anonymous_args = 0
	push	{r7, lr}
	add	r7, sp, #0
	movw	r0, #:lower16:.LC0
	movt	r0, #:upper16:.LC0
	bl	puts
	movs	r3, #0
	mov	r0, r3
	pop	{r7, pc}
	.size	main, .-main
	.ident	"GCC: (Ubuntu/Linaro 5.3.1-14ubuntu2) 5.3.1 20160413"
	.section	.note.GNU-stack,"",%progbits

molloyd@molloyd-VirtualBox:~/temp$ arm-linux-gnueabihf-gcc -S test.c -o test1.s

molloyd@molloyd-VirtualBox:~/temp$ more test1.s

.arch armv7-a

.eabi_attribute 28, 1

.fpu vfpv3-d16

.eabi_attribute 20, 1

.eabi_attribute 21, 1

.eabi_attribute 23, 3

.eabi_attribute 24, 1

.eabi_attribute 25, 1

.eabi_attribute 26, 2

.eabi_attribute 30, 6

.eabi_attribute 34, 1

.eabi_attribute 18, 4

.align 2

.ascii "Hello World\000"

.global main

.syntax unified

.thumb

.thumb_func

.type main, %function

@ args = 0, pretend = 0, frame = 0

@ frame_needed = 1, uses_anonymous_args = 0

push {r7, lr}

add r7, sp, #0

movw r0, #:lower16:.LC0

movt r0, #:upper16:.LC0

bl puts

movs r3, #0

mov r0, r3

pop {r7, pc}

.ident "GCC: (Ubuntu/Linaro 5.3.1-14ubuntu2) 5.3.1 20160413"

.section .note.GNU-stack,"",%progbits

Each of the outputs are platform dependent. Thanks, Derek.

David Merchant December 23, 2017 at 4:20 am

Not sure where this question should go under what chapter. I would like to find a reference to implementing/ programming an I2C MEMS IMU, the BNO055. I can see it with I2Cdetect but for the life of me I can’t write a program that talks to it and gets data back. Any ideas? .thank you

Chapters

Exploring Raspberry Pi

Part I – Raspberry Pi Basics

Part II – Interfacing, Controlling, and Communicating

Part III – Advanced Interfacing and Interaction

3 Comments