SAMB11 Initialization failed

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hey Guys,

i want to connect the samb11 mr210ca board with my µC atsamd21j18a.

i have connected the board with spi sercom 3 and uart.

if i want to write the ble_device_init() in my main(), my debug port sends me a message like "Please check the power and connection / hardware connector".

 

in this function i become this message: ble_manager.c

 

/* Initialize the BLE */
static void ble_init(at_ble_init_config_t * args)
{
    /* Initialize the platform */
    DBG_LOG("Initializing BTLC1000"); // this comes
    
    /* Init BLE device */
    if(at_ble_init(args) != AT_BLE_SUCCESS)
    {
        DBG_LOG("BTLC1000 Initialization failed");
        DBG_LOG("Please check the power and connection / hardware connector");    // this comes after a timeout ~ 10sec.
        while(1);
    }
}

 

could someone please help me?!

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi,

 

First thing that caught my eye were the two capacitors around Y1.  I don't have those in my design, not sure if they're required or not... my MCU is working fine, except for ULP current drain being excessive above 3 V.  Here's a link to my ATSAMB11-MR210 schematic, in case it's helpful.  I'm also attaching a copy of my working prototype code, which works well including UART logging via a 5V TTL USB adapter (different use case than yours). This is a modified startup template app.  I'm using a 10K resistor on Chip Enable, but doubt that's an issue.

 

Hopefully my working hardware and firmware will get you moving in the right direction.  It wasn't clear from your question exactly what problem you're having or how far along you are.

 

Be sure you are using the latest ASF version.

 

Rick

 

 

 

 

 

 

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Scratliner wrote:

   if(at_ble_init(args) != AT_BLE_SUCCESS)

    {
        DBG_LOG("BTLC1000 Initialization failed");
        DBG_LOG("Please check the power and connection / hardware connector");    // this comes after a timeout ~ 10sec.
        while(1);
    }

So, if you're getting that message, you know that the return value from at_ble_init() was not AT_BLE_SUCCESS - don't you?

 

But you don't know what the return value was - so why don't you find out?

That should tell you something!

 

You could also use the debugger to step into at_ble_init()  - and see where, exactly, it fails ...

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
Last Edited: Mon. Sep 25, 2017 - 05:05 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello everyone,

 

i am having a problem in the communication between the Atmel BTLC1000-XSTK Xplained Pro, after i built the solution, the flash programming works also perfectly, but i dont get the blue circle on the smartphone app when i run the demo (see the user guide: https://github.com/avrxml/asf/bl...).

 

Can someone please help me?

Best regards

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:

Scratliner wrote:

   if(at_ble_init(args) != AT_BLE_SUCCESS)

    {
        DBG_LOG("BTLC1000 Initialization failed");
        DBG_LOG("Please check the power and connection / hardware connector");    // this comes after a timeout ~ 10sec.
        while(1);
    }

So, if you're getting that message, you know that the return value from at_ble_init() was not AT_BLE_SUCCESS - don't you?

 

But you don't know what the return value was - so why don't you find out?

That should tell you something!

 

You could also use the debugger to step into at_ble_init()  - and see where, exactly, it fails ...

 

 

Hello everyone,

 

i am having a problem in the communication between the Atmel BTLC1000-XSTK Xplained Pro, after i built the solution, the flash programming works also perfectly, but i dont get the blue circle on the smartphone app when i run the demo (see the user guide: https://github.com/avrxml/asf/bl...).

 

Can someone please help me?

 

Best regards

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Baba20,

 

You have asked this in 6 places. Do it 1 more more time and you will be banned!

 

Moderator

 

Ross McKenzie ValuSoft Melbourne Australia

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I know this is an old post, but it still comes up on google, which is how I found it. I fixed the issue though, so I'll share.

 

Scratliner wrote:

You could also use the debugger to step into at_ble_init()  - and see where, exactly, it fails ...

 

You can't step into at_ble_init() because its an external file, maybe you can, but I have no idea how.

I output at_ble_init to the console which returned an int, I looked through the defines and found out its returning AT_BLE_BUS_TIMEOUT.

 

Maybe someone could answer that for me though? I'm always clicking "Goto Implementation", and when I really need it all it takes me to is a header, very frustrating when I can't get to the source file..  

Is there any way I can view those external ASF files?

 

 

Anyways, how to fix it...

 

All you have to do is right click on your project, go to the tool chain, then symbols.

Edit "BLE_MODULE=BTLC1000_MR," to the correct module, mine was the ZR.

 

That solves the connection problem, but depending on your module, you may now be getting this error "Error: Invalid BTLC1000 Host Interface UART Mode, BTLC1000-ZR supports only 4-WIRE UART mode."

 

Well, in symbols again, change "UART_FLOWCONTROL_6WIRE_MODE=true" to false and "UART_FLOWCONTROL_4WIRE_MODE=false" to true, simple.

 

 

Now you should be able to pair, unless you are using the HID keyboard example on a windows PC, you will still connect, but have a driver error immediately after, and get disconnected. 

I'm kind of surprised Atmel/Microchip let that slip through the cracks.

I had the same issue on the SAMB11 last year but never bothered to fix it, I'll report back if I do.