亲爱的支持团队,
we are currently facing an issue with the production test firmware provided by Dialog when running it on our custom PAN1740 based hardware.
The original DA14580 source code has only been adjusted regarding the UART RX/TX pin assignments.
When we connect with Connection Manager and start any TX test (e.g. unmodulated TX), we can observe a carrier in the spectrum, but at a wrong frequency. The signal looks more or less ok for channel 37. The carrier is located at 2402 MHz. Channel 38 is located at 2404 MHz instead of 2426 MHz. Channel 39 is also located at 2404 MHz, but has a much broader shape.
The prod_test fw is based on SDK5.0.4; Connection Manager is v3.0.10.
Can you give a hint what could be the reason for this behaviour?
btw. The actual application fw works well. E.g. the advertisement channels are perfectly met.
Thanks,
Holger
Hi hlinde,
I ve contacted Panasonic on this, they are looking at your issue, they will contact you directly.
Thanks MT_dialog
Good day
I would like to know what are the causes of the pin reset not detected when I try programming with UART on my own board I am using the PAN1740
Hi mayrang,
The reason that the device needs a reset when is programmed via UART is because the Smart Snippets needs to track the 0x02 byte (from the predefined UART pins) that signals the initiation of the UART booting procedure. So by hitting the reset the device starts executing the bootloader, eventually Smart Snippets will catch the 0x02 byte and start the UART booting protocol. So apparently if the Smart Snippets isn;t able to get the reset then it doesn't receive the 0x02 byte which means that most probably something is wrong with your UART connection.
Thanks MT_dialog
Hi MT_dialog
我使用的连接
FTDL to BOART
Rx ----> Tx PIN 04
Tx ----> Rx PIN 05
CTS ----> CTS P03
RTS ----> RTS P02
Vcc ----> 3V
GND ----> GND
they are correct?
Attach the connection of the reset
Thanks for your time
Thanks MT_dialog
already detecting rst was a hardware problem
now I try to program the latest version of the .hex file for AT commands
but nothing appears in tera Term and probe with 9600 Bd, 57600 and 115200 unanswered.
尝试编程SDK 5.0.3和SDK 5.0.4的其他示例,但CRC与我不匹配。
any idea how to solve this?
Hi mayrarg,
The baudrate depends on which pins you are using, from your previous statement the P04 and P05 are operating over a 57600 baudrate, if nothing appears on any of the terminals that you are using (you should see garbage printing due to the bootloader running), then either the device doesn't reset (so no bootloader running) or there should be a connection problem with your UART. Also you mention that the CRC doesn't match for you, what exactly do you mean by that ? You download code and the device doesn't respond with 0x06 (ACK) or it doesn't match the calculation on the STM ? Also be aware that you should download the .bin file and not the .hex file (you should convert the .hex file into a .bin with the appropriate tool hex2bin.exe).
Thanks MT_dialog
我如何监控设备(ACK) and 0x02 byte by UART?
I will try to change the .hex file to .bin, see what happens
thank you very much MT_dialog
Hi mayrarg,
If you would like to see the serial booting procedure you do that via attaching a logic analyser on the bus. Since you are using the Smart Snippets tool it will automatically convert the .hex file that you are using into a .bin, so converting it yourself doesn't really matter (i was under the impression that you were using an external MCU in order to download code). Regarding the error that you get, i suppose that you are using a custom device, perhaps you should check the UART lines on your device apparently the data are corrupted generating an invalid CRC from what the Smart Snippets tool has calculated and what the device sends when the downloading procedure has ended.
Thanks MT_dialog
Hi MT_dialog
I can program the examples od the DA14585 in PAN1740 module exactly as in AN-B-001 file, but the program don't compile, i check the UART lines and this are fine
any idea how to solve this?
Thanks
Hi mayrarg,
For starters the PAN1740 implements a 14580 and not a 585 as far as i know (that means that you are using the wrong SDK, SDK 5.0.4 is the latest for the 580 and 6.0.4 is latest for the 585), and what do you mean the program doesn't compile ? and also the fact that the program doesn't compile doesn't have to do anything with the fact that you are not able to program it via the UART.
Thanks MT_dialog
Hi MT_dialog
然后用sdk 5.0.4I have the problem that crc does not match the calculation in the STM.
The process as described in the AN-B-001 file is fine until after receiving the ACK bit.
Thanks
Hi mayrarg,
I am sorry i am quite confused, you are trying to program a PAN1740 via an STM processor through the UART interface and it returns a CRC mismatch or via Smart Snippets. From the images that you have attached it seems that you trying to do so via Smart Snippets and returns that kind of error. Also, what the 585 fw has to do with the above issue ? the PAN1740 has a 580 device inside and not a 585. Can please spend more time to describe what exactly you would like to do in order for me to be able to help?
Thanks MT_dialog
i'm sorry for the little explanation.
I try to program a PAN1470 module by UART with an FTDI (USB to TTL FT232RL) through SamartSinippes.
As you said I was in error trying to program 585 fw in the module since the PAN1740 has a 580.
When I try to program examples of sdk 2.0.4 of 580 returns the error of CRC does not match. the procedure marked by file AN-B-0001 is correct, I receive bit 0x02 and ACK 0x06, until the moment of receiving the bit of CRC returns 00 its value by deafult.
My problem in itself, is because CRC is not updated or does not perform the XOR to take its value?.
Hi mayrarg,
The bootloader is located in the ROM that means that the operations performed are standard, there is no way to interact or change that code somehow, if the device (580) transmits a 0x00 as a CRC value then i suppose that either there is no actual code download, so there is no actual bytes downloaded into the device (are you able to check that with an analyser), or i suppose that the PAN that you are using is somehow damaged. Can you please check with another device and check if the issue persists. Or can you try to download code via JTAG and not via UART and check if you are able to do so ?
Thanks MT_dialog
Hi MT_dialog
I try to program the PAN1740 with J-Link without success, then it is likely that my device is damaged?
Hi mayrarg,
Either damaged or there is an issue on the SWD connections.
Thanks MT_dialog
Hello MT_dialog
The problem was that I have connected the RST of the PA1740 module to the JTAG connection, but through the thread
https://support.dialog-semicondiondiondum/forums/post/dialog-smartbond-bl ...
I realized that the RST of JTAG and PAN1740 are opposites, so if I keep down the botton of RST that I have connected to both (RST module with RST JTAG) I managed to program the example of ble_app_profile, but the device is not announced, in the thread mentioned above it said that I could be in sleeping mode, how can I disable this sleeping mode?
Hi mayrarg,
为了禁用睡眠模式set the app_default_sleep_mode to ARCH_SLEEP_OFF, but the fact that the device is in sleep mode doesn't mean that the device wont advertise. All the examples perform advertising even if they are in sleep mode, the device is sleeping between the advertising intervals, it doesn't sleep constantly. You wont be able to find why the device doesn't execute (you are not able to find the device over a BLE Scanner) just by downloading the fw over UART, i would suggest to use the JTAG connections and debug via keil, in order to find why that happens.
Thanks MT_dialog
Hi MT_dialog
Already solved, my problem was that I had put #undef in the CFG_DEVELOPMENT_DEBUG statement that caused it not to be announced,
thank you very much!!!, is there anything I can do to indicate that it helped me solve my case?
Hi mayrarg,
Regarding the CFG_DEVELOPMENT_DEBUG, this isn't why the device doesn't operate and might indicate that the device was stuck due to an assertion (different kind of assertions are inserted due to that flag in order to indicate to the developer that something is wrong with the implementation). All the examples should operate with the CFG_DEVELOPMENT_DEBUG. You should debug the device via JTAG in order to check on which assertion the device is stuck with the CFG_DEVELOPMENT_DEBUG.
Regarding the solving indication, since you haven't created a new thread on this, you cannot indicate that you accept or that any of the above suggestions has helped you, you must be the creator of the thread in order to accept an answer.
Thanks MT_dialog