Coral coralmw

## actionTable storage
no malloc, so no heap?

def. stack size: 0x2000 == 0.008 mb
sizeof(actionTable_t) == 20bytes
400ish entries if the stack was otherwise empty? a 1mb stack would allow for < 50000 entries
10mb stack space perhaps?

#### Monday

Expanded stack in the linkerscript to 0xA00000

## gist:67ebefa5c2756e4ae066
OCM: 256kb of on-chip memory

?I think? it's called ps7_ram_1_S_AXI_BASEADDR in the linker scripts, but that does not work.

on boot, dmesg has zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x5e880000
This address works. un-segmented.

#define COMM_BASE 0x5e880000

app_cpu1:

## Getting shared memory RP
http://fpga.org/2013/05/28/how-to-design-and-access-a-memory-mapped-device-part-one/

CMA: https://lwn.net/Articles/486301/

## Build env
Combining the red-pitaya-notes and the stock red pitaya FPGA bit file to create a suitable package to put on the red pitaya.

pretty much red-pitaya-notes (for the ubuntu os) + the FPGA from the stock os.
	no malloc, so no heap?

	def. stack size: 0x2000 == 0.008 mb
	sizeof(actionTable_t) == 20bytes
	400ish entries if the stack was otherwise empty? a 1mb stack would allow for < 50000 entries
	10mb stack space perhaps?

	#### Monday

	Expanded stack in the linkerscript to 0xA00000
	OCM: 256kb of on-chip memory

	?I think? it's called ps7_ram_1_S_AXI_BASEADDR in the linker scripts, but that does not work.

	on boot, dmesg has zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x5e880000
	This address works. un-segmented.

	#define COMM_BASE 0x5e880000

	app_cpu1:
	http://fpga.org/2013/05/28/how-to-design-and-access-a-memory-mapped-device-part-one/

	CMA: https://lwn.net/Articles/486301/
	Combining the red-pitaya-notes and the stock red pitaya FPGA bit file to create a suitable package to put on the red pitaya.

	pretty much red-pitaya-notes (for the ubuntu os) + the FPGA from the stock os.