Pi-based Co-Pro on the cheap - 100MHz 6502 for £10? (now 274MHz)

[marcusjambler]

Call me paranoid, but could you put a Linux distribution on the card you are intending to use for PiTubeDirect, and try that in the Pi 3. Doesn't matter what. Anything to demonstrate the Pi 3 can boot off that specific card (which I assume is FAT32 formatted?)

I'll get this done when I get home tonight Dave

[marcusjambler]

FAT32 correct

[marcusjambler]

Dave

I have installed ( via Etcher ) a small ubuntu core distro onto the 1Gb card used previously for the pitube direct software.
Both the Pi2 and Pi3 boot to the config prompt.

[hoglet]

I have installed ( via Etcher ) a small ubuntu core distro onto the 1Gb card used previously for the pitube direct software.
Both the Pi2 and Pi3 boot to the config prompt.

Gosh, I'm running out of ideas.

And you are able to see some output from the serial console from Ubuntu in the Pi 3?

[marcusjambler]

Yes, and the interesting thing here is that its not garbage whereas with raspbian it is.

[hoglet]

Yes, and the interesting thing here is that its not garbage whereas with raspbian it is.

Have you tried an older release, like Anaconda?
https://github.com/hoglet67/PiTubeDirect/releases

[marcusjambler]

I tried booting the Pi3 with the other 1Gb card with Cobra diamondback release on immediately afterward and nothing... just hangs immediately. No serial info whatsoever... Then back to the Ubuntu 1Gb card... boots to config prompt.

[marcusjambler]

Have you tried an older release, like Anaconda?

I'll do that next

[marcusjambler]

Anaconda release is not booting... Its looking like this Pi3 will only boot from cards that are imaged

[KenLowe]

A couple of things to note: the serial port is just 3V signals, so might not be compatible with a given serial port. I've used a little level shifter to get the serial signals up to 5V. That meant taking a fourth connection to the board, for the 5V reference.

If you had a spare Pi, that will of course have a compatible 3V serial port on its GPIOs, so you could use that (running linux, for example.)

Yes. I suspect my serial adaptors are of the 5v variety. I've ordered up a specific RaspberryPI serial interface from ebay that claims to work with Win10 x64. Time will tell. I do also have a spare Raspberry PI. I'll look into setting these up back to back tonight. Thanks for the tip.

Another point: it's easy to get the sense of Rx and Tx wrong. So try all the combinations! At one point, and I think it's been fixed, Kjell's adapter was mislabelled.

I guess it's trying to interpret what the labels mean! Is the label referring to where it's come from, or where it's going to????
I was getting nothing at all initially, so tried swapping the RX / TX lines and then started seeing some data, but nothing that made any sense. I had the comms parameters set to 115200/8/N/1, which I believe to be correct for the Pi? I've tried some other baud rates, but none I've tried seem to work, hence I suspect a voltage issue. I'm using PuTTY as my terminal emulator. Can anyone recommend anything better?

Thanks
Ken.

Perhaps a bit late, but my new USB / serial adaptor arrived today, and after a bit of messing around with Win10 x64 drivers (I think my adaptor is using a fake prolific chipset. It was cheap, so I was half expecting that) I've got it running and I can now see diagnostic information from the Pi Zero. Let me know if you still need any info from my system.

[dp11]

Can you check there are no partitions on the sdcard.

[marcusjambler]

Since imaging ubuntu onto it (1Gb card) windows is reporting 126mb

[dp11]

Marcus, if you are using windows 10 could right click on the windows icon and select disk management.

If you have partitions on the card can you delete the extra volumes and then reformat the card ( FAT32) and put diamond back on.

[marcusjambler]

Certainly... I will do that tonight before I go out

[Elminster]

Question. Is there any plans, thoughts or possibilities for the 'W' bit of Pi Zero in pitubedirect? W is an extra £5 but if never going to need the W bit I might as wel save my self the costs of 1-2 cups of coffee.

[marcusjambler]

Hi

Yes finally getting serial boot info from this Pi3

PiZero PiB+ Pi2 & Pi3 logs

Code: Select all

enable_MMU_and_IDCaches


**********     Raspberry Pi BBC Micro Coprocessor     **********


    FIRMWARE_VERSION : 573f5f3d 
         BOARD_MODEL : 00000000 
      BOARD_REVISION : 00900093 
   BOARD_MAC_ADDRESS : e2eb27b8 63613c76 
        BOARD_SERIAL : 4be2763c 00000000 
           EMMC_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
           UART_FREQ :      3.000 MHz   1000.000 MHz   1000.000 MHz
            ARM_FREQ :   1000.000 MHz   1000.000 MHz   1000.000 MHz
           CORE_FREQ :    400.000 MHz    400.000 MHz    400.000 MHz
            V3D_FREQ :    300.000 MHz    300.000 MHz    300.000 MHz
           H264_FREQ :    300.000 MHz    300.000 MHz    300.000 MHz
            ISP_FREQ :    300.000 MHz    300.000 MHz    300.000 MHz
          SDRAM_FREQ :    450.000 MHz    450.000 MHz    450.000 MHz
          PIXEL_FREQ :      0.000 MHz  -1894.967 MHz  -1894.967 MHz
            PWM_FREQ :      0.000 MHz    500.000 MHz    500.000 MHz
           CORE TEMP :  23.94 °C
        CORE VOLTAGE :   1.35 V
     SDRAM_C VOLTAGE :   1.20 V
     SDRAM_P VOLTAGE :   1.20 V
     SDRAM_I VOLTAGE :   1.20 V
            CMD_LINE : dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708.boardrev=0x900093 bcm2708.serial=0x4be2763c smsc95xx.macaddr=B8:27:EB:E2:76:3C bcm2708_fb.fbswap=1 bcm2708.uart_clock=3000000 bcm2708.disk_led_gpio=47 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000  copro=0 copro1speed=3 tube_delay=0
               COPRO : 0
Tube ULA sample delay  0
emulator speed 3
Copro Memory size 0
Raspberry Pi Direct 0 65C02 (65tube) Client
enable_MMU_and_IDCaches


**********     Raspberry Pi BBC Micro Coprocessor     **********


    FIRMWARE_VERSION : 573f5f3d 
         BOARD_MODEL : 00000000 
      BOARD_REVISION : 00000010 
   BOARD_MAC_ADDRESS : eceb27b8 6361ee02 
        BOARD_SERIAL : 79ec02ee 00000000 
           EMMC_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
           UART_FREQ :      3.000 MHz   1000.000 MHz   1000.000 MHz
            ARM_FREQ :    700.000 MHz    700.000 MHz    700.000 MHz
           CORE_FREQ :    350.000 MHz    350.000 MHz    350.000 MHz
            V3D_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
           H264_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
            ISP_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
          SDRAM_FREQ :    400.000 MHz    400.000 MHz    400.000 MHz
          PIXEL_FREQ :      0.000 MHz  -1894.967 MHz  -1894.967 MHz
            PWM_FREQ :      0.000 MHz    500.000 MHz    500.000 MHz
           CORE TEMP :  20.72 °C
        CORE VOLTAGE :   1.20 V
     SDRAM_C VOLTAGE :   1.20 V
     SDRAM_P VOLTAGE :   1.20 V
     SDRAM_I VOLTAGE :   1.20 V
            CMD_LINE : dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708.boardrev=0x10 bcm2708.serial=0x79ec02ee smsc95xx.macaddr=B8:27:EB:EC:02:EE bcm2708_fb.fbswap=1 bcm2708.uart_clock=3000000 bcm2708.disk_led_gpio=47 bcm2708.disk_led_active_low=0 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000  copro=0 copro1speed=3 tube_delay=0
               COPRO : 0
Tube ULA sample delay  0
emulator speed 3
Copro Memory size 0
Raspberry Pi Direct 0 65C02 (65tube) Client
enable_MMU_and_IDCaches


**********     Raspberry Pi BBC Micro Coprocessor     **********


    FIRMWARE_VERSION : 573f5f3d 
         BOARD_MODEL : 00000000 
      BOARD_REVISION : 00a01041 
   BOARD_MAC_ADDRESS : e7eb27b8 6361cdb6 
        BOARD_SERIAL : 36e7b6cd 00000000 
           EMMC_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
           UART_FREQ :      3.000 MHz   1000.000 MHz   1000.000 MHz
            ARM_FREQ :    900.000 MHz    900.000 MHz    900.000 MHz
           CORE_FREQ :    350.000 MHz    350.000 MHz    350.000 MHz
            V3D_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
           H264_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
            ISP_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
          SDRAM_FREQ :    450.000 MHz    450.000 MHz    450.000 MHz
          PIXEL_FREQ :      0.000 MHz  -1894.967 MHz  -1894.967 MHz
            PWM_FREQ :      0.000 MHz    500.000 MHz    500.000 MHz
           CORE TEMP :  23.41 °C
        CORE VOLTAGE :   1.31 V
     SDRAM_C VOLTAGE :   1.20 V
     SDRAM_P VOLTAGE :   1.20 V
     SDRAM_I VOLTAGE :   1.20 V
            CMD_LINE : dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x36e7b6cd smsc95xx.macaddr=B8:27:EB:E7:B6:CD bcm2708_fb.fbswap=1 bcm2709.uart_clock=3000000 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3ea00000 vc_mem.mem_size=0x3f000000  copro=0 copro1speed=3 tube_delay=0
               COPRO : 0
Tube ULA sample delay  0
emulator speed 3
Copro Memory size 0
main running on core 0
starting core 1
starting core 2
starting core 3
Raspberry Pi Direct 0 65C02 (65tube) Client
enable_MMU_and_IDCaches


**********     Raspberry Pi BBC Micro Coprocessor     **********


    FIRMWARE_VERSION : 573f5f3d 
         BOARD_MODEL : 00000000 
      BOARD_REVISION : 00a02082 
   BOARD_MAC_ADDRESS : eaeb27b8 6361bb95 
        BOARD_SERIAL : 41ea95bb 00000000 
           EMMC_FREQ :    250.000 MHz    250.000 MHz    250.000 MHz
           UART_FREQ :     48.000 MHz   1000.000 MHz   1000.000 MHz
            ARM_FREQ :   1200.000 MHz   1200.000 MHz   1200.000 MHz
           CORE_FREQ :    400.000 MHz    400.000 MHz    400.000 MHz
            V3D_FREQ :    300.000 MHz    300.000 MHz    300.000 MHz
           H264_FREQ :    300.000 MHz    300.000 MHz    300.000 MHz
            ISP_FREQ :    300.000 MHz    300.000 MHz    300.000 MHz
          SDRAM_FREQ :    450.000 MHz    450.000 MHz    450.000 MHz
          PIXEL_FREQ :      0.000 MHz  -1894.967 MHz  -1894.967 MHz
            PWM_FREQ :      0.000 MHz    500.000 MHz    500.000 MHz
           CORE TEMP :  34.32 °C
        CORE VOLTAGE :   1.30 V
     SDRAM_C VOLTAGE :   1.20 V
     SDRAM_P VOLTAGE :   1.20 V
     SDRAM_I VOLTAGE :   1.20 V
            CMD_LINE : dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa02082 bcm2709.serial=0x41ea95bb smsc95xx.macaddr=B8:27:EB:EA:95:BB bcm2708_fb.fbswap=1 bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3ea00000 vc_mem.mem_size=0x3f000000  copro=0 copro1speed=3 tube_delay=0
               COPRO : 0
Tube ULA sample delay  0
emulator speed 3
Copro Memory size 0
main running on core 0
starting core 1
starting core 2
starting core 3
Raspberry Pi Direct 0 65C02 (65tube) Client
>> 
>> [0K
[3Cð

I'll try hooking it up to a master

[marcusjambler]

Awesome... Pi3 now running tubeelt soak test

[dp11]

well done !

I know of no plans to do anything with the "W" part . It is likely to be very difficult.

[hoglet]

Awesome... Pi3 now running tubeelt soak test

What do the think the problem actually was then?

[Elminster]

I know of no plans to do anything with the "W" part . It is likely to be very difficult.

Good answer as I ordered the standard Zero. Will test that on my misbehavinging Beebs.

[dp11]

I'd also have to splash the cash aready broken the bank buying 2 pizeros

[marcusjambler]

I think it was something in the MBR causing the Pi3 to freeze on entry and just formatting it with the standard right click formatter in Win10 didnt correct it. (This is on 2 1Gb cards from different sources.) The issue resolved when I combined the whole disk into a 'simple volume' in disk management and then formatted it again to FAT32. I have yet to try this on the 2nd 1Gb card.

[marcusjambler]

Actually that didnt work on the 2nd card...
I had to image Ubuntu core onto the card and then go into Disk management and delete each volume and create a simple volume with max space.
Then format to FAT32 and then copy across Cobra Diamond Back.
Now both cards are working on Pi3.

[fordp]

A lot of other projects recommend using the official SD Card formatter program:
https://www.sdcard.org/downloads/format ... a_windows/

[hoglet]

Just a quick note to say there has been a release candidate of Diamondback available for a few days:
https://github.com/hoglet67/PiTubeDirect/releases

Only two downloads so far, and I think one was me!

This has just two changes from Cobra:
- A fix for the small bug in the GPU code that affected some users (those with glitchy nTUBE signals, so now you know!)
- A new elk_mode configuration option that patches the Z80 and 80x86 Client ROMs so they work with the Elk

The Client ROM patches for the Electron:
- are sufficient to get CP/M working properly
- are necessary, but not sufficient, to get DOSPlus working properly

The problem with DOSPlus is that the DOSPlus boot disks contain a file called 6502.sys that is uploaded to the host. There's a disassembly of it here (do View Source) and this also contains references to the tube registers which need changing. There are other hardware references here, like the FDC and User Port, which might be more of a challenge, especially as DOSPlus runs in Mode 0 (or is it 3?).

If anyone is interested in running DOSPlus on an Elk then give me a shout and I can try to port this (unless it's already been done?).

Dave

[Elminster]

Any differentto the beta diamondback I am running already? Just waiting for my new level shifters, new pi zero arrived on Saturday. Want to prove tube on other beebs does or doesn't work, removing all the cables.

[hoglet]

Any differentto the beta diamondback I am running already? Just waiting for my new level shifters, new pi zero arrived on Saturday. Want to prove tube on other beebs does or doesn't work, removing all the cables.

It just has the elk_mode config option added.

Dave

[KenLowe]

If we're looking for guilty parties, guess I was the other downloader. Certainly fixed my glitchy nTube!

[guidol]

Just to clarify, when you say it "Fails" on Ctrl-Break, so you mean:
- the Beeb doesn't detect the Co Pro at all (i.e. no Tube banner)
- the Beeb does detect the Co Pro, but the language transfer hangs (i.e. no > prompt)
What's the behaviour on an normal break?

Hi,
today I did get my Pi-Zero-W - so I can switch from Pi3 to the Pi-Zero-W...

I did test
- PiTubeDirect_20170607_1812_dmb
- PiTubeDirect_20170612_1624_dmb
and
- PiTubeDirect_Boa (swapped the 3 files and the config-file for Pi-Zero-W)

With the Cobra-Releases the language transfer seem to hang = no > prompt after Ctrl-BREAK.
With only BREAK I do allways get the * prompt

With the Boa-Release it works on most "Cores", but on the Z80-Core (*FX 151,230,4) and the 80286-Core (FX 151,230,8) I do only get a * promt after BREAK, but no normal > prompt after Ctrl-BREAK.

I do wonder why only the Boa-Release has only a PiZero-Kernel (kernelrpizero.img)

Whats - for this time - the best Release to use a Pi_Zero-W?

I couldnt solder the connector myself to to a normal Pi-Zero, so I ordered the Pi-Zero-W at http://www.buyzero.de with header already installed.

PS: I got the Pi3 / Pi-Zero-W in my Master with the internal Master-converter, but with the Pi-Zero-W I didnt get anything on the serial debug line
With the Pi3 I could see the Messages...so I didnt changed anything on the serial line (CP2102)

[dp11]

Please wipe the SDCARD and use the diamondback release. We have changed the build structure to be simpler so less files are needed.