• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

[ArmbianBananaPi] - script.bin missing
0

6 posts in this topic

Recommended Posts

 

Hello to all!

I'm using Armbian on my BananaPi board.

I've the following version:


 

ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.15-sunxi

BOARD=bananapi
BOARD_NAME="Banana Pi"
VERSION=5.35
LINUXFAMILY=sunxi
BRANCH=next
ARCH=arm
IMAGE_TYPE=user-built
BOARD_TYPE=conf
INITRD_ARCH=arm
KERNEL_IMAGE_TYPE=zImage

 

I need to follow these instructions to wire a radio on the board:

 

https://www.mysensors.org/build/orange

 

But I cannot find the script.bin file. Why?

I can remember the file was here on old releases.

 

Any help or suggestion?

 

Thanks,

 

Simon

Share this post


Link to post
Share on other sites
13 hours ago, Igor said:

 

Good morning,

That's a great point to start with, and as always, first rule, RTFM, you're absolutely right.

I've started reading it and it's a little complicated. The part that I think it's referred on what I need is:

 

Quote

 

### spi0

Activates SPI controller 0 to use it with other overlays and sets up the pin multiplexing for it

SPI 0 pins (MOSI, MISO, SCK, CS0, CS1): PI12, PI13, PI11, PI10, PI14

### spi1

Activates SPI controller 1 to use it with other overlays and sets up the pin multiplexing for it

SPI 1 pins (MOSI, MISO, SCK, CS0): PI18, PI19, PI17, PI16

### spi2

Activates SPI controller 2 to use it with other overlays and sets up the pin multiplexing for it

SPI 2 pins a (MOSI, MISO, SCK, CS0): PC21, PC22, PC20, PC19
SPI 2 pins b (MOSI, MISO, SCK, CS0): PB16, PB17, PB15, PB14

Parameters:

param_spi2_bus_pins (char)
        SPI bus 2 pinmux variant
        Optional
        Default: a
        Supported values: a, b
        Determines what pins SPI bus 2 is exposed on if SPI 2 is used

### spi-add-cs1

Activates SPI chip select 1 on SPI controller 0
This overlay is required for using chip select 1 with other SPI overlays

SPI 0 CS1 pin: PI14

### spi-jedec-nor

Activates MTD support for JEDEC compatible SPI NOR flash chips on SPI bus
supported by the kernel SPI NOR driver

SPI 0 pins (MOSI, MISO, SCK, CS0, CS1): PI12, PI13, PI11, PI10, PI14
SPI 1 pins (MOSI, MISO, SCK, CS0): PI18, PI19, PI17, PI16
SPI 2 pins a (MOSI, MISO, SCK, CS0): PC21, PC22, PC20, PC19
SPI 2 pins b (MOSI, MISO, SCK, CS0): PB16, PB17, PB15, PB14

Parameters:

param_spinor_spi_bus (int)
        SPI bus to activate SPI NOR flash support on
        Required
        Supported values: 0, 1, 2

param_spinor_spi_cs (int)
        SPI chip select number for SPI NOR connected to SPI bus 0
        Optional
        Default: 0
        Supported values: 0, 1
        Using chip select 1 on SPI 0 requires using "spi-add-cs1" overlay

param_spinor_max_freq (int)
        Maximum SPI frequency
        Optional
        Default: 1000000
        Range: 3000 - 100000000

### spi-spidev

Activates SPIdev device node (/dev/spidevX.Y) for userspace SPI access,
where X is the bus number and Y is the CS number

SPI 0 pins (MOSI, MISO, SCK, CS0, CS1): PI12, PI13, PI11, PI10, PI14
SPI 1 pins (MOSI, MISO, SCK, CS0): PI18, PI19, PI17, PI16
SPI 2 pins a (MOSI, MISO, SCK, CS0): PC21, PC22, PC20, PC19
SPI 2 pins b (MOSI, MISO, SCK, CS0): PB16, PB17, PB15, PB14

Parameters:

param_spidev_spi_bus (int)
        SPI bus to activate mcp2515 support on
        Required
        Supported values: 0, 1, 2

param_spidev_spi_cs (int)
        SPI chip select number for SPIdev on SPI bus 0
        Optional
        Default: 0
        Supported values: 0, 1
        Using chip select 1 on SPI 0 requires using "spi-add-cs1" overlay

param_spidev_max_freq (int)
        Maximum SPIdev frequency
        Optional
        Default: 1000000
        Range: 3000 - 100000000

 

 

Due I'll need to connect on this board two radio (one NRF24L01+ and one RFM69), I fear to make some damages, so I ask here.

I would start with one radio first, the RFM69. But here comes the first question it's not totally clear for me:

 

1. Is the BananaPi able to have two radio connected on the GPIO?

 

Seems yes if the above doc speeks about SPI 0 - 1 - 2 all with required MOSI, MISO, SCK, CS....

 

But I've read somewhere for RPi the following:

Quote

Adding /dev/spidev1.0 is required since /dev/spidev0.0 is used for the onboard NAND flash

 

2. I'ts valid for BananaPi as well?

 

BTW then, let's start with the first radio assuming I can start with bus0. The overlay should look like:

overlays=spi-spidev
param_spidev_spi_bus=0

That should create a "/dev/spidev***" device.

 

This should give me those connections GPIO available:

MOSI: PI12 -> CON3-PORT19
MISO: PI13 -> CON3-PORT21
SCK: PI11 -> CON3-PORT23
CS: PI10 -> CON3-PORT24

 

Then I'm missing the power 3.3v (CON3-PORT01), ground (CON3-PORT06) and IRQ, which should be ok any normal PIN (i.e. CON3-PORT22).

 

Until here makes it sense??

 

Sorry, but as written above I fear I could make some mistrakes and damage the devices.

 

Assuming the above works, how can then I add a second spidev?

This is something I cannot understand from the documentation.

 

Many thanks,

 

Simon

 

 

Share this post


Link to post
Share on other sites

The banana pi only has 1 SPI Unless I'm mistaken. I used SPI some time ago and IIRC simply adding spi-spidev to the overlay did the trick. The Banana pi has no Nand.

 

 

Hope this helps

Share this post


Link to post
Share on other sites
4 hours ago, vlad59 said:

The banana pi only has 1 SPI Unless I'm mistaken. I used SPI some time ago and IIRC simply adding spi-spidev to the overlay did the trick. The Banana pi has no Nand.

 

 

Hope this helps

 

THANKS!

I'll give it a try and let you know ;)

 

Simon

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

0

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.