WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
TCB Q&A Forum / Re: How to Fill with zeroes the end of a disk?
« Last post by Rich on December 07, 2019, 04:45:06 PM »
Hi Santos
This should do what you want:
Code: [Select]
dd if=/dev/zero of=/dev/sdb ibs=1M obs=1M seek=200 count=10That should skip the first 200MB and then write 10MB of zeros.
22
Raspberry Pi / Re: Zero USB booting and remastering
« Last post by doctoranonymous on December 07, 2019, 03:42:42 PM »
OK, my bad! All I had to do was use ALL the piCore files from the FAT partition. It works now; booted to CLI, command prompt. Now, I guess I have to SSH in? Or, what? Can't unplug the usb can I? Can I plug a power wire into the power-usb port? And then unplug the data usb? and then plug in a keyboard? There has got to be a way to run the pi through my Kali-laptop? I dunno, I think my brain might be spent for today? Here is the CLI readout for my successful usbboot (USB Device Boot).

Code: [Select]
root@localhost:/# cd /usbboot/
root@localhost:/usbboot# ls
bin2c    boot    LICENSE  Makefile  Readme.md  win32
bin2c.c  debian  main.c   msd       rpiboot
root@localhost:/usbboot# sudo ./rpiboot -d boot
Waiting for BCM2835/6/7
Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7
Second stage boot server
File read: config.txt
File read: start.elf
File read: fixup.dat
File read: config.txt
File read: config.txt
File read: cmdline.txt
File read: kernel4922.img
File read: 9.0.3.gz
File read: bcm2708-rpi-0-w.dtb
File read: config.txt
Second stage boot server done
root@localhost:/usbboot#

Sorry so verbose, but I feel I accomplished something? Maybe someone will stumble across this string someday, and thank me for it? No sense re-inventing the wheel, right!?
23
Raspberry Pi / Re: Zero USB booting and remastering
« Last post by doctoranonymous on December 07, 2019, 03:17:32 PM »
Then, the README file says to do this: "To provide a filesystem there are many options,
you can build an initramfs into the kernel, add an initramfs to the boot directory or provide some
other interface to the filesystem.". This is probably--definitely--"out of my wheelhouse".

https://www.jootamam.net/howto-initramfs-image.htm , if, someday, I'm feeling ambitious? Anybody got a better plan?
24
Raspberry Pi / Help on loading hci_uart...
« Last post by imo on December 07, 2019, 03:01:59 PM »
Hi.
I am trying to install and run bluetooth/bluetooth low energy in a RPI zero w running piCore
I have installed bluetooth related modules, including bluetooth-4.9.22-piCore-v7.tcz
Then I ran the following commands:
sudo depmod
sudo modprobe hci_uart
   modprobe: module hci_uart not found in modules.dep
cat ....../config.txt
...
...
enable_uart=1
[PI3]
      #dtoverlay=pi3-disable-bt

I can see /usr/lib/modules/4.9.22-piCore-v7/kernel/drivers/bluetooth/hci_uart.ko
but it does not exists in modules.dep

If I:
tci-load -i  bluetooth-4.9.22-piCore-v7.tcz
it says "already installed"

Why does hci_uart is not in the modules.dep. Can I add it using vi text editor?

Thanks

Imo
25
Off-Topic - Tiny Core Lounge / Re: How Is Linux Used In An Enterprise Environment?
« Last post by Santos on December 07, 2019, 03:01:11 PM »
"Enterprise" it's and abstract concept, any company would use whatever suit it's needs. I have worked with companies or on an "Enterprise environment" some of them used Windows XP or software from 2012 without any kind of security update for the last 7 years. So, yeah if something is cheap and reliable enough sure it will be in a "Enterprise Environment". Maybe your are going to have very rock solid software and hardware on critical systems, like petrochemicals, health systems (like hospitals) and such.
26
Raspberry Pi / Re: Zero USB booting and remastering
« Last post by doctoranonymous on December 07, 2019, 02:50:57 PM »
And, minutiae number 2 (of 2); list of files I placed in "/usbboot/boot/" : bcm2708-rpi-0-w.dtb , bootcode.bin , cmdline.txt , config.txt , fixup.dat , kernel4922.img , kernel4922v7.img , LICENCE.brioadcom , README , RELEASE , start.elf . These 11 QTY files, are all the files that I put in the boot folder. Give a shout if you see something else that I should have put in. But, I will probably put the whole piCore in, at some point this evening, as it seems I am, lately, motivated to get this thing working exactly how I want it to work.

27
TCB Q&A Forum / How to Fill with zeroes the end of a disk?
« Last post by Santos on December 07, 2019, 02:50:51 PM »
Hi there!

I want to erase the end of a memory flash, by the end I mean the last blocks. Is there any way to choose one specific "block", like 100MB-250MB or just the last 10MB of the memory flash?

I've tried, but is going to work just for the first megabyte:

dd if=/dev/zero of=/dev/sdb bs=1048576 count=1

The option 'seek' works for just a file (or ignore such amount of input data, right?)

Thank you for your help.
28
Raspberry Pi / Re: Zero USB booting and remastering
« Last post by doctoranonymous on December 07, 2019, 02:38:10 PM »
OK, minutiae Number 1 (of 2). USB Device Boot (wherein Kali-Linux CLI commands, with usbboot utility, "squirts" the bootcode.bin into the r-pi-zero "data+power" micro-USB port).

Code: [Select]
root@localhost:~# cd /usbboot
root@localhost:/usbboot# sudo ./rpiboot -d boot
Waiting for BCM2835/6/7
Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7
Second stage boot server
File read: config.txt
File read: start.elf
File read: fixup.dat
File read: config.txt
File read: config.txt
File read: cmdline.txt
File read: kernel4922.img
File read: bcm2708-rpi-0-w.dtb
File read: config.txt
Second stage boot server done
root@localhost:/usbboot#

So, this gets me past rainbow screen, and then to "black-screen-with-giant-raspberry-logo". As I said, in one of the two marathon posts, above, it might be my fault because I didn't put enough files in the "/boot/" folder. (no reason to skimp, as 50 MB isn't even a drop in most buckets, nowadays).
29
Raspberry Pi / Re: Zero USB booting and remastering
« Last post by doctoranonymous on December 07, 2019, 12:58:10 PM »
OK, not the "minutiae" post yet. That will be one more below (I think). I guess things "roll out", as they develop (evolve?), as some of these boot methods are not very old (about a year and a half). R-pi.org has this documentation for possible boot sequences, but it still seems a bit abstruse and arcane to me. About six months ago I was sniffing around some githubs that were working (5 years ago) on freeing up the VPU/QPU/GPU stuff. I am not sure if it ever became FOSS (to Stallman's standards!). Luckily, as a biologist, nobody holds me to the standards of a FOSS purist, so I can "feel" my way through the ethical morass. (I'll probably end up close to the "purists" perspective, anyway!). Anyway, these guys were "bare metal" and I was feeling bare metal just reading them. I guess I forgot most of it, though, and I certainly didn't get to read all the official documentation on boot modes, since I have just found those, yesterday.

Anyhoo, https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/ and https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/bootflow.md are useful, here.

So, here is an interesting notion : https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/device.md" USB device boot mode : When this boot mode is activated (usually after a failure to boot from the SD card), the Raspberry Pi puts its USB port into device mode and awaits a USB reset from the host.".

So, all my r-pi zeros (slave/devices) could be "sd-boot failed", then wait for the one that is host, to USB-reset them?

USB Host Bootmode, is unavailable to pi zero, as far as I know? https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/host.md .

So, since I ruled out one official method, and identified a possible suitability for another official method, let us focus on the latter:

"Example code showing how the host needs to talk to the Pi can be found here." . Here goes here => https://github.com/raspberrypi/usbboot , which is, exactly where I went yesterday, when I got my pi booted to the large-raspberry-black-screen.

Not quite CLI, which, if I am smart enough, I might find today!

So, in the read-me file of usb-boot utility, there is a section "Running your own (not MSD) build[/u]". I think this is what I want to do. Now, how much do I remember about tinycore initramfs, or for that matter, any initramfs? 6 months ago I read, but definitely forgot by now. Can't remember if arms have an init?

Anyway, perhaps this website will help; seems to deal with the issue of setting up a filesystem for the usb-boot device? https://dev.webonomic.nl/how-to-run-or-boot-raspbian-on-a-raspberry-pi-zero-without-an-sd-card

"March 22nd, 2018 : Then you could burn the image to an USB flash drive, but we gonna do something clever, we gonna setup a loop device.

Code: [Select]
cd ~
 sudo losetup -P /dev/loop0 Downloads/2018-03-13-raspbian-stretch-lite.img

Then we need two mountpoints for the boot and rootfs directories. Let’s create them.

Code: [Select]
sudo mkdir -p /pi/{boot,root}  "

I don't know. I guess I have to read the rest of that post? Unless anybody else out there knows more about what I am doing than I do? If so, please let me know, so I don't break anything.
30
Raspberry Pi / Re: piCore-11
« Last post by uli on December 07, 2019, 12:01:26 PM »
Hi,

installed it on a 3B+ and it works out of the box. Great work. Thanks.

I dared to mess a bit with the boot files to allow for a (somewhat simplistic) dual boot with Rasbian, plus, went for httplist to get rid of the root partition and load extensions from the web instead.
However, that way I found that I couldn't reliably connect to the networks. Turned out that eth0 is not available in this case.

Seems that a waitusb as a kernel parameter solved it for now. Generally at least, no statistics on rare failures yet.

So, I am happy I could solve it. Assuming now that issue is an inherent one of the current build, and not due to my messing around. Unless you tell me otherwise...

Though, I am wondering whether the boot sequence should perhaps make sure that we are waiting for eth0 becoming available first, then going for a dhcp request and onwards.

Since I would guess there are very few people these days who wish to run their 3B+ without networks, I would think trying to harden the startup procedure for everyone might perhaps be beneficial. I know by far too little about the Raspi world (yet) to dig into these things myself, but perhaps someone might have a good idea, or tell me that I caused that issue myself by messing around with boot files...

Uli

Pages: 1 2 [3] 4 5 ... 10