Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Add RAK811 LoRa Tracker Board#254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fpistm merged 2 commits intostm32duino:masterfromfpistm:RAK811_LORA_TRACKER
Oct 1, 2018

Conversation

@fpistm
Copy link
Member

@fpistmfpistm commentedMay 20, 2018•
edited
Loading

Hi@sabas1080,
This PR is the review of your PR#229
I've made several clean and rename the variant RAK811_TRACKER.
RAK811 is a module not really a board but as you mentioned in your PR the board is the
RAK811 LoRa Tracker

I've only one doubt about RAM size 16k or 32k? I think it is 32k, could you confirm? --> Sub menu added to be able to select RAM Size (16Kb by default)

Could you test this variant and let me know if it is ok?
Thanks in advance.

Datasheet:
http://docs.rakwireless.com/en/RAK811%20TrackerBoard/Software%20Development/RAK811%20TrackerBoard%20Datasheet%20V1.1.pdf

Github:
https://github.com/RAKWireless/RAK811_BreakBoard

Using RAK 811 Lora Module
Datasheet:
http://docs.rakwireless.com/en/RAK811/Software%20Development/RAK811%C2%A0Lora%C2%A0Module%C2%A0Datasheet%C2%A0V1.3.pdf

http://www.rakwireless.com/en/download/RAK811/Hardware%20Design

sabas1080 reacted with thumbs up emoji
@fpistmfpistm added new variantAdd support of new bard waiting feedbackFurther information is required labelsMay 20, 2018
@fpistmfpistm self-assigned thisMay 20, 2018
@fpistmfpistm mentioned this pull requestMay 20, 2018
@sabas1080
Copy link
Contributor

Hi@fpistm

The SRAM is 16k

rak811 lora module datasheet v1 3 pdf

Thanks

@fpistmfpistmforce-pushed theRAK811_LORA_TRACKER branch from66d5a9c to5545e3eCompareMay 20, 2018 18:46
@fpistm
Copy link
MemberAuthor

Ok. Thanks. updated to 16kb of RAM. I read somewhere it was up to 32k maybe a mistake...
You could check with STLink how many RAM the board has really.
Let me know if it is ok.

@chaolue
Copy link

@fpistm,

May need to research the SRAM size - seehttps://github.com/Ebiroll/RAK811_BreakBoard

The earlier versions of the board only had 16K ram so stm32l15xx6.ld is default as linker script. If you want to use the full 32K ram you can change this line before copy "ldscript": "/home/olof/rak/STM32L151XBA_FLASH.ld"

@fpistm
Copy link
MemberAuthor

@chaolue yes this is what I've read 👍 Maybe I could add a menu to select ramsize.
@sabas1080 have you tested ?

@fpistmfpistmforce-pushed theRAK811_LORA_TRACKER branch from5545e3e tod788861CompareMay 24, 2018 21:27
@fpistm
Copy link
MemberAuthor

I've added a sub menu to be able to select RAM Size (16Kb by default)

@fpistm
Copy link
MemberAuthor

Any news@sabas1080?
I will do a release soon so if this is tested, I could merge and release it.
Thanks in advance

@fpistmfpistm added this to the1.2.1/1.3.0 milestoneMay 28, 2018
@fpistmfpistmforce-pushed theRAK811_LORA_TRACKER branch 2 times, most recently from344831c todb28efbCompareMay 30, 2018 09:11
@sabas1080
Copy link
Contributor

Hi@fpistm

I am useing stm32flash and it appears the next information

Using Parser : Raw BINARYInterface serial_posix: 115200 8E1Version      : 0x31Option 1     : 0x00Option 2     : 0x00Device ID    : 0x0429 (L1xxx6(8/B)A)- RAM        : 32KiB  (4096b reserved by bootloader)- Flash      : 128KiB (sector size: 16x256)- Option RAM : 16b- System RAM : 4KiB

@fpistm
Copy link
MemberAuthor

So, there is 2 versions. With the ram size menu you can select the right one.
Have you tested this PR?

@fpistm
Copy link
MemberAuthor

Hi@sabas1080,
without feedback from you I could not merge it.
So, without news, it will not be in next release 1.3.0

@fpistmfpistm modified the milestones:1.3.0,1.3.1Jun 14, 2018
@fpistm
Copy link
MemberAuthor

@sabas1080 Any update?

@sabas1080
Copy link
Contributor

I'm going to testing today

fpistm reacted with thumbs up emojifpistm reacted with hooray emoji

@sabas1080
Copy link
Contributor

I have updated to 1.3.0 and

/Library/Arduino15/packages/STM32/hardware/stm32/1.3.0/cores/arduino/stm32/low_power.c: In function 'LowPower_EnableWakeUpPin': /Library/Arduino15/packages/STM32/hardware/stm32/1.3.0/cores/arduino/stm32/low_power.c:98:12: error: 'SYS_WKUP1' undeclared (first use in this function) case SYS_WKUP1 : ^~~~~~~~~ /Library/Arduino15/packages/STM32/hardware/stm32/1.3.0/cores/arduino/stm32/low_power.c:98:12: note: each undeclared identifier is reported only once for each function it appears in /Library/Arduino15/packages/STM32/hardware/stm32/1.3.0/cores/arduino/stm32/low_power.c:108:12: error: 'SYS_WKUP2' undeclared (first use in this function) case SYS_WKUP2 : ^~~~~~~~~ /Library/Arduino15/packages/STM32/hardware/stm32/1.3.0/cores/arduino/stm32/low_power.c:118:12: error: 'SYS_WKUP3' undeclared (first use in this function) case SYS_WKUP3 : ^~~~~~~~~ exit status 1 Error compilando para la tarjeta RAKWireless.

@fpistm
Copy link
MemberAuthor

Sounds strange as I've added the PinNamesVar.h
https://github.com/stm32duino/Arduino_Core_STM32/pull/254/files#diff-5ad876594d46b421d0d4c00eb77e42d8

sabas1080 reacted with thumbs up emoji

@sabas1080
Copy link
Contributor

sabas1080 commentedJul 10, 2018•
edited
Loading

now I have the next error

java.io.IOException: Cannot run program /Library/Arduino15/packages/STM32/hardware/stm32/tools/macosx/serial_upload: error=2, No such file or directory

@sabas1080
Copy link
Contributor

it seems to be a path error

@fpistm
Copy link
MemberAuthor

So the build is ok but it do not fin the uploader tools.
This is due to your install to use git.
https://github.com/stm32duino/wiki/wiki/Using-git-repository#3-hereafter-2-methods-to-use-git-repository
When using git depending on how and where you put the core you have to update the platform.txt.

sabas1080 reacted with thumbs up emoji

@fpistm
Copy link
MemberAuthor

Yes. How do you use the core git repo ?

@fpistm
Copy link
MemberAuthor

I do not changed tools binaries. So, if it's work before this should always work.

@sabas1080
Copy link
Contributor

Is the version of the binary

My version is

stm32flash 0.5http://stm32flash.sourceforge.net/

@fpistm
Copy link
MemberAuthor

To sum up: build is ok but you cannot flash thanks Serial?
As said there is no change around flash tools. So, if it is ok before I guess this is linked to the board config to ba able to flash through Serial. Bootloader issue ?

@sabas1080
Copy link
Contributor

Build ok, but stmflash version not compatible with chip

@fpistm
Copy link
MemberAuthor

fpistm commentedJul 11, 2018•
edited
Loading

Ok so you never flash using stm32flash provided with core tools before?

Regarding stm32flash source:

/* L1 */{0x416, "STM32L1xxx6(8/B)"                , 0x20000800, 0x20004000, 0x08000000, 0x08020000, 16, p_256 , 0x1FF80000, 0x1FF8001F, 0x1FF00000, 0x1FF01000, F_NO_ME},{0x429, "STM32L1xxx6(8/B)A"               , 0x20001000, 0x20008000, 0x08000000, 0x08020000, 16, p_256 , 0x1FF80000, 0x1FF8001F, 0x1FF00000, 0x1FF01000, 0},{0x427, "STM32L1xxxC"                     , 0x20001000, 0x20008000, 0x08000000, 0x08040000, 16, p_256 , 0x1FF80000, 0x1FF8001F, 0x1FF00000, 0x1FF02000, 0},{0x436, "STM32L1xxxD"                     , 0x20001000, 0x2000C000, 0x08000000, 0x08060000, 16, p_256 , 0x1FF80000, 0x1FF8009F, 0x1FF00000, 0x1FF02000, 0},{0x437, "STM32L1xxxE"                     , 0x20001000, 0x20014000, 0x08000000, 0x08080000, 16, p_256 , 0x1FF80000, 0x1FF8009F, 0x1FF00000, 0x1FF02000, F_NO_ME},

Device ID : 0x0429 (L1xxx6(8/B)A) is supported.

Have you selected 32kb in the RAM menu? To use the correct linker script (ldscript_xba.ld) as it seems you have- RAM : 32KiB (4096b reserved by bootloader)

There is one issue around L1 on stm32flash:
https://sourceforge.net/p/stm32flash/tickets/92/

I will try to try stm32flash on L1 to see if I reproduce your issue.

Anyway could you test with ST-Link to validate the variant?

sabas1080 reacted with thumbs up emoji

@sabas1080
Copy link
Contributor

sabas1080 commentedJul 13, 2018•
edited
Loading

Now that I remember, I am using this correction

Formlabs/stm32flash@8c4aa65

that's why I have version 5

@fpistm
Copy link
MemberAuthor

Ah interesting.
So, it should be fine to build STM32flash with this fix.
Anyway, what is the status of this variant?
Is it ok from your point of view?

sabas1080 reacted with thumbs up emoji

@sabas1080
Copy link
Contributor

Yes, it should build STM32flash with this fix
Working variant blink and serial

@sabas1080
Copy link
Contributor

I have an error with next code

void setup() {    pinMode(LED_BUILTIN,OUTPUT);//PB_6  //CRF3    delay(200);    digitalWrite(LED_BUILTIN,HIGH);    delay(500);    digitalWrite(LED_BUILTIN,LOW);    delay(500);     }void loop() {}

led stays on

@fpistm
Copy link
MemberAuthor

If the LED is connected to 3.3V, putting LOW on the pin set the LED ON.

Ex on the DISCO L475 IOT:
discoiotled

Putting LOW set the LD4 on

sabas1080 reacted with thumbs up emoji

@sabas1080
Copy link
Contributor

Yes, LED is connected to 3.3v

@fpistm
Copy link
MemberAuthor

So this is normal :)

@fpistm
Copy link
MemberAuthor

About STM32Flash issue.
There will be 2 solutions:
1- Update it with the Fix and rebuild all host OS binaries (Windows/linux/Mac)
2- Unified tools used to flash. It should be possible to use STM32CubeProgrammer CLI. Seestm32duino/Arduino_Tools#23

Think the 2nd is the best solution as it support all STM32 Series.

sabas1080 reacted with thumbs up emoji

@sabas1080
Copy link
Contributor

I'm going to try the second option

@sabas1080
Copy link
Contributor

I'm trying with STM32CubeProgrammer and i have error de protection
captura de pantalla 2018-07-16 a la s 11 40 04

10:16:49 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:16:49 : Sending init command: 10:16:49 : byte 0x7F sent successfully to target10:16:49 : Received response from target: 0x7910:16:49 : Activating device: OK10:16:49 : Sending GetID command and its XOR:10:16:49 : byte 0x02 sent successfully to target10:16:49 : byte 0xFD sent successfully to target10:16:49 : Received response from target: 0x7910:16:49 : Received response from target: 0x0104297910:16:49 : Chip ID: 0x429 10:16:49 : Sending Get command and its XOR:10:16:49 : byte 0x00 sent successfully to target10:16:49 : byte 0xFF sent successfully to target10:16:49 : Received response from target: 0x7910:16:49 : Received response from target: 0x0b10:16:49 : size of bytes in the response: 1110:16:49 : Received response from target: 0x3100010211213144637382927910:16:49 : Full received response: 0b3100010211213144637382927910:16:49 : byte 0x11 sent successfully to target10:16:49 : byte 0xEE sent successfully to target10:16:49 : data sent successfully to target: 0x0800000010:16:49 : byte 0x08 sent successfully to target10:16:49 : byte 0x00 sent successfully to target10:16:49 : byte 0xFF sent successfully to target10:16:49 : Sending GetID command and its XOR:10:16:49 : byte 0x02 sent successfully to target10:16:49 : byte 0xFD sent successfully to target10:16:49 : Received response from target: 0x7910:16:49 : Received response from target: 0x0104297910:16:49 : byte 0x11 sent successfully to target10:16:49 : byte 0xEE sent successfully to target10:16:49 : data sent successfully to target: 0x0800000010:16:49 : byte 0x08 sent successfully to target10:16:49 : byte 0x00 sent successfully to target10:16:49 : byte 0xFF sent successfully to target10:16:49 : Sending Read command and its XOR:10:16:49 : byte 0x11 sent successfully to target10:16:49 : byte 0xEE sent successfully to target10:16:49 : Received response from target: 0x7910:16:49 : Sending Read address and its checksum:10:16:49 : data sent successfully to target: 0x40023c1c10:16:49 : byte 0x62 sent successfully to target10:16:49 : Received response from target: 0x7910:16:49 : Sending number of bytes to be read - 1 and its checksum:10:16:49 : data sent successfully to target: 0x0310:16:49 : byte 0xFC sent successfully to target10:16:49 : Received response from target: 0x1f10:16:49 : Error: Number of bytes to be be read at address: 0x40023C1C not acknowledged!10:16:49 : Sending Read command and its XOR:10:16:49 : byte 0x11 sent successfully to target10:16:49 : byte 0xEE sent successfully to target10:16:49 : Received response from target: 0x1f10:16:49 : Error: READ command not acknowledged at address: 0x40023C1C10:16:49 : byte 0x11 sent successfully to target10:16:49 : byte 0xEE sent successfully to target10:16:49 : data sent successfully to target: 0x0800000010:16:49 : byte 0x08 sent successfully to target10:16:53 : Disabling memory Read Protection...10:16:53 : Sending read unprotect command and its XOR:10:16:53 : byte 0x92 sent successfully to target10:16:53 : byte 0x6D sent successfully to target10:16:53 : Received response from target: 0x1f10:16:53 : Error: Disabling memory Read Protection failed10:17:09 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:17:09 : Sending init command: 10:17:09 : byte 0x7F sent successfully to target10:17:09 : Received response from target: 0x1f10:17:09 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again... 10:17:17 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:17:17 : Sending init command: 10:17:17 : byte 0x7F sent successfully to target10:17:18 : No response from target received10:17:18 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again... 10:17:21 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:17:21 : Sending init command: 10:17:21 : byte 0x7F sent successfully to target10:17:21 : Received response from target: 0x1f10:17:21 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again... 10:18:34 : Read File: /Users/sabas/Documents/proyectoshd/RAK811WithCoreArduino/ttn/ttn.ino.RAK811.hex10:18:34 : Number of segments: 110:18:34 : segment[0]: address= 0x8000000, size= 0x80C410:18:49 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:18:49 : Sending init command: 10:18:49 : byte 0x7F sent successfully to target10:18:50 : No response from target received10:18:50 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again... 10:18:59 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:18:59 : Sending init command: 10:18:59 : byte 0x7F sent successfully to target10:18:59 : Received response from target: 0x7910:18:59 : Activating device: OK10:18:59 : Sending GetID command and its XOR:10:18:59 : byte 0x02 sent successfully to target10:18:59 : byte 0xFD sent successfully to target10:18:59 : Received response from target: 0x7910:18:59 : Received response from target: 0x0104297910:18:59 : Chip ID: 0x429 10:18:59 : Sending Get command and its XOR:10:18:59 : byte 0x00 sent successfully to target10:18:59 : byte 0xFF sent successfully to target10:18:59 : Received response from target: 0x7910:18:59 : Received response from target: 0x0b10:18:59 : size of bytes in the response: 1110:18:59 : Received response from target: 0x3100010211213144637382927910:18:59 : Full received response: 0b3100010211213144637382927910:18:59 : byte 0x11 sent successfully to target10:18:59 : byte 0xEE sent successfully to target10:18:59 : data sent successfully to target: 0x0800000010:18:59 : byte 0x08 sent successfully to target10:18:59 : byte 0x00 sent successfully to target10:18:59 : byte 0xFF sent successfully to target10:18:59 : Sending GetID command and its XOR:10:18:59 : byte 0x02 sent successfully to target10:18:59 : byte 0xFD sent successfully to target10:18:59 : Received response from target: 0x7910:18:59 : Received response from target: 0x0104297910:18:59 : byte 0x11 sent successfully to target10:18:59 : byte 0xEE sent successfully to target10:18:59 : data sent successfully to target: 0x0800000010:18:59 : byte 0x08 sent successfully to target10:18:59 : byte 0x00 sent successfully to target10:18:59 : byte 0xFF sent successfully to target10:18:59 : Sending Read command and its XOR:10:18:59 : byte 0x11 sent successfully to target10:18:59 : byte 0xEE sent successfully to target10:18:59 : Received response from target: 0x7910:18:59 : Sending Read address and its checksum:10:18:59 : data sent successfully to target: 0x40023c1c10:18:59 : byte 0x62 sent successfully to target10:18:59 : Received response from target: 0x7910:18:59 : Sending number of bytes to be read - 1 and its checksum:10:18:59 : data sent successfully to target: 0x0310:18:59 : byte 0xFC sent successfully to target10:18:59 : Received response from target: 0x1f10:18:59 : Error: Number of bytes to be be read at address: 0x40023C1C not acknowledged!10:18:59 : Sending Read command and its XOR:10:18:59 : byte 0x11 sent successfully to target10:18:59 : byte 0xEE sent successfully to target10:18:59 : Received response from target: 0x1f10:18:59 : Error: READ command not acknowledged at address: 0x40023C1C10:18:59 : byte 0x11 sent successfully to target10:18:59 : byte 0xEE sent successfully to target10:18:59 : data sent successfully to target: 0x0800000010:18:59 : byte 0x08 sent successfully to target10:19:01 : Disabling memory Read Protection...10:19:01 : Sending read unprotect command and its XOR:10:19:01 : byte 0x92 sent successfully to target10:19:01 : byte 0x6D sent successfully to target10:19:01 : Received response from target: 0x1f10:19:01 : Error: Disabling memory Read Protection failed10:19:08 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:19:08 : Sending init command: 10:19:08 : byte 0x7F sent successfully to target10:19:08 : Received response from target: 0x1f10:19:08 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again... 10:19:16 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:19:16 : Sending init command: 10:19:16 : byte 0x7F sent successfully to target10:19:16 : Received response from target: 0x7910:19:16 : Activating device: OK10:19:16 : Sending GetID command and its XOR:10:19:16 : byte 0x02 sent successfully to target10:19:16 : byte 0xFD sent successfully to target10:19:16 : Received response from target: 0x7910:19:16 : Received response from target: 0x0104297910:19:16 : Chip ID: 0x429 10:19:16 : Sending Get command and its XOR:10:19:16 : byte 0x00 sent successfully to target10:19:16 : byte 0xFF sent successfully to target10:19:16 : Received response from target: 0x7910:19:16 : Received response from target: 0x0b10:19:16 : size of bytes in the response: 1110:19:16 : Received response from target: 0x3100010211213144637382927910:19:16 : Full received response: 0b3100010211213144637382927910:19:16 : byte 0x11 sent successfully to target10:19:16 : byte 0xEE sent successfully to target10:19:16 : data sent successfully to target: 0x0800000010:19:16 : byte 0x08 sent successfully to target10:19:16 : byte 0x00 sent successfully to target10:19:16 : byte 0xFF sent successfully to target10:19:16 : Sending GetID command and its XOR:10:19:16 : byte 0x02 sent successfully to target10:19:16 : byte 0xFD sent successfully to target10:19:16 : Received response from target: 0x7910:19:16 : Received response from target: 0x0104297910:19:16 : byte 0x11 sent successfully to target10:19:16 : byte 0xEE sent successfully to target10:19:16 : data sent successfully to target: 0x0800000010:19:16 : byte 0x08 sent successfully to target10:19:16 : byte 0x00 sent successfully to target10:19:16 : byte 0xFF sent successfully to target10:19:16 : Sending Read command and its XOR:10:19:16 : byte 0x11 sent successfully to target10:19:16 : byte 0xEE sent successfully to target10:19:16 : Received response from target: 0x7910:19:16 : Sending Read address and its checksum:10:19:16 : data sent successfully to target: 0x40023c1c10:19:16 : byte 0x62 sent successfully to target10:19:16 : Received response from target: 0x7910:19:16 : Sending number of bytes to be read - 1 and its checksum:10:19:16 : data sent successfully to target: 0x0310:19:16 : byte 0xFC sent successfully to target10:19:16 : Received response from target: 0x1f10:19:16 : Error: Number of bytes to be be read at address: 0x40023C1C not acknowledged!10:19:16 : Sending Read command and its XOR:10:19:16 : byte 0x11 sent successfully to target10:19:16 : byte 0xEE sent successfully to target10:19:16 : Received response from target: 0x1f10:19:16 : Error: READ command not acknowledged at address: 0x40023C1C10:19:16 : byte 0x11 sent successfully to target10:19:16 : byte 0xEE sent successfully to target10:19:16 : data sent successfully to target: 0x0800000010:19:16 : byte 0x08 sent successfully to target10:19:18 : Disabling memory Read Protection...10:19:18 : Sending read unprotect command and its XOR:10:19:18 : byte 0x92 sent successfully to target10:19:18 : byte 0x6D sent successfully to target10:19:18 : Received response from target: 0x1f10:19:18 : Error: Disabling memory Read Protection failed10:19:25 : Error: Connection to target must be established before performing the erase command.10:19:32 : Error: Connection to target must be established before performing the erase command.10:19:41 : Error: Connection to target must be established before performing the erase command.10:19:44 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:19:44 : Sending init command: 10:19:44 : byte 0x7F sent successfully to target10:19:44 : Received response from target: 0x7910:19:44 : Activating device: OK10:19:44 : Sending GetID command and its XOR:10:19:44 : byte 0x02 sent successfully to target10:19:44 : byte 0xFD sent successfully to target10:19:44 : Received response from target: 0x7910:19:44 : Received response from target: 0x0104297910:19:44 : Chip ID: 0x429 10:19:44 : Sending Get command and its XOR:10:19:44 : byte 0x00 sent successfully to target10:19:44 : byte 0xFF sent successfully to target10:19:44 : Received response from target: 0x7910:19:44 : Received response from target: 0x0b10:19:44 : size of bytes in the response: 1110:19:44 : Received response from target: 0x3100010211213144637382927910:19:44 : Full received response: 0b3100010211213144637382927910:19:44 : byte 0x11 sent successfully to target10:19:44 : byte 0xEE sent successfully to target10:19:44 : data sent successfully to target: 0x0800000010:19:44 : byte 0x08 sent successfully to target10:19:44 : byte 0x00 sent successfully to target10:19:44 : byte 0xFF sent successfully to target10:19:44 : Sending GetID command and its XOR:10:19:44 : byte 0x02 sent successfully to target10:19:44 : byte 0xFD sent successfully to target10:19:44 : Received response from target: 0x7910:19:44 : Received response from target: 0x0104297910:19:44 : byte 0x11 sent successfully to target10:19:44 : byte 0xEE sent successfully to target10:19:44 : data sent successfully to target: 0x0800000010:19:44 : byte 0x08 sent successfully to target10:19:44 : byte 0x00 sent successfully to target10:19:44 : byte 0xFF sent successfully to target10:19:44 : Sending Read command and its XOR:10:19:44 : byte 0x11 sent successfully to target10:19:44 : byte 0xEE sent successfully to target10:19:44 : Received response from target: 0x7910:19:44 : Sending Read address and its checksum:10:19:44 : data sent successfully to target: 0x40023c1c10:19:44 : byte 0x62 sent successfully to target10:19:44 : Received response from target: 0x7910:19:44 : Sending number of bytes to be read - 1 and its checksum:10:19:44 : data sent successfully to target: 0x0310:19:44 : byte 0xFC sent successfully to target10:19:44 : Received response from target: 0x1f10:19:44 : Error: Number of bytes to be be read at address: 0x40023C1C not acknowledged!10:19:44 : Sending Read command and its XOR:10:19:44 : byte 0x11 sent successfully to target10:19:44 : byte 0xEE sent successfully to target10:19:44 : Received response from target: 0x1f10:19:44 : Error: READ command not acknowledged at address: 0x40023C1C10:19:44 : byte 0x11 sent successfully to target10:19:44 : byte 0xEE sent successfully to target10:19:44 : data sent successfully to target: 0x0800000010:19:44 : byte 0x08 sent successfully to target10:19:54 : Disabling memory Read Protection...10:19:54 : Sending read unprotect command and its XOR:10:19:54 : byte 0x92 sent successfully to target10:19:54 : byte 0x6D sent successfully to target10:19:54 : Received response from target: 0x1f10:19:54 : Error: Disabling memory Read Protection failed10:19:56 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:19:56 : Sending init command: 10:19:56 : byte 0x7F sent successfully to target10:19:56 : Received response from target: 0x1f10:19:56 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again... 10:20:02 : Serial Port cu.SLAB_USBtoUART is successfully opened.10:20:02 : Sending init command: 10:20:02 : byte 0x7F sent successfully to target10:20:02 : Received response from target: 0x7910:20:02 : Activating device: OK10:20:02 : Sending GetID command and its XOR:10:20:02 : byte 0x02 sent successfully to target10:20:02 : byte 0xFD sent successfully to target10:20:02 : Received response from target: 0x7910:20:02 : Received response from target: 0x0104297910:20:02 : Chip ID: 0x429 10:20:02 : Sending Get command and its XOR:10:20:02 : byte 0x00 sent successfully to target10:20:02 : byte 0xFF sent successfully to target10:20:02 : Received response from target: 0x7910:20:02 : Received response from target: 0x0b10:20:02 : size of bytes in the response: 1110:20:02 : Received response from target: 0x3100010211213144637382927910:20:02 : Full received response: 0b3100010211213144637382927910:20:02 : byte 0x11 sent successfully to target10:20:02 : byte 0xEE sent successfully to target10:20:02 : data sent successfully to target: 0x0800000010:20:02 : byte 0x08 sent successfully to target10:20:02 : byte 0x00 sent successfully to target10:20:02 : byte 0xFF sent successfully to target10:20:02 : Sending GetID command and its XOR:10:20:02 : byte 0x02 sent successfully to target10:20:02 : byte 0xFD sent successfully to target10:20:02 : Received response from target: 0x7910:20:02 : Received response from target: 0x0104297910:20:02 : byte 0x11 sent successfully to target10:20:02 : byte 0xEE sent successfully to target10:20:02 : data sent successfully to target: 0x0800000010:20:02 : byte 0x08 sent successfully to target10:20:02 : byte 0x00 sent successfully to target10:20:02 : byte 0xFF sent successfully to target10:20:02 : Sending Read command and its XOR:10:20:02 : byte 0x11 sent successfully to target10:20:02 : byte 0xEE sent successfully to target10:20:02 : Received response from target: 0x7910:20:02 : Sending Read address and its checksum:10:20:02 : data sent successfully to target: 0x40023c1c10:20:02 : byte 0x62 sent successfully to target10:20:02 : Received response from target: 0x7910:20:02 : Sending number of bytes to be read - 1 and its checksum:10:20:02 : data sent successfully to target: 0x0310:20:02 : byte 0xFC sent successfully to target10:20:02 : Received response from target: 0x1f10:20:02 : Error: Number of bytes to be be read at address: 0x40023C1C not acknowledged!10:20:02 : Sending Read command and its XOR:10:20:02 : byte 0x11 sent successfully to target10:20:02 : byte 0xEE sent successfully to target10:20:02 : Received response from target: 0x1f10:20:02 : Error: READ command not acknowledged at address: 0x40023C1C10:20:02 : byte 0x11 sent successfully to target10:20:02 : byte 0xEE sent successfully to target10:20:02 : data sent successfully to target: 0x0800000010:20:02 : byte 0x08 sent successfully to target10:21:24 : Error: Connection to target must be established before performing the read command.

@fpistm
Copy link
MemberAuthor

Did you set the Boot0 to 1 ?

@sabas1080
Copy link
Contributor

yes

@fpistm
Copy link
MemberAuthor

Hi@sabas1080,
there is a new version of STM32CubeProgrammer, could you try with it.
Anyway, I think I will rebuilt the stm32flasher with the fix.

@fpistm
Copy link
MemberAuthor

Small update, I will update soon all the current upload tools (STM32Flasher, STLink for windows and texane stlink for Linux/MacOS) to their latest version.
At this time, I could not integrate the STM32CubeProgrammer due to some issues (JRE,...)

sabas1080 reacted with thumbs up emoji

@fpistm
Copy link
MemberAuthor

Hi@sabas1080
Tools have been updated, so Serial upload will be ok for this target using the next release
Seestm32duino/Arduino_Tools#27

I think I will merge this PR as the basic support should be ok.
Are you ok@sabas1080 ?

sabas1080 reacted with thumbs up emoji

@fpistmfpistm removed waiting feedbackFurther information is required review on going labelsOct 1, 2018
@fpistmfpistm merged commit7799334 intostm32duino:masterOct 1, 2018
@fpistmfpistm deleted the RAK811_LORA_TRACKER branchOctober 1, 2018 08:18
benwaffle pushed a commit to benwaffle/Arduino_Core_STM32 that referenced this pull requestApr 10, 2019
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

@fpistmfpistm

Labels

new variantAdd support of new bard

Projects

None yet

Milestone

1.4.0

Development

Successfully merging this pull request may close these issues.

3 participants

@fpistm@sabas1080@chaolue
[8]ページ先頭
©2009-2025 Movatter.jp