Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bootloader and then ? #3

Open
phil123456 opened this issue Jul 5, 2020 · 4 comments
Open

bootloader and then ? #3

phil123456 opened this issue Jul 5, 2020 · 4 comments

Comments

@phil123456
Copy link

phil123456 commented Jul 5, 2020

Hello,

  • I wired an FTDI dongle (3v) to my rpi
  • I added a reset switch
  • I copied your bootloader.img as a kernel.img
  • I set putty to 115200 baud

I pasted the blinker01/notmain.srec into putty,

I press 'g' (right?) the program is supposed to be running ?

cos it redisplay the SREC message and that's it

@louigi600
Copy link

I don't think the author looks here ... maybe you will have better luck on RPI forums.
I'm curious did you get the bootloader thing to work ?

@dwelch67
Copy link
Owner

dwelch67 commented Dec 9, 2021

You did a raw/ascii download of the srec file?

@alvaroarenas
Copy link

alvaroarenas commented Jan 6, 2022

Hi @dwelch67

I am also interested in getting the bootloader to work. I successfully got the blinker01 working.

Could you explain in detail the commands you use in minicom. I did:

  • Converted the blinker01 .elf using
arm-none-eabi-objcopy --srec-forceS3 notmain.elf -O srec notmain.srec
  • Started minicom
minicom -b 115200 -D /dev/cu.usbserial-0001
  • I got the pi booting prompt and selected Meta-s (send), ascii, selected the file. But I get BADBAD02 back
MESS:00:00:01.977527:0: Failed to open command line file 'cmdline.txt'
MESS:00:00:02.109417:0: brfs: File read: /mfs/sd/kernel.img
MESS:00:00:02.113297:0: Loading 'kernel.img' to 0x8000 size 0x1f851c
MESS:00:00:02.119441:0: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined
MESS:00:00:02.127842:0: uart: Set PL011 baud rate to 103448.300000 Hz
MESS:00:00:02.134292:0: uart: Baud rate change done...
MESS:00:00:02.137727:0: uart: Baud rate change done...
MESS:00:00:02.143145:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER�������j
                                                                                        002002C4

SREC
BADBAD02

any ideas what could be wrong?
This is the file content I sent

S00F00006E6F746D61696E2E737265631F
S3150000800002D9A0E3050000EBFEFFFFEA001080E5C1
S315000080101EFF2FE1000090E51EFF2FE11EFF2FE15E
S3150000802070402DE964009FE5F9FFFFEB0E16C0E3F3
S31500008030021681E354009FE5F3FFFFEB50609FE5D6
S3150000804050509FE50219A0E30600A0E1EEFFFFEB0A
S315000080500040A0E30400A0E1014084E2EEFFFFEB54
S31500008060010654E3FAFFFF1A0219A0E30500A0E196
S31500008070E5FFFFEB0040A0E30400A0E1014084E23D
S31500008080E5FFFFEB010654E3FAFFFF1AECFFFFEAF8
S3110000809010002020200020202C002020C2
S705000080007A

@philippeflorent
Copy link

philippeflorent commented Dec 8, 2022

You did a raw/ascii download of the srec file?

it's a built code that generated the SREC
I notice that the file starts with S so it should engage to state machine of the bootloader
but it is not
regular communication works since my own firmware works as a terminal

but how do you upload the file ? do you reset then upload ? do you wait a bit ?

on ubuntu putty doesn't seem to do anything as I CTRL+V, right click, middle click

I tried this

#!/bin/bash

echo "sending notmain.srec ..." 
stty -F /dev/ttyUSB0 115200
exec 9<>/dev/ttyUSB0
read answer <&9 ; echo "$answer"
read answer <&9 ; echo "$answer"
read answer <&9 ; echo "$answer"
read answer <&9 ; echo "$answer"
cat notmain.srec >&9
exec 9>&-

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants