BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.embedded-recipes.org//er2026//speaker//GWGFTA
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-er2026-9RX7LL@cfp.embedded-recipes.org
DTSTART;TZID=CET:20260527T144500
DTEND;TZID=CET:20260527T152500
DESCRIPTION:Contemporary SoCs perform initial system boot on a dedicated co
 re and start the additional cores only after the system was fully initiali
 zed. This boot core may be a Cortex-M\, which is also capable of running U
 -Boot\, and remains active even after the other cores started.\n\nThis tal
 k first clarifies the specifics of porting U-Boot to Cortex-M\, including 
 read-only text and read-write data at offset\, limited SRAM size\, partial
  relocation\, console access\, and start of the additional cores.\n\nNext\
 , the talk explains how U-Boot running on the boot core can be used as an 
 always-on debug tool\, to inspect the state of the other cores\, periphera
 ls and memory in the system. This includes interaction with peripherals ev
 en if the other cores may have crashed\, and the use of DMA to access memo
 ry above the 32bit boundary. The talk ends with a real-world example of su
 ch a setup.
DTSTAMP:20260406T234836Z
LOCATION:Auditorium
SUMMARY:U-Boot on boot core as an always-on debug tool - Marek Vasut
URL:https://cfp.embedded-recipes.org/er2026/talk/9RX7LL/
END:VEVENT
END:VCALENDAR