How to extend memory Raspberry Pi Pico with sd card module - raspberry-pi

I'm trying to to extend memory storage in RaspberryPi Pico, because I need space for two exe files that are more than 2MB.
After connecting sd card module it is not showing in Windows. Can someone help me?

Related

Trying to run Raspberry-Pi image under QEMU, but VM memory is limited to 256MB

I want to build a time consuming package (mediapipe) on my Raspberry-Pi buster image under QEMU. So far, I've gotten the image to load and run (including with network connectivity); however, I'm limited to 256MB of storage, which just isn't enough to do much - especially build a mediapipe. Can someone explain why Raspbian images running under QEMU seem to be limited to 256MB?
I've seen some posts about people running with 512MB and even one with 1GB, but they don't seem to be very successful. Can anyone explain the reason for the restriction, and a potential fix?
The problem here is that a lot of people claim to be running "raspberry pi emulation in QEMU" when they're actually just running Raspbian userspace on top of a kernel for a different machine emulation. So it's easy to be confused if you look at several different tutorials that are really describing entirely different emulation setups. Look for what machine type they pass QEMU.
The "versatilepb" machine type gets used in a lot of tutorials, especially older ones, because it has been in QEMU a long time and it is possible to get it to work with the 1176 CPU that the classic Raspberry Pi boards used. This specific machine has a 256MB maximum memory size, because the real hardware it's emulating has that restriction (it's imposed by the way the physical memory address space is designed). This machine type will never be able to support more RAM, so if you need more then you should ignore any tutorial or setup that uses it.
More recent versions of QEMU really do emulate the actual raspberry pi hardware; these are the raspi0, raspi1ap, raspi2b, raspi3ap, raspi3b machine types. These will have the same amount of RAM as the real raspi hardware they're emulating (either 512MB or 1GB). The downside of these board models is that some of the device emulation is lacking features -- so older QEMU will often not correctly boot a newer kernel, and sometimes devices you would like to use are not present. Also, because the raspi boards hang their ethernet device off the USB controller, the only way to get ethernet on these QEMU models would also be to use a USB ethernet device, eg with:
-device usb-net,netdev=eth0 -netdev user,id=eth0
This probably needs a recent QEMU version to get a working USB controller.
I don't know if there are any tutorials/recipes for running Raspbian on top of the QEMU "virt" board. If there are, this would probably be the best experience, because the virt board permits lots of memory, PCI devices, virtio devices, and is well maintained.

Emulate a Raspberry Pi 1 or Zero in QEMU with the peripherals and the memory maps

Im trying to build a custom bare metal OS for Raspberry Pi 1 and Zero. I want to emulate any of these machines in QEMU but the only supported machines are raspi2 and raspi3.
I need to run it on a raspi1 or zero because I dont want to implement multicore support and in raspi1 and zero everything its easier.
Thanks!

How to use hard disk with raspberry pi?

I have a raspberry pi Zero and I wnat to use a 128GB ssd hard disk with it. How can I connect it to my raspberry pi.
Also be aware about this kickstarter project: https://www.kickstarter.com/projects/2073955313/pidrive-low-power-msata-ssd-for-the-raspberry-pi
Use a USB HDD enclosure.
Google

Redhat OS with notebook to Embedded controller RPI

Now I have the Redhat:Linux OS on notebook computer there are many applications inside that computer.
Reason that I need to port Redhat:OS to RPI that computer was installed Labview application and Labview with NiDAQmx , VISA I/O.(Now it's running fine on notebook with NI6008)
The question is how can I port that linux OS to my Raspberry PI with driver of RPI?(I need to know step by step)
NI does not support running LabVIEW standard on ARM processors - see What Linux Distributions Do National Instruments Drivers and Software Support?.
NI does have a Real Time modules that supports ARM processors, but not the Pi - see Targetting Raspberry PI.
You can still connect a NI6008 DAQ to your Pi and access the data using a driver such as Low Cost USB DAQ Driver for use with Raspberry Pi, but you will have to consume the data with an application written in a language other than LabVIEW (such as Python).

rpi v/s carambola --- rootfile system size

I am using following distribution for raspberry pi.
http://www.raspberrypi.org/downloads
http://downloads.raspberrypi.org/images/raspbian/2013-02-09-wheezy-raspbian/2013-02-09-wheezy-raspbian.zip
FOR rpi It is recommended to use >2GB card.
Also when i install it on my memory card size of root file system is about 1.4GB.
But dont you think it is too much size just for an root filesystem in EMBEDDED SYSTEM.
Is it possible for RPI to make a linux distribution with root file system with small size ?
Because most of the embedded system do not have this much memory.
like carambola have 8mb Flash & 32 MB RAM.
http://8devices.com/carambola
In this case carambola root filesystem (OPEN wrt) will fit in 8MB flash. How is it possible ?
Raspbian is a full on general purpose operating system, with the ability to run X windows, create a development environment, watch movies, play games, etc.
It also includes support for a great many devices you might want to connect via USB, such as networking devices, webcams, keyboards, mice, etc.
Many embedded systems are purpose built, with no options for adding/removing devices, nor options for running arbitrary programs. OpenWRT is a routing platform running on typical router hardware, and as such, can be MUCH smaller.
You could check out Buildroot for this, which also has been the base of OpenWrt (OpenWrt used for creating the rootfs for the linked Carambola). Buildroot also has support for raspberry pi, so you can easily create a pretty small rootfs with just a few of installed packages.