Recent Posts

1

Raspberry Pi / Re: bridge-utils, net-sched and net-usb on piCore 9.0.3

« Last post by Јаневски on Today at 01:36:58 PM »

I have managed to install net-usb with:

Code: [Select]

$ tce-load -i -w net-usb-4.9.22-piCore-v7

net-bridging and net-sched remain.

2

Extension requests / Re: Veracrypt?

« Last post by Rich on Today at 12:33:03 PM »

Hi Cypherpunky Brewster

I have been struggling with making this work, and so far have failed.

If you post what is giving you problems, someone here may be able to help you. If you are getting compiler errors, post
a copy of the error messages.

3

Extension requests / Re: Veracrypt?

« Last post by Cypherpunky Brewster on Today at 11:53:11 AM »

perhaps you could have a go at making the extension yourself?

I have been struggling with making this work, and so far have failed. Either I convince someone to do this (it should be a simple edit of the existing Truecrypt package) or I will have to go back to using Ubuntu. A shame, really; tiny core does everything I need to do other than accessing my Veracrypt partition.    

4

Raspberry Pi / Re: dwc_otg issues

« Last post by jefferee on Today at 09:57:14 AM »

The Pi's usb is just buggy, that's been known for years. You probably knew about it before deciding to buy one.

See
https://github.com/raspberrypi/linux/issues/739
The very same thing reported in 2014.

Yes, I'm well aware that OTG in general is a weak point for what I am trying to do here. Dumping the R-Pi for something that has better (i.e., not OTG) usb support is definitely on the table.

5

Raspberry Pi / Re: dwc_otg issues

« Last post by jefferee on Today at 09:51:26 AM »

Thanks, Rich. I'll have a look.

So it looks like we get into this case of

Code: [Select]

switch (st->fsmand hit the BUG() statement on line 2438.

Code: [Select]

case FIQ_NP_SPLIT_LS_ABORTED:
/* A few cases can cause this - either an unknown state on a SSPLIT or
* STALL/data toggle error response on a CSPLIT */
if (hcint.b.stall) {
handle_hc_stall_intr(hcd, hc, hc_regs, qtd);
} else if (hcint.b.datatglerr) {
handle_hc_datatglerr_intr(hcd, hc, hc_regs, qtd);
} else if (hcint.b.bblerr) {
handle_hc_babble_intr(hcd, hc, hc_regs, qtd);
} else if (hcint.b.ahberr) {
handle_hc_ahberr_intr(hcd, hc, hc_regs, qtd);
} else {
local_fiq_disable();
BUG();
}
break;
Throwing FIQ_NP_SPLIT_LS_ABORTED: into da Google shows the following bug report, which declares it fixed and closed in the 4.9 kernel. Guess it's time to try piCore 9.0.3!
https://github.com/raspberrypi/linux/issues/1506

6

Raspberry Pi / Re: dwc_otg issues

« Last post by curaga on Today at 09:48:47 AM »

The Pi's usb is just buggy, that's been known for years. You probably knew about it before deciding to buy one.

See
https://github.com/raspberrypi/linux/issues/739
The very same thing reported in 2014.

7

Raspberry Pi / Re: dwc_otg issues

« Last post by jefferee on Today at 08:55:04 AM »

Thanks, Rich. I'll have a look.

8

Raspberry Pi / Re: Pi3 -> Pi3 communication over GPIO

« Last post by jefferee on Today at 08:49:25 AM »

What I ended up doing, for anyone (probably me) googling this later:

Checked mmcblk0p1/config.txt on both Pis, to ensure both had the lines

Code: [Select]

enable_uart=1to enable the serial console, and

Code: [Select]

dtoverlay=pi3-disable-btto disable the bluetooth (this line is specific to Pi 3). I did this so that the console can be run through the (better) /dev/ttyAMA0 interface, rather than /dev/ttyS0.
In 8.1.4, both lines were included in config.txt by default.

Modified mmcblk0p1/cmdline3.txt on both Pis:
Changed console entries on the server to

Code: [Select]

console=ttyAMA0,115200 console=tty1and removed all

Code: [Select]

console=entries on the client.


Modified /opt/bootlocal.sh, to change terminal startup.
Commented out the stock serial terminal startup line

Code: [Select]

/usr/sbin/startserialtty &on both machines.
On the server only, added the line

Code: [Select]

/opt/serialtty.sh &(we'll get to that script next).

On the server, created a script /opt/serialtty.sh

Code: [Select]

#!/bin/sh

# Start serial terminal on Raspberry Pi
while :
do
  /sbin/getty -L /dev/ttyAMA0 115200 vt100
done
This forces the console to use /dev/ttyAMA0, so it assumes bluetooth is disabled.

...et voila!

9

Off-Topic - Tiny Core Lounge / Re: Favourite portable windows based ssh client

« Last post by Lee on Today at 08:37:46 AM »

I've dabbled with the BitVise SSH client a little and it seems to work ok, although it's not in danger of becoming my favorite.  The client is free-to-use and has a command line switch that tells it not to use the Windows registry but I don't know if the application itself has to be -installed-.

I use PortaPuTTY, although lately I primarily use it as a legacy telnet client.  What do you find annoying about PuTTY?

For most of my Windows ssh'ing needs I use openssh under Cygwin - but I wouldn't exactly call that "portable".

10

Raspberry Pi / Re: dwc_otg issues

« Last post by Rich on Today at 08:35:06 AM »

Hi jefferee
I think you need to get the source package for your kernel and take a look around line 2438 of:
drivers/usb/host/dwc_otg/dwc_otg_hcd_intr.c
to get a better idea of what the actual error is.